Skip to content

[CI] Upgraded Actions #2568

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

Conversation

AlexandreSinger
Copy link
Contributor

@AlexandreSinger AlexandreSinger commented May 29, 2024

The Annotations section of the CI was full of deprecation warnings:
image

Node.js 16 actions were deprecated. Upgraded setup-python, checkout, and upload-artifact to their most recent version. See: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/

v3 of upload-artifact was also deprecated. v4 claims to be 98% faster, however, may come with some breaking changes. Pertaining to us, artifacts cannot have the same name now and there is a limit of 500 artifacts. See:
https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/

Upgrade summary:

  • actions/setup-python@v4 -> actions/setup-python@v5
  • actions/checkout@v3 -> actions/checkout@v4
  • actions/upload-artifact@v3 -> actions/upload-artifact@v4

NOTE: Had to leave the nightly tests behind since the self-hosted
machine does not support node20. Need to upgrade the machine in order to
upgrade these actions.

@github-actions github-actions bot added the infra Project Infrastructure label May 29, 2024
@AlexandreSinger AlexandreSinger force-pushed the feature-upgrade-ci-actions branch from 9e9e62a to 7de3875 Compare May 30, 2024 15:34
The Annotations section of the CI was full of deprecation warnings.

Node.js 16 actions were deprecated. Upgraded setup-python, checkout, and
upload-artifact to their most recent version. See:
https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/

v3 of upload-artifact was also deprecated. v4 claims to be 98% faster,
however, may come with some breaking changes. Pertaining to us,
artifacts cannot have the same name now and there is a limit of 500
artifacts. See:
https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/

NOTE: Had to leave the nightly tests behind since the self-hosted
machine does not support node20. Need to upgrade the machine in order to
upgrade these actions.
@AlexandreSinger AlexandreSinger force-pushed the feature-upgrade-ci-actions branch from 7de3875 to 4dd51dd Compare May 30, 2024 15:45
@AlexandreSinger
Copy link
Contributor Author

@vaughnbetz What do you think about these changes? This has removed most of the warnings except for 1, which I put a comment in the CI code with a TODO regarding upgrading the self-hosted runners:
image

This also made it easier to download artifacts for the nightly tests since it now separates them out into their own artifacts:
image

@vaughnbetz
Copy link
Contributor

vaughnbetz commented May 31, 2024

Sounds great -- thanks! Merging these in. Upgrading the self-hosted ones before node 16 goes away forever is definitely a good idea too. Not sure what we have to do to make that happen, and if we need Herman's help (since it is on a google cloud machine).

@vaughnbetz vaughnbetz merged commit cca8d76 into verilog-to-routing:master May 31, 2024
53 checks passed
@@ -71,9 +73,12 @@ jobs:
VTR_CMAKE_PARAMS: ${{ matrix.cmake }}
NUM_CORES: ${{ matrix.cores }}

- uses: actions/upload-artifact@v3
if: ${{ always() }}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this line should not have been removed.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@AlexandreSinger : what do you think? Should this go back in?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@soheilshahrouz @vaughnbetz My bad... I misunderstood what this was trying to do. Perhaps in the future we should consider a better keyword to use:
https://docs.github.com/en/actions/learn-github-actions/expressions#always

In the meantime I have raised a PR reverting this removal: PR #2583

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

Successfully merging this pull request may close these issues.

3 participants