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

Only check for shard status file if a test passed #22098

Closed
wants to merge 1 commit into from

Conversation

fmeum
Copy link
Collaborator

@fmeum fmeum commented Apr 23, 2024

If a test fails, the failure is going to be informative than a generic exec error and the failure may have interrupted or prevented the test runner from touching the status file.

Speculatively fixes #22028

If a test fails, the failure is going to be informative than a generic
exec error and the failure may have interrupted or prevented the test
runner from touching the status file.

Speculatively fixes bazelbuild#22028
@fmeum fmeum requested a review from tjgq April 23, 2024 19:48
@github-actions github-actions bot added the awaiting-review PR is awaiting review from an assigned reviewer label Apr 23, 2024
@fmeum
Copy link
Collaborator Author

fmeum commented Apr 23, 2024

@bazel-io fork 7.2.0

@bazel-io bazel-io added the potential release blocker Flagged by community members using "@bazel-io flag". Should be added to a release blocker milestone label Apr 23, 2024
@iancha1992 iancha1992 added team-OSS Issues for the Bazel OSS team: installation, release processBazel packaging, website and removed potential release blocker Flagged by community members using "@bazel-io flag". Should be added to a release blocker milestone labels Apr 23, 2024
@tjgq tjgq added awaiting-PR-merge PR has been approved by a reviewer and is ready to be merge internally and removed awaiting-review PR is awaiting review from an assigned reviewer labels Apr 25, 2024
bazel-io pushed a commit to bazel-io/bazel that referenced this pull request Apr 26, 2024
If a test fails, the failure is going to be informative than a generic exec error and the failure may have interrupted or prevented the test runner from touching the status file.

Speculatively fixes bazelbuild#22028

Closes bazelbuild#22098.

PiperOrigin-RevId: 628355694
Change-Id: I370c7aba331f2a7a89cb9a9ff99d32b1694fd03a
@fmeum fmeum deleted the 22028-shard-failure branch April 26, 2024 10:44
@sgowroji sgowroji removed the awaiting-PR-merge PR has been approved by a reviewer and is ready to be merge internally label Apr 30, 2024
github-merge-queue bot pushed a commit that referenced this pull request May 8, 2024
If a test fails, the failure is going to be informative than a generic
exec error and the failure may have interrupted or prevented the test
runner from touching the status file.

Speculatively fixes #22028

Closes #22098.

PiperOrigin-RevId: 628355694
Change-Id: I370c7aba331f2a7a89cb9a9ff99d32b1694fd03a

Commit
874a050

Co-authored-by: Fabian Meumertzheim <[email protected]>
Kila2 pushed a commit to Kila2/bazel that referenced this pull request May 13, 2024
If a test fails, the failure is going to be informative than a generic exec error and the failure may have interrupted or prevented the test runner from touching the status file.

Speculatively fixes bazelbuild#22028

Closes bazelbuild#22098.

PiperOrigin-RevId: 628355694
Change-Id: I370c7aba331f2a7a89cb9a9ff99d32b1694fd03a
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
team-OSS Issues for the Bazel OSS team: installation, release processBazel packaging, website
Projects
None yet
Development

Successfully merging this pull request may close these issues.

--incompatible_check_sharding_support can cause intermittent test failures
5 participants