travis: If the comparison-tool fails, dump the tail of the debug log #5025

1. 
   theuni commented at 8:47 pm on October 1, 2014: member

   The entire debug log would be huge, and could cause issues for automated tools like travis. Printing 200 lines is an initial guess at a reasonable number, more may be required.
2. travis: If the comparison-tool fails, dump the tail of the debug log

   The entire debug log would be huge, and could cause issues for automated tools
   like travis. Printing 200 lines is an initial guess at a reasonable number,
   more may be required.

   5ad450a65a
3. 
   sipa commented at 8:48 pm on October 1, 2014: member

   ut ACK
4. 
   theuni commented at 9:02 pm on October 1, 2014: member

   @sipa might be worth pulling this into your headers-first branch and letting it fail so we can see if it is enough to be useful.
5. 
   TheBlueMatt commented at 10:21 pm on October 1, 2014: member

   Why not just cat instead of tail? Maybe the error was right at the beginning and it kept running.
6. 
   theuni commented at 10:34 pm on October 1, 2014: member

   See description. Travis has a limit for how big the output can be. Here’s what the log looks like after a successful run:

   0cory@cory-i7:~/dev/bitcoin(travis-print-log)$ wc -l .bitcoin/regtest/debug.log
   126015 .bitcoin/regtest/debug.log
   2cory@cory-i7:~/dev/bitcoin(travis-print-log)$ du -h .bitcoin/regtest/debug.log 
   31.7M    .bitcoin/regtest/debug.log
   

   Things would get ugly if we cat’d that.

7. 
   TheBlueMatt commented at 10:41 pm on October 1, 2014: member

   Well, we should just include the full debug.log with the copy over to bitcoincore.org or so.
8. 
   sipa commented at 1:58 am on October 2, 2014: member

   This is much easier, and shouldn’t hurt anyway.
9. 
   TheBlueMatt commented at 2:21 am on October 2, 2014: member

   Yes, sorry, utACK on this…but a suggestion for when build output happens: make sure to include debug.log.
10. 
    laanwj commented at 6:33 am on October 2, 2014: member

    Well, we should just include the full debug.log with the copy over to bitcoincore.org or so.

    Once Travis grows support for producing multiple build results and securely uploading them, that would be the idea. But tailing 200 lines is a useful improvement already. (ut)ACK.

11. laanwj merged this on Oct 2, 2014
12. laanwj closed this on Oct 2, 2014

    ---

13. laanwj referenced this in commit 3b390723c1 on Oct 2, 2014
14. MarcoFalke locked this on Sep 8, 2021

Contributors
theuni sipa TheBlueMatt laanwj