ci: Print Linux kernel info #28575

1. 
   maflcko commented at 2:39 PM on October 3, 2023: member

   Required to debug issues like #28487 (comment). For example:

   FATAL: ThreadSanitizer: unexpected memory mapping 0x57cf8f031000-0x57cf8f173000
   

2. ci: Print Linux kernel info fac054d24c
3. 
   DrahtBot commented at 2:39 PM on October 3, 2023: contributor

   <!--e57a25ab6845829454e8d69fc972939a-->

   The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.

   <!--021abf342d371248e50ceaed478a90ca-->

   Reviews

   See the guideline for information on the review process.

   Type	Reviewers
   ACK	hebasto

   If your review is incorrectly listed, please react with 👎 to this comment and the bot will ignore it on the next update.

4. DrahtBot added the label Tests on Oct 3, 2023
5. hebasto approved
6. 
   hebasto commented at 2:45 PM on October 3, 2023: member

   ACK fac054d24c4b6fe3370e458ad6b626f98bd018d6

7. maflcko added this to the milestone 26.0 on Oct 3, 2023
8. 
   fanquake commented at 3:46 PM on October 3, 2023: member

   I assume we are going to backport this as well, as the issues only seem to be happening in the 25.x and 24.x branches?

9. 
   maflcko commented at 3:54 PM on October 3, 2023: member

   No need to backport. This shouldn't fix any bug and I'll try to track down and fix the CI issue in the meantime.

10. 
    fanquake commented at 3:56 PM on October 3, 2023: member

    Right. I just assumed you'd want the debug info in the branches where it's actually happening. Fine to merge in any case.

11. fanquake merged this on Oct 3, 2023
12. fanquake closed this on Oct 3, 2023

    ---

13. maflcko deleted the branch on Oct 3, 2023
14. 
    maflcko commented at 4:43 PM on October 3, 2023: member

    See https://www.github.com/cirruslabs/cirrus-ci-docs/issues/1241 for the upstream tracking issue

15. Frank-GER referenced this in commit 1683f196b0 on Oct 13, 2023
16. bitcoin locked this on Dec 3, 2024

Milestone
26.0