Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .ci/integration.cloudbuild.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -522,7 +522,7 @@ steps:
.ci/test_with_coverage.sh \
"Spanner" \
spanner \
spanner || echo "Integration tests failed."
spanner || { echo "Integration tests failed."; exit 1; }
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The explicit error handling || { echo ...; exit 1; } is redundant here. In a Cloud Build args block using bash -c, the exit code of the shell is determined by the last command executed in the script. Since this test command is the final operation in its branch of the if statement, the step will naturally fail if the tests fail. Removing this logic would make the Spanner step consistent with all other integration test steps in this file (e.g., cloud-sql-pg, alloydb, bigquery, etc.), which simply call the test script directly.

            spanner

else
echo "No relevant changes for Spanner. Skipping shard."
exit 0
Expand Down
Loading