Skip to content

Commit

Permalink
CI: Grep for exact error message
Browse files Browse the repository at this point in the history
`cargo +nightly` output of panic recently changed breaking our grep
statement by adding the code line and a newline.

Grep for the exact second line of the error message.
  • Loading branch information
tcharding committed Aug 8, 2023
1 parent 29e1a0c commit 912b82d
Showing 1 changed file with 3 additions and 1 deletion.
4 changes: 3 additions & 1 deletion contrib/test.sh
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,9 @@ if cargo --version | grep "1\.48"; then
fi

# Test if panic in C code aborts the process (either with a real panic or with SIGILL)
cargo test -- --ignored --exact 'tests::test_panic_raw_ctx_should_terminate_abnormally' 2>&1 | tee /dev/stderr | grep "SIGILL\\|panicked at '\[libsecp256k1\]"
cargo test -- --ignored --exact 'tests::test_panic_raw_ctx_should_terminate_abnormally' 2>&1 \
| tee /dev/stderr \
| grep "SIGILL\\|\[libsecp256k1] illegal argument. !rustsecp256k1_v0_._._fe_is_zero(&ge->x)"

# Make all cargo invocations verbose
export CARGO_TERM_VERBOSE=true
Expand Down

0 comments on commit 912b82d

Please sign in to comment.