-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adjust SkipOnCoreClr for Match_ExcessPrefix test #59564
Conversation
Tagging subscribers to this area: @eerhardt, @dotnet/area-system-text-regularexpressions Issue DetailsWe wanted this test to skip on: cc @stephentoub
|
7ed5777
to
8756c60
Compare
src/libraries/System.Text.RegularExpressions/tests/Regex.Match.Tests.cs
Outdated
Show resolved
Hide resolved
Thanks. Are there other uses of SkipOnCoreClr that specify multiple conditions? Given that ConditionalXx runs the test only if all conditions pass, as the inverse it would logically make sense if SkipXx didn't run the test if any of them were an issue. So unless we're depending on this in other places, I'd be inclined to fix the attribute instead. But we should also validate other attributes to make sure we maintain consistent behavior so that they remain predictable. |
There are only two other places where multiple conditions are used: runtime % git grep 'SkipOnCoreClr.*,.*,' :/
src/libraries/System.Drawing.Common/tests/mono/System.Drawing/BitmapTests.cs: [SkipOnCoreClr("https://github.com/dotnet/runtime/issues/37082", TestPlatforms.AnyUnix, RuntimeConfiguration.Checked)]
src/libraries/System.Runtime.Numerics/tests/BigInteger/BigIntegerToStringTests.cs: [SkipOnCoreClr("Long running tests: https://github.com/dotnet/runtime/issues/11980", TestPlatforms.Linux, RuntimeConfiguration.Checked)]
# ruling out multi-line case
runtime % git grep SkipOnCoreClr :/ | grep -v ']'
# nothing Looks like we want |
Browser_wasm_Windows failure is #59556. |
e9e200f
to
a1582f2
Compare
Maybe a better way to do this is change the
|
3fb8693
to
df1b082
Compare
Sounds good. Question, do we want to make the change in arcade and wait for arcade update (+ fix the skip attribute) to fix #59541? Or should we take this change (initial simple version 8756c60) to unblock clean CI and then update arcade lazily? |
If this is blocking PRs and making CI red, we should merge the quickest fix and then cleanup once the attribute supports multiple instances of it. |
df1b082
to
8756c60
Compare
Thanks, I have reverted it back to earlier version. I'll follow up on arcade (unless someone else beat me to it 🙂). |
What's the status of this PR? Is it ready to be merged? Asking as this test failure nukes our pass rate (it's 0% right now). |
cc @krwq |
I've disabled it until the right fix is available runtime/src/libraries/System.Text.RegularExpressions/tests/Regex.Match.Tests.cs Line 1093 in 5d71e32
|
c92bbf7
to
b060d5c
Compare
Ah, arcade was updated today, just noticed that it missed the fix commit. 😕 |
b060d5c
to
4502cde
Compare
Today's arcade update brought the updated |
Thanks, @am11! |
We wanted this test to skip on:
RuntimeConfiguration.Checked
orRuntimeTestModes.JitMinOpts
,but
SkipOnCoreClr
performsRuntimeConfiguration.Checked
andRuntimeTestModes.JitMinOpts
.Related: #10680
Fixes: #59541
cc @stephentoub