Skip to content

fix(ci): add exit-code check for reservation tests step#200

Merged
itsmiso-ai merged 1 commit into
mainfrom
saffron/issue-176-exit-code-check
Jun 10, 2026
Merged

fix(ci): add exit-code check for reservation tests step#200
itsmiso-ai merged 1 commit into
mainfrom
saffron/issue-176-exit-code-check

Conversation

@itsmiso-ai

Copy link
Copy Markdown
Contributor

Fixes #176

Add exit-code enforcement to the reservation tests CI step, consistent with all other test steps (script, E2E, layout).

Previously the reservation tests step ran the tests but did not fail the CI job on non-zero exit — a silent pass on test failure. This fix captures the exit code and fails the job if tests do not pass.

The reservation tests step in CI was missing exit-code enforcement,
meaning test failures would silently pass. Add proper exit-code
checking consistent with all other test steps (script, E2E, layout).

Refs #176
@itsmiso-ai itsmiso-ai requested a review from joryirving as a code owner June 10, 2026 11:20

@its-saffron its-saffron Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

AI Automated Review

Full PR review.

Analysis engine: review@https://litellm.jory.dev/v1 (openai)

Recommendation

Approved. This PR correctly addresses the issue by ensuring that failures in the reservation tests are captured and cause the CI job to fail, preventing silent passes on test failures.

Change-by-change findings

  • .github/workflows/test.yml: Added logic to capture the exit code (RES_EXIT=$?) of the reservation tests command. It now checks if the exit code is non-zero, prints a GitHub error annotation if it fails, and exits the job with code 1. This aligns the reservation tests step with the existing behavior of the script, E2E, and layout regression test steps.

Linked Issue Fit

  • Issue PR 176: The PR directly satisfies the requirement to "add exit-code checks for reservation tests" as identified in the audit findings. It resolves the specific problem where the reservation CI step was printing logs but not failing the job on non-zero exit codes.

Standards Compliance

  • The implementation follows the existing pattern in .github/workflows/test.yml for handling test failures (using ::error:: annotations and exit 1), maintaining consistency across the CI pipeline.

@itsmiso-ai itsmiso-ai merged commit 4117562 into main Jun 10, 2026
4 checks passed
@itsmiso-ai itsmiso-ai deleted the saffron/issue-176-exit-code-check branch June 10, 2026 13:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Make all checked-in tests runnable and enforce them in CI

1 participant