From: Eva Kurchatova <eva.kurchatova@virtuozzo.com>
To: khorenko@virtuozzo.com
Cc: devel@openvz.org
Subject: [Devel] [PATCH hci-8.1 v3 0/7] selftests: fix sticky failure in runners
Date: Tue, 27 Oct 2026 19:34:16 +0200 [thread overview]
Message-ID: <20261027173457.1261044-1-eva.kurchatova@virtuozzo.com> (raw)
Patchset for task https://virtuozzo.atlassian.net/browse/VSTOR-134205
Blocked on https://virtuozzo.atlassian.net/browse/VSTOR-150731
Changes in v3:
- zram: a compression algorithm the kernel is built without skips zram01
(SKIP line, exit 4) instead of failing it. An unreadable list of
algorithms fails it.
- zram: a missing mkfs.ext2, mkswap, swapon or swapoff skips the tests.
Link to v2: http://lore.virtuozzo.com/kernel/20261027155236.1226178-1-eva.kurchatova@virtuozzo.com/T/#t
Changes in v2:
- Pick 7d50e00fef28 ("selftests/futex: futex_waitv wouldblock test
should fail") before the run.sh patch, so that run.sh failing on
futex_wait_wouldblock comes with a "not ok" line.
- futex_waitv: the waiter returns its status and the main thread reports
one result per subtest, instead of the waiter adding a second one; a
waiter that cannot be joined counts as failed; the ksft_get_fail_cnt()
check is gone.
- zram: the message says it is the steps that report FAIL which fail the
test, and that the suite takes the worst result of its two tests.
Link to v1: http://lore.virtuozzo.com/kernel/20261026124139.606106-1-eva.kurchatova@virtuozzo.com/T/#t
Edward Liaw (1):
ms/selftests/futex: futex_waitv wouldblock test should fail
Eva Kurchatova (6):
ms/selftests/bpf: Upon failures, exit with code 1 in test_xsk.sh
selftests/memfd: fail run_hugetlbfs_test.sh when a test fails
selftests: sigaltstack: report the failures the signal handler records
selftests/zram: fail when a step fails
selftests/futex: fail run.sh when a test fails
selftests/futex: fail futex_waitv when the waiter failed
tools/testing/selftests/bpf/test_xsk.sh | 2 +
.../futex/functional/futex_wait_wouldblock.c | 2 +-
.../selftests/futex/functional/futex_waitv.c | 28 ++++++--
.../testing/selftests/futex/functional/run.sh | 66 ++++++++++---------
.../selftests/memfd/run_hugetlbfs_test.sh | 7 +-
tools/testing/selftests/sigaltstack/sas.c | 3 +-
tools/testing/selftests/zram/zram.sh | 11 +++-
tools/testing/selftests/zram/zram01.sh | 8 +++
tools/testing/selftests/zram/zram02.sh | 1 +
tools/testing/selftests/zram/zram_lib.sh | 45 ++++++++++---
10 files changed, 122 insertions(+), 51 deletions(-)
--
2.56.0
_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel
next reply other threads:[~2026-10-27 17:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 17:34 Eva Kurchatova [this message]
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
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=20261027173457.1261044-1-eva.kurchatova@virtuozzo.com \
--to=eva.kurchatova@virtuozzo.com \
--cc=devel@openvz.org \
--cc=khorenko@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.