[Devel] [PATCH hci-8.1 v2 0/7] selftests: fix sticky failure in runners

[Eva Kurchatova]

Patchset for task https://virtuozzo.atlassian.net/browse/VSTOR-134205

Blocked on https://virtuozzo.atlassian.net/browse/VSTOR-150731

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        |  4 ++
 tools/testing/selftests/zram/zram02.sh        |  1 +
 tools/testing/selftests/zram/zram_lib.sh      | 24 ++++---
 10 files changed, 97 insertions(+), 51 deletions(-)

-- 
2.56.0