Repository navigation
test: removing mac-aarch64 from the CI job + re-adding TagBot.yml - #501
Conversation
It is too unreliable, presumably because not enough RAM on remote server.
|
Let's try |
mac-aarch64 from the CI jobmac-aarch64 is allowed to failed on CI
|
Yeah it's common that the jobs are just cancelled like right now, I think because of the capacity constraints. Very noisy. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #501 +/- ##
==========================================
+ Coverage 97.25% 97.29% +0.04%
==========================================
Files 28 28
Lines 7093 7093
==========================================
+ Hits 6898 6901 +3
+ Misses 195 192 -3
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Since the `juliaci.yml` workflow no longer trigger the TagBot, let's try the old way.
mac-aarch64 is allowed to failed on CImac-aarch64 is allowed to failed on CI + re-adding TagBot.yml
The windows CI just crashed with a OOM error, let's retry this option
|
The |
mac-aarch64 is allowed to failed on CI + re-adding TagBot.ymlmac-aarch64 from the CI job + re-adding TagBot.yml
It's cool and all to test on all the official platform supported by Julia, but the provided server is too low on RAM (I think 8 GB) and running the test suite here require a lot of RAM. This is likely the cause of the random fails for this job.
The fails are too common and I'm tired of manually re-triggering this job, let's remove this matrix for now.