-
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
Can_Run_App_With_StatiHost installer test failure in CI #42101
Comments
Tagging subscribers to this area: @vitek-karas, @agocke |
I have what may be the same issue, with an extra clue - @vitek-karas does this help?
This is in 5.0 branch |
@jaredpar if this is rare, but did break a CI job, is it appropriate to set 'blocking-clean-ci' or is that just for more common issues? Also, how to notify runfo about it so that it autolinks when it happens again? |
Also note this was Installer-coreclr-Linux_musl_x64-Release |
This message apparently means that we are trying to execute an executable while it is being modified - apparently in its text section. |
This is failing about once a day right now so blocking clean CI is appropriate here. |
OK, that's a good rule of thumb.. |
@agocke could someone maybe take a look? |
failed again in job: runtime 20201217.40 failed test: Can_Run_App_With_StatiHost Installer-coreclr-Linux_x64-Release Error message
|
Removing blocking tag due to low incidence cc: @agocke |
Failed again in runtime 20210601.76 Failed test:
Error message:
|
Happening every 3rd day for this test, but IIRC there were other tests with this issue. |
We've fundamentally changed how single-file tests work over the past year or two (in a way that should help with reliability). Closing this - we'll track any new failures separately. |
In my PR, the test has failed with the following stack trace:
It looks similar to #35068
Runfo Tracking Issue: Runtime test Can_Run_App_With_StatiHost
Build Result Summary
The text was updated successfully, but these errors were encountered: