From: Tianyi Chen <diannaaav@gmail.com>
To: kernel-ci@meta.com
Cc: bpf@vger.kernel.org, andrii@kernel.org, daniel@iogearbox.net,
martin.lau@linux.dev
Subject: Re: [PATCH bpf v3] selftests/bpf: Check returned keys in map batch validators
Date: Wed, 16 Sep 2026 09:18:55 +0800 [thread overview]
Message-ID: <20260916011855.1563648-1-diannaaav@gmail.com> (raw)
In-Reply-To: <2b6eb4563b296447ef2011962270b7da14edcc84eded24e3784dd20c8f6f6b5e@mail.kernel.org>
Hi CI team,
The latest failure for series 1162495 is in VM startup, before veristat
runs. Could you refresh the vmtest executable and rerun the failed job?
The sole failing job is x86_64 GCC 15 / veristat-meta:
https://github.com/kernel-patches/bpf/actions/runs/34808652400/job/103868698882
Its /usr/bin/vmtest appears to contain an HTML document rather than the
expected executable. The log reports:
/usr/bin/vmtest: line 1: !DOCTYPE: No such file or directory
/usr/bin/vmtest: line 4: Hello: command not found
It then exits 2 with an unmatched-quote error before the guest starts.
There is no verifier regression result from this job.
The action requests vmtest v0.18.0. The run-vmtest installer in libbpf/ci
uses curl -L to write directly to /usr/bin/vmtest, followed by chmod,
without HTTP failure checking or executable-content validation. Adding
those checks would make this fail clearly at download/install time
instead of trying to execute an HTML response. The log does not identify
which HTTP response or intermediary supplied the page.
The earlier run of this same patch version completed veristat-meta and
reported that its output matched its baseline:
https://github.com/kernel-patches/bpf/actions/runs/34800861264/job/103846813446
The latest run's test_maps jobs also passed on x86_64 GCC, x86_64 LLVM
and aarch64 GCC. This patch changes only three map_tests validators;
it does not change vmtest, CI scripts or the verifier. I am keeping v3
unchanged for this infrastructure failure.
Thanks,
Tianyi
prev parent reply other threads:[~2026-09-16 1:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 2:50 [PATCH bpf v3] selftests/bpf: Check returned keys in map batch validators Tianyi Chen
2026-09-11 2:57 ` sashiko-bot
2026-09-11 3:03 ` Tianyi Chen
[not found] ` <fd1233fd7c263a4150672e1af33aaea82d625f727ead53cb681ae69bce1e6322@mail.kernel.org>
2026-09-11 11:57 ` Tianyi Chen
[not found] ` <2b6eb4563b296447ef2011962270b7da14edcc84eded24e3784dd20c8f6f6b5e@mail.kernel.org>
2026-09-16 1:18 ` Tianyi Chen [this message]
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=20260916011855.1563648-1-diannaaav@gmail.com \
--to=diannaaav@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-ci@meta.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