The travis test result which is linked to by most commits on GitHub is sometimes not related to the commit.
It may happen that even the build jobs of a single build contains results from different commits.
The travis test result which is linked to by most commits on GitHub is sometimes not related to the commit.
It may happen that even the build jobs of a single build contains results from different commits.
Travis error seems unrelated. Just re-kicked travis for this PR.
Maybe you'd like to print $TRAVIS_COMMIT_RANGE, so that it's immediately clear what was in the build? I believe it should print "foo...bar", which could be easily checked locally.
Right now it should print
commit $some_random_hash Merge: 30c2dd8 faef3b7
where 30c2dd8 should be in bitcoin/master and faef3b7 in the branch someone wants to merge. I think that is sufficient to quickly check that something went wrong.
Travis error seems unrelated
Travis is building random crap, which you can see by observing the commit ids:
$ echo $TRAVIS_COMMIT_LOG
commit 73c560fc0d92177e88ddd02f6ac628340b85688c Merge: 30c2dd8 4b1ea9a
where 30c2dd8 is the current HEAD and 4b1ea9a is some random commit.
So the travis error is "related" but unwanted.
@theuni Is it ok if I print both, so it is clear which commit of the target branch travis used? Also, I'd rather not trust $TRAVIS_COMMIT_RANGE blindly.
$ echo $TRAVIS_COMMIT_RANGE
30c2dd8d0598afac9319d3a813a89a682b9c0d34...fac9ca2ec69bc629dbbd81c83e5bf67690e52c96
$ echo $TRAVIS_COMMIT_LOG
commit 049d5e4dfe711bb2af5c9c3904de7f78a24fedac Merge: a914968 fac9ca2
Last travis failure indeed unrelated:
Failed to fetch http://us.archive.ubuntu.com/ubuntu/pool/main/g/gcc-4.6/libstdc++6_4.6.3-1ubuntu5_i386.deb Unable to connect to us.archive.ubuntu.com:http: [IP: 2001:67c:1562::15 80]
Anything holding this back?
Restarting travis.
utACK