Skip to content

Conversation

@danolivo
Copy link
Contributor

It seems that spockbench doesn't check anything now. Try to improve it.

@danolivo danolivo self-assigned this Dec 31, 2025
@danolivo danolivo added the bug Something isn't working label Dec 31, 2025
Previously, Spockbench errors would fail silently because:
1. run-tests.sh had 'set -euo pipefail' commented out
2. check-outputs.sh only validated container exit codes
3. PostgreSQL logs were never checked for errors

This meant the old log_old_value syntax could have been failing
silently without triggering test failures in GitHub Actions.

Changes:

1. run-tests.sh:
   - Uncommented 'set -euo pipefail' to fail fast on errors
   - Now SQL errors will immediately terminate the script

2. check-outputs.sh:
   - Added validation that containers actually exist
   - Added PostgreSQL log error checking
   - Scans pg logs for ERROR entries (excluding benign "relation does not exist")
   - Shows container logs on failure for debugging
   - Provides clear pass/fail feedback

This ensures that:
- SQL syntax errors are caught immediately
- Database errors don't go unnoticed
- Test failures are visible in CI/CD
- Debugging is easier with automatic log output

Now Spockbench will fail until the following commits fix detected issues.
@danolivo danolivo force-pushed the spoc-354 branch 4 times, most recently from 5c3bbc1 to eb2fd79 Compare December 31, 2025 13:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants