I imagine this problem happens because 95% of github actions users are using the hosted runners (which are ubuntu if you pick linux) and for the 5% who use self-hosted runners, 95% of them use ubuntu
Top-level
I imagine this problem happens because 95% of github actions users are using the hosted runners (which are ubuntu if you pick linux) and for the 5% who use self-hosted runners, 95% of them use ubuntu 10 comments
computers were a mistake. I tried removing the "setup python" setup (figuring just having a working python installed already should be good) but then the next step fails because it can't find "python", since the binary is named "python3", and they're not symlinked together, but setup-python fixes this I'm just gonna patch lsb_release so that it says I'm on "Mozilla Debian GNU/Linux 11 (bullseye), like Ubuntu 22.04.2 LTS" fun fact: that's three different languages. four if you count the cmd.exe shell I think I'm gonna rethink our "move CI stuff to github actions" plans. This one annoyance is proving so hard to fix properly that I'm thinking it'll just be less work to go back to Jenkins so I got it "working" on github actions. and it ran for 26 minutes |
so it's just the 0.25% of us who use self-hosted runners on non-debian that are fucked