-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Github actions fails after new VMs deployed #9733
Comments
Can confirm, I am getting the same error on my workflow runs. |
Seems to be the same as reported in microsoft/linux-package-repositories#130. |
We are getting this as well on all our repos. |
same for us |
Same issue on our repos. |
We got same issues in Github Actions that using ubuntu-latest. |
content-length: 0
|
same here on ubuntu latest |
For myself added |
Some workarounds we've seen are adding |
same here too 🥹 |
Same issue for us too. Changing 'runs-on: latest' to 'runs-on: ubuntu-20.04' helped. |
Actually
won't help because apt index would be incomplete and the error to be ignored. The problem is not in the image itself but in the Microsoft's apt repo, we are reaching them out. the better workaround would be the following snippet of code:
|
Failure being related to a broken Microsoft repository we don't need, we just needed to implement work-around from: actions/runner-images#9733 (comment)
strange my browser can fetch |
until actions/runner-images#9733 is fixed.
Running `playwright install --with-deps` fails because it executes `apt update` in the background, which is failing on the `latest ubuntu-22.04` image release. Related to [Issue #9733](actions/runner-images#9733). Thanks to the temporary fix provided [here](actions/runner-images#9733 (comment)) 🙌.
Upgrade Playwright to 1.43.1 and apply temporary fix to the global GitHub issue (actions/runner-images#9733)
It's a workaround for GHA issue. Ref. actions/runner-images#9733
Update 13:10 UTC issue has been reported fixedWe are keeping an eye |
Seems to be fixed, our runners work as intended. |
It's a workaround for GHA issue. Ref. actions/runner-images#9733
Our github actions are now working as intended, the issue seems fixed for us |
This reverts commit 04a395c.
We got confirmation that the issue has been fully addressed, closing now! |
This reverts commit 0e22a5e.
* [misc]: Add TWError, TWResult, TWErrorKind, and traits * Use `TWError` in `tw_coin_entry` * [misc]: Return SigningError, SigningResult back, make TWError<E> generic * [misc]: Add `tw_aptos` error contexts * [misc]: Add `tw_sui` error contexts * [misc]: Simplify `TWError` casts, add tests * [misc]: Add contexts in `tw_cosmos_sdk` * [misc]: Add contexts in `tw_evm` * [misc]: Fix compilation of `tw_ethereum`, `tw_ronin`, `tw_bitcoin`, `tw_native_evmos`, `tw_native_injective`, `tw_thorchain` * [misc]: Add error contexts in `tw_solana` * [misc]: Fix `tw_bitcoin` compilation errors * [misc]: Add error contexts to `tw_greenfield` * [misc]: Fix other compilation errors * [CI] Trigger CI * [codegen-v2]: Fix Rust codegen templates * [misc]: Add `TWError` doc comments * [CI]: Apply a workaround * [CI]: Apply a work around actions/runner-images#9733 * [CI]: Try to disable workaround * [CI]: Try to disable workaround * [CI]: Fix broken dependencies cache * [CI]: Apply the changes for linux-sampleapp-ci.yml
This reverts commit d82b682.
Upstream: - issue -- actions/runner-images#9733 - code snippet -- actions/runner-images#9733 (comment)
* [misc]: Add TWError, TWResult, TWErrorKind, and traits * Use `TWError` in `tw_coin_entry` * [misc]: Return SigningError, SigningResult back, make TWError<E> generic * [misc]: Add `tw_aptos` error contexts * [misc]: Add `tw_sui` error contexts * [misc]: Simplify `TWError` casts, add tests * [misc]: Add contexts in `tw_cosmos_sdk` * [misc]: Add contexts in `tw_evm` * [misc]: Fix compilation of `tw_ethereum`, `tw_ronin`, `tw_bitcoin`, `tw_native_evmos`, `tw_native_injective`, `tw_thorchain` * [misc]: Add error contexts in `tw_solana` * [misc]: Fix `tw_bitcoin` compilation errors * [misc]: Add error contexts to `tw_greenfield` * [misc]: Fix other compilation errors * [CI] Trigger CI * [codegen-v2]: Fix Rust codegen templates * [misc]: Add `TWError` doc comments * [CI]: Apply a workaround * [CI]: Apply a work around actions/runner-images#9733 * [CI]: Try to disable workaround * [CI]: Try to disable workaround * [CI]: Fix broken dependencies cache * [CI]: Apply the changes for linux-sampleapp-ci.yml
* [misc]: Add TWError, TWResult, TWErrorKind, and traits * Use `TWError` in `tw_coin_entry` * [misc]: Return SigningError, SigningResult back, make TWError<E> generic * [misc]: Add `tw_aptos` error contexts * [misc]: Add `tw_sui` error contexts * [misc]: Simplify `TWError` casts, add tests * [misc]: Add contexts in `tw_cosmos_sdk` * [misc]: Add contexts in `tw_evm` * [misc]: Fix compilation of `tw_ethereum`, `tw_ronin`, `tw_bitcoin`, `tw_native_evmos`, `tw_native_injective`, `tw_thorchain` * [misc]: Add error contexts in `tw_solana` * [misc]: Fix `tw_bitcoin` compilation errors * [misc]: Add error contexts to `tw_greenfield` * [misc]: Fix other compilation errors * [CI] Trigger CI * [codegen-v2]: Fix Rust codegen templates * [misc]: Add `TWError` doc comments * [CI]: Apply a workaround * [CI]: Apply a work around actions/runner-images#9733 * [CI]: Try to disable workaround * [CI]: Try to disable workaround * [CI]: Fix broken dependencies cache * [CI]: Apply the changes for linux-sampleapp-ci.yml
Description
When running github actions when the VMs are in active deployment the github actions fail.
Taken from workflow actions log.
Please disable action running, while VM is deploying or only allow queuing.
Platforms affected
Runner images affected
Image version and build link
Ubuntu LTS
Is it regression?
Not sure
Expected behavior
Either do not run the GitHub workflow or make it queue.
Actual behavior
Workflows fail.
Repro steps
apt update
as workflow stepTemporary Workaround
Actually
sudo apt-get update || true
won't help because apt index would be incomplete and the error to be ignored.
The problem is not in the image itself but in the Microsoft's apt repo, we are reaching them out.
the better workaround would be the following snippet of code:
Update 13:10 UTC issue has been reported fixed
We are keeping an eye
The text was updated successfully, but these errors were encountered: