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

Bug Report: CI does not fail when an e2e race test fails #13630

Closed
brendar opened this issue Jul 26, 2023 · 0 comments · Fixed by #13654
Closed

Bug Report: CI does not fail when an e2e race test fails #13630

brendar opened this issue Jul 26, 2023 · 0 comments · Fixed by #13654

Comments

@brendar
Copy link
Contributor

brendar commented Jul 26, 2023

Overview of the Issue

There is a bug in tools/e2e_test_race.sh that causes it to exit 0 even when a data race is detected or a test fails.

For example, this End-to-End Test (Race) job from a recent PR has 3 failures with race detected during execution of test but ultimately reports success: https://github.com/vitessio/vitess/actions/runs/5653523125/job/15314840298

The cause is this line in tools/e2e_test_race.sh:

echo "$all_e2e_tests" | xargs go test $VT_GO_PARALLEL -race 2>&1 | tee $temp_log_file
if [ ${PIPESTATUS[0]} -ne 0 ]; then

Which should be: ${PIPESTATUS[1]}

I didn't open a PR to fix that since the PR will fail CI until all the races are fixed, but I confirmed the issue with a draft PR here: Shopify#112

Reproduction Steps

n/a

Binary Version

n/a

Operating System and Environment details

n/a

Log Fragments

n/a
@brendar brendar added Needs Triage This issue needs to be correctly labelled and triaged Type: Bug labels Jul 26, 2023
@shlomi-noach shlomi-noach added Component: Build/CI and removed Needs Triage This issue needs to be correctly labelled and triaged labels Jul 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants