public inbox for bpf@vger.kernel.org
 help / color / mirror / Atom feed
From: Ihor Solodrai <ihor.solodrai@linux.dev>
To: Ilya Leoshkevich <iii@linux.ibm.com>
Cc: bpf <bpf@vger.kernel.org>, Alexei Starovoitov <ast@kernel.org>,
	Andrii Nakryiko <andrii@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	Martin KaFai Lau <martin.lau@linux.dev>
Subject: [BPF CI] OOMs on s390x runners
Date: Tue, 20 Jan 2026 09:59:28 -0800	[thread overview]
Message-ID: <8553c4ab-9b42-46a8-9187-38ba4f63fff0@linux.dev> (raw)

Hi Ilya,

The BPF selftests regularly fail on s390x runners with OOMs.

The s390x hosts that I've been maintaining have 16G of memory, hosting
2 runners each. VMs (qemu instances) running the tests currently get
5G of memory each.

I noticed that the s390x runners didn't have swap set up, so I added
an ansible config to set up a swapfile. This seems to have helped with
OOM failures.

https://github.com/libbpf/ci/commit/8767dc05ab84c88da198af3c651511e731ddbac7

I spot checked a couple of recent failures, and all of them happened
on the "ebpf1-worker-*" runners that you've been maintaining IIRC.
Here is a couple of examples:
  - https://github.com/kernel-patches/bpf/actions/runs/21178791628/job/60916006746
  - https://github.com/kernel-patches/bpf/actions/runs/21163448380/job/60863171062
  - https://github.com/kernel-patches/bpf/actions/runs/21157785072/job/60846570064

Could you please re-provision the hosts with the swap setup?
Let's see if that helps.

Thanks!

             reply	other threads:[~2026-01-20 17:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-20 17:59 Ihor Solodrai [this message]
2026-01-21 22:56 ` [BPF CI] OOMs on s390x runners Ilya Leoshkevich
2026-02-05 23:50   ` Ihor Solodrai
2026-02-10 21:23     ` Ilya Leoshkevich

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=8553c4ab-9b42-46a8-9187-38ba4f63fff0@linux.dev \
    --to=ihor.solodrai@linux.dev \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=iii@linux.ibm.com \
    --cc=martin.lau@linux.dev \
    /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