-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
use gce runner for execution-performance benchmark #15300
base: main
Are you sure you want to change the base?
Conversation
⏱️ 1h 57m total CI duration on this PR
🚨 1 job on the last run was significantly faster/slower than expected
|
27d066a
to
0c14aab
Compare
0c14aab
to
3553bbc
Compare
steps: | ||
- uses: actions/checkout@v4 | ||
with: | ||
ref: ${{ inputs.GIT_SHA }} | ||
if: ${{ inputs.IGNORE_TARGET_DETERMINATION || needs.test-target-determinator.outputs.run_execution_performance_test == 'true' }} | ||
|
||
- uses: aptos-labs/aptos-core/.github/actions/rust-setup@main | ||
- uses: aptos-labs/aptos-core./.github/actions/rust-setup@main |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There appears to be an extra period in the action path aptos-labs/aptos-core./.github/actions/rust-setup@main
which will cause the action to fail. The correct path should be aptos-labs/aptos-core/.github/actions/rust-setup@main
.
Spotted by Graphite Reviewer
Is this helpful? React 👍 or 👎 to let us know.
Description
Migrate the execution-performance workflow to using CE instances instead of using runners from our CI cluster
I'm using the related-sciences/gce-github-runner action to create and cleanup the instance. I forked this with some changes to make it work with our dev_setup.sh
How Has This Been Tested?
https://github.com/aptos-labs/aptos-core/actions/runs/11898685620/job/33396239201?pr=15300
Key Areas to Review
Type of Change
Which Components or Systems Does This Change Impact?
Checklist