GHA CI migration#1553
Conversation
tomt1664
force-pushed
the
gha_ci_migration
branch
2 times, most recently
from
7814a9d to
a1cb489
Compare
|
Seeing a failure on the macos 13 task which looks git related, not sure if that's what's stopping the other tasks from running? |
tomt1664
force-pushed
the
gha_ci_migration
branch
from
a1cb489 to
9b065d5
Compare
|
Squashed all the commits. The failure seems to be due to the Merge base branch step which apparently not be needed with actions/checkout@v4 |
tomt1664
force-pushed
the
gha_ci_migration
branch
from
afdeecb to
9cd01a1
Compare
|
All jobs should now pass.
|
tomt1664
force-pushed
the
gha_ci_migration
branch
from
9cd01a1 to
9247676
Compare
delta1
left a comment
delta1
left a comment
There was a problem hiding this comment.
Left a few comments, nothing major
|
Just waiting on CI to finish |
|
This looks great, thanks @tomt1664 ! Please squash into the top 2 commits and then I'll merge |
tomt1664
force-pushed
the
gha_ci_migration
branch
from
59c3377 to
0331feb
Compare
| DEBIAN_FRONTEND: noninteractive | ||
| run: | | ||
| set +o errexit | ||
| sudo bash -c '(ionice -c 3 nice -n 19 rm -rf /usr/share/dotnet/ /usr/local/graalvm/ /usr/local/.ghcup/ /usr/local/share/powershell /usr/local/share/chromium /usr/local/lib/android /usr/local/lib/node_modules)&' |
There was a problem hiding this comment.
Is clear-files used? I don't see it in ci.yml. Anyway, if its unused it can be removed in a follow-up
2 participants
Migration of Elements CI from Cirrus (which is closing 1st June) to Github actions.
Notes:
GHA runners have IPV6 disabled in their linux containers. So
feature_proxy.pyandrpc_blind.py --ipv6disabled for these, as in bitcoin/bitcoin#30193windows-2019is being deprecated and no runners appear to be readily available. actions/runner-images#12045 (consider changing towindows-2022) forwin64-msvcjobs.previous-releasesrequires a persistent self-hosted runner. This job was being skipped by Cirrus (withNo public persistent worker pools found!).