-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
System.Text.RegularExpressions.Tests failing for release 3.1 #41286
Comments
Just adding a note that setting flags in S.T.RegEx.csproj to 1) turn on XUnit logs and 2) turn off parallel unit tests did not help. The logs didn't show anything, and the failure still occurred. |
It is worth noting that this is not only happening on release/3.1, so whatever change that is causing the memory corruption is also in dotnet/runtime as when doing the investigation I found very similar failures in dotnet/runtime runs as well. |
So we(me and @joperezr ) spent some time looking at this and I'm not sure we have enough actionable material here. We ran this query:
which resulted in 1 failing run with a coredump. When I investigated that run, it looks like many libs failed with time outs and seg faults, which leads me to believe that RegEx is not the problem. If I delete the |
Here's the latest. Most looked like the process being killed.
One was a little different. Could it be a lead?
|
Nice! Will track this down tomorrow and disable it if it makes sense. I honestly have no idea why this would start failing in corefx suddenly. Maybe there was a globalization related change on the CI machines (because of ICU/(non-ICU)). Just guessing here. |
Actually found we were hitting a similar thing in 5.0 that @stephentoub fixed. #2153 Maybe we could try backporting the test fix?
Fix made was #2194 |
Ah, that PR was made before I started with RegEx, or I would've remembered! Out of curiosity, how did you find the issue/toub's PR? |
I searched for "exit code 137". YMMV, this change touches tests which were added in 5.0, but it might also touch some that preexisted. I liked @stephentoub's technique for surveying the test workload. Would be nice to also survey memory usage, but that might not be present in the log. |
@ericstj are you sure that |
yes we can remove the blocking servicing and blocking-ci as well. we moved the failing test to outerloop |
I think this can actually be closed with @pgovind's fix, assuming we're seeing successful PRs runs now. I don't actually see any PRs after his change, however his was green. |
Yes we have green builds now dotnet/corefx#43007 |
System.Text.RegularExpressions.Tests are failing on release 3.1 branch consistently.
@joperezr did some investigation to find if its related to a particular os or infra.
It Fails on a lot of different distros and some of them show that its a memory corruption error
https://dev.azure.com/dnceng/public/_build/results?buildId=780834&view=logs&jobId=a52227ff-668e-56e2-c853-fe96ee61d984&j=a52227ff-668e-56e2-c853-fe96ee61d984&t=60819441-8b21-5634-db97-1a5a84d92242
There are dumps available offline.
cc @joperezr @ericstj @safern @ViktorHofer
The text was updated successfully, but these errors were encountered: