public inbox for git@vger.kernel.org
 help / color / mirror / Atom feed
From: Philippe Blain <levraiphilippeblain@gmail.com>
To: Git mailing list <git@vger.kernel.org>
Subject: Failures in GitHub Actions linux-leaks and linux-asan-ubsan
Date: Sat, 16 Mar 2024 15:20:44 -0400	[thread overview]
Message-ID: <3e217121-f49b-33bd-b76f-df24efca6d14@gmail.com> (raw)

Hi everyone,

You might have noticed that the linux-leaks and linux-asan-ubsan
jobs in GitHub Actions started failing last week. I investigated 
this so I'm sharing my findinds in case it helps.

The failures are due to the new ubuntu-22.04 GitHub Actions image
(release 20240310.1.0, [1]) which uses a kernel where ASLR is configured
in a way that is incompatible with ASan and LSan as used in 
the GCC and Clang versions in that image. More info can be found
in [2] and [3] and pages linked there.

A workaround was already implemented in the image generation process 
[4], so the next version of the image should work. I think the images
are released weekly. We could maybe add the same sysctl command to reduce
the entropy to our YAML file, or we could live with it for the next week
or so while waiting for the next image to roll out.

Cheers,

Philippe.

[1] https://github.com/actions/runner-images/commit/d67fa31aeeec3cf0d666d0eb2976b683471c6b90
[2] https://github.com/actions/runner-images/issues/9491#issuecomment-1989718917
[3] https://github.com/actions/runner-images/issues/9524#issuecomment-2002065399
[4] https://github.com/actions/runner-images/pull/9513

             reply	other threads:[~2024-03-16 19:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-16 19:20 Philippe Blain [this message]
2024-03-16 23:31 ` Failures in GitHub Actions linux-leaks and linux-asan-ubsan Junio C Hamano
2024-03-18  6:52 ` Linus Arver
2024-03-18  9:08 ` Jeff King

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3e217121-f49b-33bd-b76f-df24efca6d14@gmail.com \
    --to=levraiphilippeblain@gmail.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox