You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Given that jdk_jfr tests do not run well on certain platforms, like arm32 (or win32?), rather than exclude 10s of testcases, we will exclude the entire target on those platforms. So, if there are more than 5 testcases failing out of the set, we should consider this approach, otherwise we just exclude via ProblemList.
It appears as though the tests were not well tested on those platforms, but we need to confirm if they are ever met to be run there (and if not, lobby to exclude specific tests upstream).
The text was updated successfully, but these errors were encountered:
hmm... perhaps it is too aggressive to remove the entire target then... I just noted that jdk_jfr is not tier1 or tier2 but rather tier3 (in jdk_svc), but that is in jdk_stable... (of note, some jfr tests require g1 gc and I have not looked closely at the list to see if this is correlated with the failures we have seen)
Given that jdk_jfr tests do not run well on certain platforms, like arm32 (or win32?), rather than exclude 10s of testcases, we will exclude the entire target on those platforms. So, if there are more than 5 testcases failing out of the set, we should consider this approach, otherwise we just exclude via ProblemList.
It appears as though the tests were not well tested on those platforms, but we need to confirm if they are ever met to be run there (and if not, lobby to exclude specific tests upstream).
The text was updated successfully, but these errors were encountered: