-
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: baseservices\\threading\\interlocked\\add\\InterlockedAddInt_2\\InterlockedAddInt_2.cmd #44139
Comments
CC @briansull |
We have a lot of similar issues: Most likely some kind of infrastructure issue due to file locking. |
Seems like we should add some more checking/retry logic. E.g., make sure the .dasm.il file exists before assembling, then retrying once or twice (after waiting) if it fails with a "Could not open" error. Maybe ildasm crashed and it actually doesn't exist? |
@BruceForstall Do you or anyone else understand how this IlAsm/IlDasm roundtrip testing is supposed to work?
Then this part of the script will be run:
|
fyi, that logic comes from https://github.com/dotnet/runtime/blob/6553a49e1b501cd3c40ef64999475fecad1c9f19/src/tests/Common/CLRTest.Execute.Batch.targets I was thinking we add something like:
of course, it has to be implemented for both Linux/bash and Windows/cmd. |
The issue could also be |
All of the reported failure are on Windows, I'm not sure if we are running IlDasm/IlAsm roundtrip testing on Linux. |
I built the Priority=1 tests locally and ran this test 100 times on my system |
Fixed with #46765 |
failed in job: runtime-coreclr ilasm 20201031.1
CoreCLR Windows_NT arm64 Checked ilasmroundtrip @ Windows.10.Arm64v8.Open
Error message
The text was updated successfully, but these errors were encountered: