-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
CI failure in OSX x64 release NativeAOT SmokeTests SharedLibrary.sh #75005
Comments
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
I put this in the 7.0 milestone - @MichalStrehovsky would you agree? Feel free to adjust. |
We have known crashes and hangs on osx-x64. #73299 is the top one. osx-x64 is not officially supported in .NET 7. This does not need to be fixed in .NET 7. We can disable this test on osx-x64 in servicing if it becomes a problem. |
For the record, I am seeing it again in another release/7.0 PR: #75042 @jkotas @MichalStrehovsky if it's not officially supported, can you please disable the tests in 7.0? Feel free to reopen this issue so the PR resolves it. |
This started happening around the time background GC was enabled. I wonder if background GC made things worse for macOS. We can disable the test for mac but I wonder if we should consider disabling background GC on mac as well given people would still like to try using it (#61231 (comment)). If the SharedLibrary test is crashing, the GC is probably completely unusable (the test really doesn't do much besides triggering a collection). |
When trying to build locally with
Is something missing in my local setup? |
I also hit #74973 , which is probably causing the above error. |
old x64 machine seems to be able to build, but it will take time |
I am able to reproduce the failure. Somehow |
Fixed in #75298. |
See in a backport PR for release/7.0: #74894
Please determine if a fix needs to get backported to that branch.
Report
Summary
The text was updated successfully, but these errors were encountered: