CI: Make failure message easier to spot #31200

1. 
   m3dwards commented at 8:06 pm on October 31, 2024: contributor

   Sometimes during a CI failure the actual error message can be buried in a wall of log output and not immediately clear. Ideally it should be obvious why a CI job has failed.

   CC @maflcko

2. 
   maflcko commented at 7:26 am on November 1, 2024: member

   I don’t think there is an easy solution to always show the error reason at the tail of the CI log. To expand for each task:

   • The lint tests are designed to run all (even if a failure occurs in the first one), so that all failures are collected. However, some of the lint tests print other output, so the failures may not be at the very tail. I’ve added the ⚠️ emoji to error messages to make them easier to spot, but maybe there are other ways to improve. Example: https://github.com/bitcoin/bitcoin/runs/30825233774
   • Compile failures are re-done verbosely in a single thread, so they should be at the tail and easy to spot. Example: https://github.com/bitcoin/bitcoin/runs/32337137613
   • For unit and functional test failures, the full debug log and test log is printed, so the error may be hidden early in the log and not at the tail. I don’t think this is possible to improve on.
3. maflcko added the label Tests on Nov 1, 2024
4. maflcko added the label Brainstorming on Nov 1, 2024

Contributors
m3dwards maflcko

Labels
Brainstorming Tests