You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a test fails, it currently outputs only the failed assertion (with file and line) to stderr. The seed is output to stdout only. Moreover, neither stdout nor stderr are output on make check. Instead, the stderr is written to ./test-suite.log
As a consequence, a non-reproducible failure on Travis is somewhat useless to us because we just see the FAIL but we have no idea what failed because we don't see the contents of the log file. (This just happened downstream in secp256k1-zkp). A similar issue was the failed PR build on a Fedora build server, which contained only stderr #558 (comment) and thus we didn't get the seed.
We should probably
output the seed to stderr, at least if the test fails.
When a test fails, it currently outputs only the failed assertion (with file and line) to stderr. The seed is output to stdout only. Moreover, neither stdout nor stderr are output on
make check
. Instead, the stderr is written to./test-suite.log
As a consequence, a non-reproducible failure on Travis is somewhat useless to us because we just see the FAIL but we have no idea what failed because we don't see the contents of the log file. (This just happened downstream in secp256k1-zkp). A similar issue was the failed PR build on a Fedora build server, which contained only stderr #558 (comment) and thus we didn't get the seed.
We should probably
after_script
orafter_failure
, see https://docs.travis-ci.com/user/job-lifecycle/#the-job-lifecycleThe text was updated successfully, but these errors were encountered: