Page MenuHomePhabricator

[SECP256K1] Fix issue where travis does not show the logs
ClosedPublic

Authored by Fabien on Mar 5 2020, 11:50.

Details

Summary
I noticed that according to the doc tests.log should contain stdout as
well as stderr. But it doesn't because stdout isn't flushed. I removed
buffering completely to avoid having to call fflush twice.

Backport of secp256k1 PR685.

Depends on D5433.

It slightly varies from the PR by only printing the logs in the event of
a failure.

There is no need to explicitly cat the logs with the cmake build because
they are already printed by the test runner in case of failure.

Before: https://travis-ci.org/Fabcien/secp256k1/jobs/658610743
After: https://travis-ci.org/Fabcien/secp256k1/jobs/658631083

Test Plan

Diff Detail

Repository
rABC Bitcoin ABC
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

[Bot Message]
One or more PR numbers were detected in the summary.
Links to those PRs have been inserted into the summary for reference.

Why aren't the log printed in the cmake build as well?

src/secp256k1/travis/build_autotools.sh
39 ↗(On Diff #16777)

What does this double mouthy smiley do? He doesn't look amused anyways :/

deadalnix requested changes to this revision.Mar 5 2020, 17:01
This revision now requires changes to proceed.Mar 5 2020, 17:01
Fabien requested review of this revision.Mar 5 2020, 17:19

Let me quote the summary :)

There is no need to explicitly cat the logs with the cmake build because they are already printed by the test runner in case of failure.

src/secp256k1/travis/build_autotools.sh
39 ↗(On Diff #16777)

: is an alias for true. This is a usual pattern to say that I don't care about the return code of cat.

This revision is now accepted and ready to land.Mar 5 2020, 23:37