-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
bazel, ci: use test2json format for nightly logging #72611
Conversation
34668fc
to
e047827
Compare
e268940
to
9c2511c
Compare
Fixes cockroachdb#71930 Previously, bazel based nightlies didn't report errors as github issues. This PR uses a custom feature of `rules_go` to save the log output in `test2json` format. A new shell function is added to post-process the generated log and ports the `run_json_test` features to submit failures to GitHub. Release note: None
9c2511c
to
c1861d3
Compare
I think this is ready to be reviewed. I pushed this rules_go change to the release-0.29 branch, so we can save logs in To be tested (in production): This is how it behaves when there is a test failure: artifacts And there is also a green test: artifacts |
bors r=rickystewart |
Build failed (retrying...): |
Build succeeded: |
Fixes #71930
Previously, bazel based nightlies didn't report errors as github issues.
This PR uses a custom feature of
rules_go
to save the log output intest2json
format. A new shell function is added to post-process thegenerated log and ports the
run_json_test
features to submit failuresto GitHub.
Release note: None