Throwaway: verify Windows Bazel log tailing#18198
Draft
starr-openai wants to merge 2 commits intomainfrom
Draft
Conversation
Limit the Windows Bazel test lane to 8 jobs to reduce local runner pressure, and make failed-test log tailing resolve paths using the same CI config and Windows host-platform context as the failed invocation. Co-authored-by: Codex <noreply@openai.com>
Add an intentional throwaway test failure with a unique marker so the Windows Bazel workflow can verify failed-test log tailing. Co-authored-by: Codex <noreply@openai.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
WINDOWS_LOG_TAIL_PROBE_MARKERExpected result
The Windows Bazel test job should fail, and the GitHub job log should include the marker from the failed test log tail.
Cleanup
This PR is throwaway and should be closed/deleted after verification.