-
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
ci: ensure all nightlies post github issues when tests fail #77688
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewed 5 of 5 files at r1, all commit messages.
Reviewable status: complete! 0 of 0 LGTMs obtained (waiting on @rickystewart)
build/teamcity/cockroach/nightlies/compose.sh, line 40 at r1 (raw file):
if [ $exit_status -ne 0 ] then exit $exit_status
I think you can just exit $exit_status
without the if
check, because exit 0 is a normal exit status.
build/teamcity/cockroach/nightlies/lint_urls_impl.sh, line 24 at r1 (raw file):
$GO_TEST_JSON_OUTPUT_FILE \ $exit_status if [ $exit_status -ne 0 ]
the same here
build/teamcity/cockroach/nightlies/random_syntax_tests_impl.sh, line 22 at r1 (raw file):
/artifacts \ $GO_TEST_JSON_OUTPUT_FILE \ $exit_status
you need to add exit
here
build/teamcity/cockroach/nightlies/sqlite_logic_test_impl.sh, line 23 at r1 (raw file):
/artifacts \ $GO_TEST_JSON_OUTPUT_FILE \ $exit_status
and here
Release justification: ensure failing nightlies post github issues Release note: None
cf78893
to
82e0b12
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewed 4 of 4 files at r2, all commit messages.
Reviewable status: complete! 0 of 0 LGTMs obtained (waiting on @rickystewart)
bors r=rail |
Build succeeded: |
Confusingly bazci uses `--artifacts_dir` whereas roachtest uses `--artifacts`. The recent refactoring of optimizer_tests_impl.sh erroneously used the latter instead of the former. Consequently, (sql) Optimizer Tests stopped working in CI. Fixes: cockroachdb#77688 Release justification: ensure CI can run nightly (sql) Optimizer Tests Release note: None
80091: ci: fix optimizer_tests_impl.sh r=srosenberg a=srosenberg Confusingly bazci uses `--artifacts_dir` whereas roachtest uses `--artifacts`. The recent refactoring of optimizer_tests_impl.sh erroneously used the latter instead of the former. Consequently, (sql) Optimizer Tests stopped working in CI. Fixes: #77688 Release justification: ensure CI can run nightly (sql) Optimizer Tests Release note: None 80130: ci: fail if `redact_safe.md` is not up-to-date r=rail,ajwerner a=rickystewart Release note: None 80135: bazel: bump size of `rangefeed` test r=celiala a=rickystewart I've seen this time out in CI a couple times. Release note: None Co-authored-by: Stan Rosenberg <[email protected]> Co-authored-by: Ricky Stewart <[email protected]>
Confusingly bazci uses `--artifacts_dir` whereas roachtest uses `--artifacts`. The recent refactoring of optimizer_tests_impl.sh erroneously used the latter instead of the former. Consequently, (sql) Optimizer Tests stopped working in CI. Fixes: #77688 Release justification: ensure CI can run nightly (sql) Optimizer Tests Release note: None
Confusingly bazci uses `--artifacts_dir` whereas roachtest uses `--artifacts`. The recent refactoring of optimizer_tests_impl.sh erroneously used the latter instead of the former. Consequently, (sql) Optimizer Tests stopped working in CI. Fixes: #77688 Release justification: ensure CI can run nightly (sql) Optimizer Tests Release note: None
Release justification: ensure failing nightlies post github issues
Release note: None