-
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
System.Text.RegularExpressions.Tests.AttRegexTests test fails in CI #75808
Comments
Tagging subscribers to this area: @dotnet/area-system-text-regularexpressions Issue Details
Hit in #75805. Log https://helixre107v0xdeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-pull-75805-merge-b1ca28fe798046d3af/System.Text.RegularExpressions.Tests/1/console.2a2dc4a5.log?helixlogtype=result
|
cc: @stephentoub This is very weird; those tests are supposed to be deterministic. I understand that this is a theory that in reallity involves hundreds of tests due to all of the permutations we make, so grepping for failures of the test doesn't really equate to having a Fact that fails as often, but I still don't understand why any of these tests would ever fail indeterministic, the line that is failing is literally just evaluating if a given input matches a given Regex object. Any clues why this may be flaky Steve? Not sure if it is relevant, but in the query that @jkotas provided above, this has failed 4 times in rolling in the last 30 days, and it has always been in the queue |
It is likely a GC hole. Does this test calls into the recently vectorized methods? They would be my primary suspect. Here are a few things you can do to help diagnose it:
|
The particular pattern shown in the opening issue comment will end up using |
Similar failures in a different test https://helixre107v0xdeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-pull-75612-merge-564fd52802984edbad/System.Text.RegularExpressions.Tests/1/console.09dea590.log?helixlogtype=result :
|
That compiled regex would also end up using |
I am going to close the issue since no activity here or for "AttRegexTests" in 10 months, please reopen it if it fails again - at that point we can fill out the "known issue" template to track the failures. The reference above to |
Runfo failures in last 30 days
As of 9/24:
No failures in Kusto as of 9/24
Console log on 9/24 (rolling run 28605):
Original report
Hit in #75805. Log https://helixre107v0xdeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-pull-75805-merge-b1ca28fe798046d3af/System.Text.RegularExpressions.Tests/1/console.2a2dc4a5.log?helixlogtype=result
Report
Summary
Known issue validation
Build: 🔎⚠️ Validation could not be done without an Azure DevOps build URL on the issue. Please add it to the "Build: 🔎" line.
Result validation:
The text was updated successfully, but these errors were encountered: