-
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
Test failure:System.Security.Cryptography.X509Certificates.Tests.ChainTests.BuildInvalidSignatureTwice #57187
Comments
Tagging subscribers to this area: @bartonjs, @vcsjones, @krwq, @GrabYourPitchforks Issue DetailsRun: runtime-coreclr libraries-jitstress 20210810.1 Failed test:
Error messags:
|
Configuration: |
The failure isn't exactly reproducible, but we should make a better special assert for successful chain builds that reports what went wrong when they fail. |
Well, this particular case is nothing went wrong, but we expected it to (the chain built when it was not expected to). |
Oy. One of these days, I'll learn to read. |
OK, for "should have failed, but didn't", we probably want to figure out a sensible way of logging all of the generated data to see if it reproduces. |
Happened again:
Configuration: |
Here it is again:
Configuration: |
Failed again in: runtime 20211228.1 Failed test:
Error message:
|
This seems to be mostly occurring on Windows 7 now, despite the original issue indicating Linux. Has it happened at all on Linux since the initial report? |
Happened on Windows 7 for me just now:
It's happening about 5x a month: Execute: Web | Desktop | Web (Lens) | Desktop (SAW) https://engsrvprod.kusto.windows.net/engineeringdata TestResults
| join kind=inner WorkItems on WorkItemId
| join kind=inner Jobs on JobId
| where Started >= now(-60d)
| where Result == "Fail"
| where Method == "BuildInvalidSignatureTwice"
| where Message startswith "Chain is valid on execution 1"
| project QueueName, Started//, Message
| sort by Started desc
//| summarize count() by Status, QueueName, Message
|
@danmoseley for your kusto query... there are actually two tests with that method name... runtime/src/libraries/System.Security.Cryptography.X509Certificates/tests/DynamicChainTests.cs Line 71 in 380cfc9
and runtime/src/libraries/System.Security.Cryptography.X509Certificates/tests/ChainTests.cs Line 951 in 380cfc9
Is your query lumping them together? If so, what do the results look like when broken up? |
Failed again in: runtime-coreclr libraries-jitstressregs 20230226.1 Failed test:
Error message:
|
Duplicate of #82837 |
Run: runtime-coreclr libraries-jitstress 20210810.1
Failed test:
Error messags:
The text was updated successfully, but these errors were encountered: