-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Ubuntu-latest workflows will use Ubuntu-24.04 image #10636
Comments
The more I look at this list the more I realize that 24.04 is a step back for a lot of people. People are going to complain when this becomes the ubuntu-latest. Be aware of this and maybe make sure this communication is shown on github/azure devops But thanks for the heads up! |
ubuntu-24.04 is still labeled Will you now be removing the |
Yes @MikeMcC399 . Its updated and removed. |
@ThibaultLesuisse are you aware that NuGet refers specifically to NuGet.exe (which requires mono on Mac & Linux), as does Azure Pipeline's If you're building your projects with |
But we need NuGet.exe to sync our custom Artifacts store. And yes I know that commonly you need to run mono nuget.exe to run it on Mac/Linux. But it doesn't change the fact that a lot of tools are now missing for various reasons. This should be communicated. |
We're also affected by the removal of Mono. The official Mono repo only lists 20.04, but the package seem to work fine in newer versions–which is how the 22.04 image got Mono: runner-images/images/ubuntu/scripts/build/install-mono.sh Lines 15 to 18 in ae99c16
Is there a reason this can't be done for 24.04 as well? I tested it briefly and it's working for our relatively simple needs. Mono is fairly chunky so we'd rather not install it every single workflow run. |
…o `ubuntu-latest` ### What changes were proposed in this pull request? The pr aims to align the running OS image of `maven_test.yml` to `ubuntu-latest` (from `ubuntu-22.04` to `ubuntu-24.04`) ### Why are the changes needed? https://github.com/actions/runner-images/releases/tag/ubuntu24%2F20240922.1 <img width="627" alt="image" src="https://github.com/user-attachments/assets/f42fd7ed-c52a-4b39-9a92-02657c53d734"> After actions/runner-images#10636, `ubuntu-latest` has already pointed to `ubuntu-24.04` instead of `ubuntu-22.04`. <img width="811" alt="image" src="https://github.com/user-attachments/assets/adf6b3a8-5ca5-4daa-b35d-ea1386fa07a6"> I have checked all tasks running on `Ubuntu OS` (except for the 2 related to `TPCDS`), and they are all using `ubuntu-latest`. Currently, only `maven_test.yml` is using `ubuntu-22.04`. Let's align it. ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? Pass GA. ### Was this patch authored or co-authored using generative AI tooling? No. Closes #48263 from panbingkun/SPARK-49797. Authored-by: panbingkun <[email protected]> Signed-off-by: Dongjoon Hyun <[email protected]>
Hi there - my team is scrambling this morning due to this change. I have detailed the issue on the community forum here, but the tl;dr is that this version bump prevents Python packages from being installed for system Python. Unfortunately, it seems the evaluation of this issue was incorrect:
In fact, my team has a large number of workflows created by many different engineers, and around a dozen of our workflows that didn't previously leverage actions/setup-python now have to go through our internal change management process in order to restore stability to our CI/CD In the future, please announce breaking changes as a deprecation notice on the GitHub Blog. It's the one place we rely on to proactively catch and prevent stability issues from occurring in our pipelines |
This morning, several of our CI pipelines broke due to these changes. It would be great to have compatibility with the following dependencies, allowing us to upgrade the ubuntu version in the future without complicating our pipelines 🙇 .
|
When gh moved `ubuntu-latest` to `24.04` actions/runner-images#10636 our tests started to timeout on finding status bar. Use older version for now before we will know why this happened. commit-id:9c5625cb
Ieakeystore bank account $100.000 to be use and set up website to be able so that Clifton rone only to use on and website |
Would you please drop the annotation saying "ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see #10636" ? It is supposed to be completed and generated a lot of noise on every single GHA. |
The `qemu-efi` package is absent after upgrade. Rollout is in progress: actions/runner-images#10636
* remove unused try_into impl * align tests * get rid of FailedWithdrawalResolution * report status of processing request * manual refund for failed deposits * trigger maintenance mode of cancel_resolution failure * bump sdk * apply formatting * [MGX-1369] connect with jira * [MGX-1193] connect with jira * remove not needed test * add new group of tests * [MGX-1370] Align manual batches * Test for specific behaviour agreed with product team * [MGX-1366] - BEX - Maintanance mode alignments * align formatting * add: disable mocks in tests on demand * test_sequencer_updates_are_ignored_and_removed_in_maintanance_mode * align maintanance mode behaviour * test that same l1update can be provided again if was skipped in maintanance mode * feat: Add multi-platform Docker image build for arm64 platform support MGX-1326 (#792) • Support multiple architecture builds • Improve cross-platform compatibility MGX-1326 * return read rights while skipping sequencer updates in maintanance mode * Provide specific error when withdraw not existing token * extract helpers methods for batch creation * [MGX-1366] - add 'force_create_batch' * [MGX-1417] Only deposit recipient can refund failed deposit * typo 'TokenDoestNotExist' -> 'TokenDoesNotExist' * [MGX-1184] Store prometheus metrics as u128 * [MGX-1220] Make sure that MaxSequencers limits is applied per chain * [MGX-1220] new 'StakeAction' parameter that determines wheter sequencer is expected to join active set * Update Gasp erc20 address for test environment * [MGX-1189] BEX - Contract/Node - Event observability * trigger ci * add 'StakeRemoved' event * Align protocol messages with ferries * issuance for sequencers, sequencer rewards, withdraw fee in rolldown (#803) + modify issuance to add sequencer vaault + modify sequnecer staking to add rewards + modify staking to call sequncer payout hook + modify rolldown to add sequencer update authorship hook for rewards + modify rolldown to add flat withdraw fee + modify bunch of mocks to impl issuance changes * rename group * ci: add multiplatform image build for fast runtime image (#809) * deposit ferry impl * support ferries of failed deposits * add tests for abi compatiblity * implement ConvertBack for address converter * add: ferry_deposit_unsafe * add: update_hash parameter for update_l2_from_l1 * reject updates with wrong hash * rename 'NotMangataLiquidityAsset' => 'NotPairedWithNativeAsset' * fix cancel rights settlement * Feature/upgrades (#811) * do not allow for ferry deposits that were already ferried * add test group * [MGX-1123] change withdraw fee to per chain vs const (#818) * [MGX-1443] Feature/foundation membership (#819) add membership pallet used to manage foundation members only allowed method is for the member to change his key * split withdrawal rolldown tests * update token address * use type prefix when calculating the L2Request hash * Revert "[GASP-1564] Include request type in request hash calculation" * use type prefix when calculating the L2Request hash * make rpc api return purly encoded structs * prove that aliases can be freed up * [FIX] produce batches even when all sequencers have left * limit manual batch size with the AutomaticBatchSize * fix typo * add group * Reproduce problem reported by audit company * fix: sequencer alias cleanup * Feature/rolldown benchmarks (#831) Rolldown benchmarks * fix cargo refs (#834) fix cargo refs * added offset to VerExtrinsicBaseWeight and FeeLockWeight to xyk extri… (#837) added offset to VerExtrinsicBaseWeight and FeeLockWeight to xyk extrinsics * checkpoint * compiled * all compiles * unit tests passes * ut & benchmarks works * allign tests * simplify * on_idle hook * on_idle hook * properly account for corner case scenario * on_idle hook fixed * allign tests * remove outdated comment * account for big reads/writes * base integration (#839) base integration * different dispute period per l1 * different dispute period per l1 * tests for dispute period set * [GASP-1632] - stop processing on first failed request * allign with base * configure features * adjust dispute period * Feature/stable pool mgx 1307 (#838) Co-authored-by: Marian Vanderka <[email protected]> * fix update validation * Feature/market improvs (#845) - RPC add calc_price_impact variant - fix swap buy call missing in feelock filter - adjust create pool to infer fixed rate from initial deposit * GASP-1625 Feature/locked tokens (#841) adds checks for non transferable tokens `--features=unlocked` removes such restrictions runtime cofing defines the native currency - `0` as non transferable token tokens all transfer calls, set_balance, mint extrinsics are checked market create, mint, burn are checked market swaps are allowed foundation members have veto over: market create_pool & burn * expose feature in cargo, and disable for fast-runtime * apply benchmarks * revert changes to pallet vesting * Added chain genesis salt to system genesis (#848) * CI: Add additionoal unlocked runtime image build in CI (#850) Introduce a separate build process for Docker images with an unlocked runtime, along with the necessary adjustments to export WASM artifacts and manage image manifests. * bumped gaspErc20Mock addresses in chain spec (#852) * fixes gasp-1666 gasp-1671 (#851) limit withdrawals recipient to sender's address for nontransferable tokens ensure withdraw amount >= ferry tip * adds maintenance check for ferry deposit calls (#846) * Use -unrestricted for e2e non-fast tests (#849) * Fix/seq dies (#853) * Fix/rewards notransfer GASP-1688 (#857) * adds a check that only single ferry can happen on a deposit request gasp-1652 (#858) * Fix/market mint ratio gasp-1689 (#859) fix calculate expected method fix mint liq to respect fixed ratio fix tests * remove patch * Fix/rewards market GASP-1681 (#855) * fixes the symbol naming for liq pools (#860) * safety precautions for on_idle hook * fixe while loop causing crash & add u512 to avoid overflows for maxxe… (#865) + adjust bench to use unbalanced values + add minmax pool test * Fix/mint activate lp gasp-1712 (#866) * minimal set of changes to disable sequencer registration for non sudo users * runtime parameters modifications * duplicate existing config * ethereum-mainnet chainspec * working chainspec * foundation accounts * council accounts * update issuance config * adjust issuance config * adjust values to avoid zero devision * set immediate release of TGE - not used either way * adjust issuance so 5M of GASP is minted in genesis block & account for it in issuance config * update node url * adjust minimum stake amount * fix execution queue progression * revert sequencers balances * fix pallet-sequencer-staking tests * fix integration tests * align rolldown benchmarks * fix formatting * 1st Runtime Upgrade on Rollup Prod Alphanet: Issuance Edits (#876) 1st Runtime Upgrade on Rollup Prod Alphanet Changed issuance behaviour and changed issuance config Bumped spec_version and impl_version * minor fixes * remove dummy test * fix execute_tge benchmarks * add missing check * fix formatting * fix * move to gasp-node subdir for monorepo * adds gasp-node workflow * ci: update GHA workflows to run `gasp-node` build and tests on opened pull requests * fix: update permissions in reusable-gasp-node-e2e-tests GHA workflow * fix: update Docker login secrets in reusable GHA workflow * ci: update job names in GitHub Actions workflows for clarity and consistency * fix: update JOB_CACHE_PREFIX and add context for gasp-node in reusable build workflow * chore: test if workflows will work without extra setup-gcloud step * feat: add rust-toolchain.toml for `gasp-node` * Revert "chore: test if workflows will work without extra setup-gcloud step" This reverts commit 964ce24. * feat: add rust-src component to rust-toolchain.toml for gasp-node * fix: add actions/checkout step for multiplatform image generation job to fix integration with global working-directory config * chore: update JOB_CACHE_PREFIX for gasp-node in reusable workflow * fix: update Docker build context paths in reusable gasp-node workflow to use git default context * feat: merge `stash` service builds to main workflow * Revert "fix: update Docker build context paths in reusable gasp-node workflow to use git default context" This reverts commit 36cb10d. * ci: merge foundry smart contracts checks into the main build and test reusable workflow * fix: foundry-toolchain version reference * fix: update job name in reusable build and test workflow * fix: add missing bun install step in reusable build and test workflow * chore: temporary disable `bun run analyze:ci` * feat: add `slither-action` usage for `contracts` checks * ci: move `stash` build to reusable-build-and-test.yml and rearrange `contracts` check stesp * ci: add `reusable-gasp-node-performance-tests.yml` workflow for future integration into the workflows * fix: syntax warnings * chore: rearrange jobs sequence * feat: add workflow updates for `branch-main.yml` workflow to support `mangata-node` builds * fix: gasp-node generate types jobs * fix: add proper permissions for `slither-action` operation * chore: update AVS services build job name for clarity in GHA workflows * chore: revert temporary changes to test `branch-main.yml` workflow * chore: get rid of annoying GHA warnings caused by some bug More details here: actions/runner-images#10636 * fix: wasm artifact upload paths * chore: debug var * Revert "chore: debug var" This reverts commit 495d01c. * fix: gasp-node image version propagation to generate-types workflow * chore: temporary disable longest jobs * chore: remove redundant configs from `gasp-node` codebase * fix: NODE_DOCKER_IMAGE variable reference for reusable-gasp-node-e2e-tests.yml * Revert "chore: temporary disable longest jobs" This reverts commit ecd70ba. * fix: set working directory for gasp-node in reusable-gasp-node-e2e-tests.yml * fix: update default branch for e2e tests to eth-rollup-develop * fix: use new var to set correct gasp-node docker compose network when running e2e tests * fix: remove redundant variables from e2e workflow * ci: rearrange jobs sequencing for gasp-node buiild to save a few minutes * fix: jobs permission propagation * feat: prepare reusable-rust-build.yml to support gasp-node builds * feat: move gasp-node unit tests and coverage report runs to separate reusable job * revert: put back the eth-rollup-develop branch to be used for fetching gasp-xyz/gasp-e2e repo within workflow * [GASP-1840] Root configurable issuance config (#878) * [gasp-1863] Feature/transfer allowlist (#882) gasp-node has a new membership pallet that allows following calls for ROOT: add_member, remove_member, swap_member, reset_mebers set_prime, clear_prime are disabled orml tokens pallet adds an allowlist that overrides non-transferablitiy for following methods: transfer, transfer_keep_alive, transfer_all force_transfer(origin, from, to, ...) does an allowlist check on the from param * [GASP-1826] reverts swap trx fees (#877) swaps always pays commission min fee fix fee goes to trsy, bnb, pool fix valuation where it applies to the real, not predicted swap value --------- Co-authored-by: goncer <[email protected]> --------- Co-authored-by: Mateusz Nowakowski <[email protected]> Co-authored-by: Aleksandr Chetverov <[email protected]> Co-authored-by: AlexChetverov <[email protected]> Co-authored-by: mateuszaaa <[email protected]> Co-authored-by: Misha Kolesnik <[email protected]> Co-authored-by: mateuszaaa <[email protected]> Co-authored-by: iStrike7 <[email protected]> Co-authored-by: goncer <[email protected]>
The release of `2.24.0rc2` failed: https://github.com/pantsbuild/pants/actions/runs/12909883768/job/36005845441#step:3:19 ``` Version 3.7 was not found in the local cache Error: The version '3.7' with architecture 'x64' was not found for Ubuntu 24.04. The list of all available versions can be found here: https://raw.githubusercontent.com/actions/python-versions/main/versions-manifest.json ``` This is because the `publish` step was running on `ubuntu-latest` which GitHub recently switched from Ubuntu 24 to 22. actions/runner-images#10636 Which has a different set of GitHub Python versions <https://github.com/actions/python-versions> available. Setting to an explicit image version lets us control the upgrade cadence instead of rugs being pulled out from under.
The release of `2.24.0rc2` failed: https://github.com/pantsbuild/pants/actions/runs/12909883768/job/36005845441#step:3:19 ``` Version 3.7 was not found in the local cache Error: The version '3.7' with architecture 'x64' was not found for Ubuntu 24.04. The list of all available versions can be found here: https://raw.githubusercontent.com/actions/python-versions/main/versions-manifest.json ``` This is because the `publish` step was running on `ubuntu-latest` which GitHub recently switched from Ubuntu 24 to 22. actions/runner-images#10636 Which has a different set of GitHub Python versions <https://github.com/actions/python-versions> available. Setting to an explicit image version lets us control the upgrade cadence instead of rugs being pulled out from under.
The release of `2.24.0rc2` failed: https://github.com/pantsbuild/pants/actions/runs/12909883768/job/36005845441#step:3:19 ``` Version 3.7 was not found in the local cache Error: The version '3.7' with architecture 'x64' was not found for Ubuntu 24.04. The list of all available versions can be found here: https://raw.githubusercontent.com/actions/python-versions/main/versions-manifest.json ``` This is because the `publish` step was running on `ubuntu-latest` which GitHub recently switched from Ubuntu 24 to 22. actions/runner-images#10636 Which has a different set of GitHub Python versions <https://github.com/actions/python-versions> available. Setting to an explicit image version lets us control the upgrade cadence instead of rugs being pulled out from under.
The release of `2.24.0rc2` failed: https://github.com/pantsbuild/pants/actions/runs/12909883768/job/36005845441#step:3:19 ``` Version 3.7 was not found in the local cache Error: The version '3.7' with architecture 'x64' was not found for Ubuntu 24.04. The list of all available versions can be found here: https://raw.githubusercontent.com/actions/python-versions/main/versions-manifest.json ``` This is because the `publish` step was running on `ubuntu-latest` which GitHub recently switched from Ubuntu 24 to 22. actions/runner-images#10636 Which has a different set of GitHub Python versions <https://github.com/actions/python-versions> available. Setting to an explicit image version lets us control the upgrade cadence instead of rugs being pulled out from under.
The release of `2.24.0rc2` failed: https://github.com/pantsbuild/pants/actions/runs/12909883768/job/36005845441#step:3:19 ``` Version 3.7 was not found in the local cache Error: The version '3.7' with architecture 'x64' was not found for Ubuntu 24.04. The list of all available versions can be found here: https://raw.githubusercontent.com/actions/python-versions/main/versions-manifest.json ``` This is because the `publish` step was running on `ubuntu-latest` which GitHub recently switched from Ubuntu 24 to 22. actions/runner-images#10636 Which has a different set of GitHub Python versions <https://github.com/actions/python-versions> available. Setting to an explicit image version lets us control the upgrade cadence instead of rugs being pulled out from under. Co-authored-by: cburroughs <[email protected]>
The release of `2.24.0rc2` failed: https://github.com/pantsbuild/pants/actions/runs/12909883768/job/36005845441#step:3:19 ``` Version 3.7 was not found in the local cache Error: The version '3.7' with architecture 'x64' was not found for Ubuntu 24.04. The list of all available versions can be found here: https://raw.githubusercontent.com/actions/python-versions/main/versions-manifest.json ``` This is because the `publish` step was running on `ubuntu-latest` which GitHub recently switched from Ubuntu 24 to 22. actions/runner-images#10636 Which has a different set of GitHub Python versions <https://github.com/actions/python-versions> available. Setting to an explicit image version lets us control the upgrade cadence instead of rugs being pulled out from under. Co-authored-by: cburroughs <[email protected]>
Hi |
base on this ticket the rollout is already completed. I wonder in the github action we still see the warning message.
may I know when will this warning message be removed ? |
… For more details, see actions/runner-images#10636
Rollout will begin on December 5th and will complete on January 17th, 2025.
Breaking changes
Ubuntu 24.04 is ready to be the default version for the "ubuntu-latest" label in GitHub Actions and Azure DevOps.
Target date
This change will be rolled out over a period of several weeks beginning December 5th and will complete on January 17th, 2025.
The motivation for the changes
GitHub Actions and Azure DevOps have supported Ubuntu 24.04 in preview mode since May 2024, and starting from July 2024 Ubuntu 24.04 is generally available for all customers. We have monitored customer feedback to improve the Ubuntu 24.04 image stability and now we are ready to set it as the latest. There are a set of packages listed below that we have removed from the Ubuntu 24 image. Please review the list carefully to see if you will be impacted by these changes. We have made cuts to the list of packages so that we can maintain our SLA for free disk space. The images have grown so large we are in danger of violating our SLA if we keep the package list as-is.
The factors we took into consideration when removing packages are as follows:
We understand that our reasoning may not make sense to some of you out there, but please bear in mind that we tried to keep disruptions as minimal as possible, and tried to keep the best interests of the community at large in mind. There is a very large and diverse community using our images, and as much as we would like to, we cannot pre-install every tool on these images.
Platforms affected
Mitigation ways
Steps or options for impact mitigation
If you see any issues with your workflows during transition period:
runs-on: ubuntu-22.04
We support two latest LTS Ubuntu versions, so Ubuntu 22 will still be maintained for the next 2 years.Software Differences
The Ubuntu 22.04 image has a different set of software than Ubuntu 24.04. The most significant changes are listed in the table below:
The text was updated successfully, but these errors were encountered: