Disable Mill libraries #8351
Disable Mill libraries #8351
Conversation
|
#8352 has passed so maybe the mill libs are not to blame after all. I've disabled the lampsrv43 runners since that machine has resources worth of a laptop and clearly is not meant to be used as a server. The previous slowdowns were due to that machine. Evidently drone uses that machine as a master, to dispatch the tasks to the other machines. |
|
The merge tests for #8352 passed as well: https://github.com/lampepfl/dotty/runs/458109863 This indicates that caching may not be at fault with the Mill lib failures but lack of resources. We should wait a couple of days and see whether the community build failure issue manifests itself again and hopefully close this PR. |
GH actions don't digest them well fttb
anatoliykmetyuk
force-pushed
the
anatoliykmetyuk-patch-2
branch
from
49e9138 to
c66a33e
Compare
|
Mill tests currently fail non-deterministically. So it's best that we drop them for now so that they don't block the CI migration. We can debug them separately after the higher-priority CI migration issue is resolved. |
GH actions don't digest them well fttb