From: Konstantin Khorenko <khorenko@virtuozzo.com>
To: Eva Kurchatova <eva.kurchatova@virtuozzo.com>
Cc: devel@openvz.org
Subject: Re: [Devel] [PATCH hci-8.1 v3 0/7] selftests: fix sticky failure in runners
Date: Fri, 30 Oct 2026 19:57:02 +0100 [thread overview]
Message-ID: <179338662218.1743453.2909333848355568985.b4-ty@b4> (raw)
In-Reply-To: <20261027173457.1261044-1-eva.kurchatova@virtuozzo.com>
On Tue, 27 Oct 2026 19:34:16 +0200, Eva Kurchatova wrote:
> selftests: fix sticky failure in runners
>
> Patchset for task https://virtuozzo.atlassian.net/browse/VSTOR-134205
>
> Several selftests report "ok" when a check inside them failed:
> - a shell runner ends with the status of its last command, not of the
> tests it ran (test_xsk.sh, run_hugetlbfs_test.sh, zram, futex run.sh)
> - a C test reports a failed check as a pass (sigaltstack, futex_waitv,
> futex_wait_wouldblock)
>
> [...]
Applied to branch-rh10-6.12.0-211.52.1.22.x.vz10-ovz, will be released in rh10-6.12.0-211.52.1.22.13.vz10, thanks!
[1/7] ms/selftests/bpf: Upon failures, exit with code 1 in test_xsk.sh
https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/d5e5642b10a0
[2/7] selftests/memfd: fail run_hugetlbfs_test.sh when a test fails
https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/29577a0ef957
[3/7] selftests: sigaltstack: report the failures the signal handler records
https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/21eb3e460690
[4/7] selftests/zram: fail when a step fails
https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/2604d3a4efa5
[5/7] ms/selftests/futex: futex_waitv wouldblock test should fail
https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/ee8fba174b3f
[6/7] selftests/futex: fail run.sh when a test fails
https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/1eee0b827336
[7/7] selftests/futex: fail futex_waitv when the waiter failed
https://bitbucket.org/virtuozzocore/vzkernel.vzs/commits/c388a3b453e1
--
Konstantin Khorenko,
Virtuozzo Linux Kernel Team
_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel
prev parent reply other threads:[~2026-10-30 18:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 17:34 Eva Kurchatova
2026-10-27 17:34 ` [Devel] [PATCH hci-8.1 v3 1/7] ms/selftests/bpf: Upon failures, exit with code 1 in test_xsk.sh Eva Kurchatova
2026-10-27 17:34 ` [Devel] [PATCH hci-8.1 v3 2/7] selftests/memfd: fail run_hugetlbfs_test.sh when a test fails Eva Kurchatova
2026-10-27 17:34 ` [Devel] [PATCH hci-8.1 v3 3/7] selftests: sigaltstack: report the failures the signal handler records Eva Kurchatova
2026-10-27 17:34 ` [Devel] [PATCH hci-8.1 v3 4/7] selftests/zram: fail when a step fails Eva Kurchatova
2026-10-27 17:34 ` [Devel] [PATCH hci-8.1 v3 5/7] ms/selftests/futex: futex_waitv wouldblock test should fail Eva Kurchatova
2026-10-27 17:34 ` [Devel] [PATCH hci-8.1 v3 6/7] selftests/futex: fail run.sh when a test fails Eva Kurchatova
2026-10-27 17:34 ` [Devel] [PATCH hci-8.1 v3 7/7] selftests/futex: fail futex_waitv when the waiter failed Eva Kurchatova
2026-10-30 18:45 ` [Devel] [PATCH hci-8.1 v3 0/7] selftests: fix sticky failure in runners Konstantin Khorenko
2026-10-30 18:57 ` Konstantin Khorenko [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=179338662218.1743453.2909333848355568985.b4-ty@b4 \
--to=khorenko@virtuozzo.com \
--cc=devel@openvz.org \
--cc=eva.kurchatova@virtuozzo.com \
/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