-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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 suite failures on aarch64-darwin #43614
Comments
You shouldn't be surprised: this platform is in tier-3 support, which by definition means
There are already plenty of tickets reporting issues for apple silicon, including #43321 which is a similar ticket reporting a grab bag of problems. Some of them had been already addressed before you opened this issue. For example, |
Understood. How should I go about reporting these failures then? Should I create separate GH issues for each one (skipping those that have already been reported ofc)? |
Is there anything different than #43321? This looks a duplicate of that ticket, no? |
I don't see any of the segfaults reported in #43321, but perhaps I'm missing something? |
Many segfaults on the M1 are related to #41440 |
Ah, understood. I'll try rerunning things on latest master. Out of curiosity, is there an ETA for getting aarch64-darwin support to tier 1 or 2? |
No |
After downloading the official dmg from the website, I was surprised to find that the test suite does not pass on aarch64-darwin (aka M1 aka apple silicon aka macOS on ARM etc). I ran
bin/julia --check-bounds=yes --startup-file=no --depwarn=error share/julia/test/runtests.jl
from the Contents/Resources/julia directory. To summarize I'm seeing the following failures:KILLING BY QUICK KILL WATCHDOG
warning/messageYou can view the full logs here: https://gist.github.com/samuela/b24439841ecd52cc201dd1a60d3b1d6f. The whole test suite ran in about 20 minutes for me on the 10-core M1 Max.
Related: #36617
The text was updated successfully, but these errors were encountered: