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.

Sign up for GitHub

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

Jump to bottom

bazel,ci: investigate whether sharded tests are difficult to debug #69423

Closed

rickystewart opened this issue Aug 26, 2021 · 1 comment

Assignees

Labels

A-ci C-investigation T-dev-inf

Collaborator

rickystewart commented Aug 26, 2021

From #59045:

If a test failed, would that always happen while prominently displaying the shard? I'm asking because it would be tough to go through up to 16 directories on any failure of the kvserver tests that requires looking at the logs.

Check whether failed tests can easily be correlated to a log file. If not, implement some glue to make things easier.

rickystewart added C-investigation T-dev-inf A-ci labels

rickystewart self-assigned this

Collaborator Author

rickystewart commented Aug 31, 2021

Left a comment.

Right now I don't think any immediate changes are necessary, but as we move forward maybe we'll find that some additional glue will be necessary.

rickystewart closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment