Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Run Build (x86_64-unknown-linux-gnu) job #61

Closed
DervexDev opened this issue May 2, 2024 · 8 comments · Fixed by #62
Closed

Run Build (x86_64-unknown-linux-gnu) job #61

DervexDev opened this issue May 2, 2024 · 8 comments · Fixed by #62

Comments

@DervexDev
Copy link
Contributor

This job is waiting to run for over 40 minutes now. This causes all GitHub workflows using setup-aftman action to fail as it uses the latest tag by default.

@LPGhatguy
Copy link
Owner

Super cursed GitHub Actions issue. I just restarted the action to see if it'll actually run this time.

@DervexDev
Copy link
Contributor Author

Yeah that's probably GitHub's fault. I had a very similar issue some time ago.

@filiptibell
Copy link
Contributor

Looks like it isn't starting because it's requesting an ubuntu-18.04 runner and waiting for one to become available. Those runners were removed some time ago: https://github.blog/changelog/2022-08-09-github-actions-the-ubuntu-18-04-actions-runner-image-is-being-deprecated-and-will-be-removed-by-12-1-22/

@LPGhatguy
Copy link
Owner

LPGhatguy commented May 2, 2024

Hah, cool. I'll see if I can patch a fix in without blowing things up too badly.

I remember we chose 18.04 specifically because of some funny libc/OpenSSL compat issues.

@DervexDev
Copy link
Contributor Author

We could use reqwest with the rustls-tls feature. It builds just fine on ubuntu-latest.

@LPGhatguy
Copy link
Owner

LPGhatguy commented May 2, 2024

For the time being, I've deleted the v0.2.8 release. The new action has created a new draft release that will go live when it's ready.

If someone wants to PR the rustls-tls feature change (it should be small!) I'm down to get that in a follow-up release.

@LPGhatguy
Copy link
Owner

Alright, this issue should be resolved for the v0.2.8 release.

@DervexDev
Copy link
Contributor Author

Just opened #62

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants