-
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 XmlSerializerTests.Xml_NookTypes #86563
Comments
Failed again in: runtime-coreclr libraries-jitstress-random 20230527.1 Failed test:
Error message:
More failures
|
CC @markples if it can be test merging related. CC @dotnet/jit-contrib. |
This test is not merged.
|
Failed again in: runtime-coreclr libraries-jitstress-random 20230610.1 Failed tests:
�Error message:
�Stack trace:
More failures
|
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch Issue DetailsRun: runtime-coreclr libraries-jitstress-random 20230520.1 Failed test:
Error message:
|
This appears to be JitStress only; changing to area-CodeGen-coreclr. |
@BruceForstall is there some simple way to figure out what random seeds those older runs might have used? |
The seeds are output in the console logs, so if you can get those (easily if there are failures, or possibly via Kusto otherwise) then you can see them. |
For the most recent failure, linux-arm64 in
so this bit is likely similar to #87508 |
I can see the May 20 failure in Kusto but can't fetch the log, presumably it got purged? Any other way you can think of? |
Also looked at the 6/12 failure on win/arm64 and it also is in
|
Going to assume these are all physical promotion related, #87508 is the main issue. |
Very likely. I don't know what our retention policy is, but I think it's no more than 2-3 weeks. Once the log is gone, there's no way to get the used random number. |
Run: runtime-coreclr libraries-jitstress-random 20230520.1
Failed test:
Error message:
The text was updated successfully, but these errors were encountered: