-
Notifications
You must be signed in to change notification settings - Fork 1.7k
fix(ci): macOS runner for Intel #22134
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
Datadog ReportBranch report: ✅ 0 Failed, 7 Passed, 0 Skipped, 25.42s Total Time |
@@ -268,7 +268,7 @@ jobs: | |||
|
|||
build-x86_64-apple-darwin-packages: | |||
name: Build Vector for x86_64-apple-darwin (.tar.gz) | |||
runs-on: macos-latest-xlarge | |||
runs-on: macos-latest-large |
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.
The macos-verify
job runs on [macos-14, macos-15]
. I wonder if it should just run on macos-latest-large
.
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.
I think the macos-verify
job will fail with this update, no?, due to the CPU architecture not matching.
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 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.
I think we need to update the macos-verify
job too, but otherwise 👍
* fix(ci): macOS runner for Intel * fix macos-verify
* fix(ci): macOS runner for Intel * fix macos-verify
Summary
macos-latest-xlarge
is for ARM architecture based on https://docs.github.com/en/actions/using-github-hosted-runners/using-larger-runners/about-larger-runners.This PR is an immediate fix. Will followup with another PR to add support for both ARM and Intel and fix the verification step.
Change Type
Is this a breaking change?
How did you test this PR?
Does this PR include user facing changes?
Checklist
Cargo.lock
), pleaserun
dd-rust-license-tool write
to regenerate the license inventory and commit the changes (if any). More details here.References
Ref: #22129