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

bazci,engflow: update bazel-github-helper to post issues for failures #120352

Merged
merged 1 commit into from
Mar 15, 2024

Conversation

rickystewart
Copy link
Collaborator

@rickystewart rickystewart commented Mar 12, 2024

We only post failures if we're on master or a release branch.

This requires a refactor to move some common code into
pkg/build/engflow. I also needed to move pkg/cmd/internal/issues
to a different location to avoid restrictions related to internal
packages.

Epic: CRDB-8308
Release note: None

@rickystewart rickystewart requested a review from celiala March 12, 2024 16:45
@rickystewart rickystewart requested review from a team as code owners March 12, 2024 16:45
@rickystewart rickystewart requested review from srosenberg and renatolabs and removed request for a team March 12, 2024 16:45
Copy link

blathers-crl bot commented Mar 12, 2024

It looks like your PR touches production code but doesn't add or edit any test code. Did you consider adding tests to your PR?

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

@cockroach-teamcity
Copy link
Member

This change is Reviewable

@rickystewart rickystewart force-pushed the post-failures-from-ci branch 4 times, most recently from 41de46b to 807f330 Compare March 12, 2024 18:05
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.

:lgtm: - makes sense to me - thanks!

Reviewed 59 of 59 files at r1, all commit messages.
Reviewable status: :shipit: complete! 1 of 0 LGTMs obtained (waiting on @renatolabs and @srosenberg)

We only post failures if we're on `master` or a release branch.

This requires a refactor to move some common code into
`pkg/build/engflow`. I also needed to move `pkg/cmd/internal/issues`
to a different location to avoid restrictions related to `internal`
packages.

Epic: CRDB-8308
Release note: None
@rickystewart rickystewart force-pushed the post-failures-from-ci branch from 807f330 to 7e9a753 Compare March 14, 2024 22:19
@rickystewart
Copy link
Collaborator Author

TFTR!

bors r=celiala

@craig
Copy link
Contributor

craig bot commented Mar 15, 2024

@craig craig bot merged commit f5f5940 into cockroachdb:master Mar 15, 2024
19 checks passed
rickystewart added a commit to rickystewart/cockroach that referenced this pull request Mar 18, 2024
This was accidentally regressed in cockroachdb#120352.

Epic: CRDB-8308
Release note: None
craig bot pushed a commit that referenced this pull request Mar 18, 2024
120578: workflows: fetch extra commit needed for `TestRaftCopyrightHeaders` r=rail a=rickystewart

Epic: CRDB-8308
Release note: None

120602: colexecargs: deeply reset monitor registry on Reset r=yuzefovich a=yuzefovich

Given some recent issues we've had with leaks around memory monitors, it seems prudent to deeply reset the slice of monitors that is stored in the monitor registry object and is reused. Note that we haven't seen any evidence of leaks related to this registry, but this change might make things easier for GC, so seems worth it.

Epic: None

Release note: None

120650: bazci: only set extra params if provided on command-line r=rail a=rickystewart

This was accidentally regressed in #120352.

Epic: CRDB-8308
Release note: None

120651: sql/logictest: skip lookup_join_local under race r=mgartner a=mgartner

Fixes #120609

Release note: None

Co-authored-by: Ricky Stewart <[email protected]>
Co-authored-by: Yahor Yuzefovich <[email protected]>
Co-authored-by: Marcus Gartner <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants