Skip to content
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

bincheck: do not use uname -o #119393

Merged
merged 1 commit into from
Feb 20, 2024
Merged

Conversation

rail
Copy link
Member

@rail rail commented Feb 20, 2024

Previously, the bincheck script used uname -om to identify the OS. The -o options is not supported on the GitHub runners for darwin-amd64.

This PR stops using -o to fix the issue.

Epic: none
Release note: None

Previously, the bincheck script used `uname -om` to identify the OS. The
`-o` options is not supported on the GitHub runners for darwin-amd64.

This PR stops using `-o` to fix the issue.

Epic: none
Release note: None
@rail rail added C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior. A-release T-release Release Engineering & Automation Team backport-23.1.x Flags PRs that need to be backported to 23.1 backport-23.2.x Flags PRs that need to be backported to 23.2. labels Feb 20, 2024
@rail rail requested a review from celiala February 20, 2024 17:02
@rail rail self-assigned this Feb 20, 2024
@rail rail requested a review from a team as a code owner February 20, 2024 17:02
@cockroach-teamcity
Copy link
Member

This change is Reviewable

Copy link
Collaborator

@celiala celiala left a comment

Choose a reason for hiding this comment

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

Good catch! Thank you - LGTM

@rail
Copy link
Member Author

rail commented Feb 20, 2024

bors r=celiala

@craig
Copy link
Contributor

craig bot commented Feb 20, 2024

This PR was included in a batch that was canceled, it will be automatically retried

@craig
Copy link
Contributor

craig bot commented Feb 20, 2024

Build succeeded:

@craig craig bot merged commit 84ca65f into cockroachdb:master Feb 20, 2024
12 of 13 checks passed
Copy link

blathers-crl bot commented Feb 20, 2024

Encountered an error creating backports. Some common things that can go wrong:

  1. The backport branch might have already existed.
  2. There was a merge conflict.
  3. The backport branch contained merge commits.

You might need to create your backport manually using the backport tool.


error creating merge commit from b163677 to blathers/backport-release-23.1-119393: POST https://api.github.com/repos/cockroachdb/cockroach/merges: 409 Merge conflict []

you may need to manually resolve merge conflicts with the backport tool.

Backport to branch 23.1.x failed. See errors above.


🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-release backport-23.1.x Flags PRs that need to be backported to 23.1 backport-23.2.x Flags PRs that need to be backported to 23.2. C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior. T-release Release Engineering & Automation Team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants