https://pantsbuild.org/ logo
Join Slack
Powered by
Ugh, our Linux ARM CI server is going away today, ...
# development
h
Ugh, our Linux ARM CI server is going away today, and our request for GitHub Actions runners has not had a response yet. I will I guess have to set something up on AWS. Maybe can free up some budget for this by moving our MacOS x86 builds back to GitHub hosted runners.
b
Oh, no! Thanks for being across that. Re macOS CI it seems GH just published today that they’re deprecating macOS 12: https://github.blog/changelog/2024-08-19-notice-of-upcoming-deprecations-and-breaking-changes-in-github-actions-runners/ Which changes the supported-devices calculation in https://github.com/pantsbuild/pants/issues/21074
Sounds like we should try to land some deprecations of these old platforms sooner rather than later, given how fiddly they’re becoming to support! I can try to look at this, but am pretty time limited
h
Yeah, I’ll take a look at it, but probably 2.22.x should be the last Pants version to officially support macOS12 ?
I mean, if someone wants it they can always build it themselves for that platform
plus, it may just work even if built on a later macos version?
I just don’t want us to have to support it
👍 2
p
Not sure if you've seen Ubicloud, but they have an easy setup for cheaper runners than GHA
👀 1
h
I will look at them, thanks. I’m also looking at RunsOn, which is similar-sounding
✅ 1
Damn, and now begins the slog of setting up the runners appropriately…
OK, installing python3.9 was an easy hurdle, now things seem to be rolling along, keep those fingers crossed…
🤞 2
Well, pants built on the shard, but then couldn’t run due to
Copy code
/home/runner/.cache/pants/pants_dev_deps/70ca84525a818e4a1799fe6feeb85275f90234f9.venv/bin/python: error while loading shared libraries: libpython3.9.so.1.0: cannot open shared object file: No such file or directory
Fortunately it is possible to SSH into the runner
Erk, well, it was while it was running
It’s getting late so I will have to pick this up tomorrow
b
thanks for getting it rolling!
Re macOS: I’ve started the deprecation in https://github.com/pantsbuild/pants/pull/21326.
h
back to chasing down why LD_LIBRARY_PATH isn’t propagated everywhere it should be
OK, looks like what we need a custom AMI, which we actually already have. BUT - the runs-on configuration has to be in main, which means we will need to merge it without green CI. But fortunately it’s just a new toml file that affects nothing in our repo.
OK, this should go green now, but please don’t merge it for me, as we first need to merge the runs-on config into the branches
This is now in main, so CI is back up for main. I will be merging into 2.20x, 2.21.x and 2.22.x as soon as the PRs go green.
b
thank you for getting that done!
h
I will write up the manual part of creating the AMI
Gotta say, I’m quite impressed by runs-on, it was very easy to set up, and it’s fantastic that it creates ec2 instances on the fly, as needed, and then terminates them. So the cost control for something intermittent like CI is really beneficial.
👍 1
b
awesome (coincidentally I've been trying to find time to roll it out at work, hoping for benefits like that, so nice to have a testimonial I properly trust 🙂 )
🎉 1
i hit the merge buttons on all the cherry-picks, so we're unblocked on all branches again
21 Views
Open in Slack
PreviousNext
Powered by