From: no-reply@sashiko.virtuozzo.com
To: khorenko@virtuozzo.com, Eva Kurchatova <eva.kurchatova@virtuozzo.com>
Cc: devel@openvz.org
Subject: Re: [Devel] [PATCH hci-8.1 v2 6/7] selftests/futex: fail run.sh when a test fails
Date: Tue, 27 Oct 2026 15:58:31 +0000 [thread overview]
Message-ID: <010701a17e15aaaa-eddeaea9-941c-4121-9d40-a28cfd2365f6-000000@eu-central-1.amazonses.com> (raw)
In-Reply-To: <20261027155236.1226178-7-eva.kurchatova@virtuozzo.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] selftests/futex: commit message carries downstream Jira URL and Feature tag
--
commit 32515d0daa85b1e913c1fe888da07e4c683238af
Author: Eva Kurchatova <eva.kurchatova@virtuozzo.com>
selftests/futex: fail run.sh when a test fails
This patch changes tools/testing/selftests/futex/functional/run.sh so that
each test invocation is followed by "|| ret=1" and the script ends with
"exit $ret". A failure in any test is now reported, not just a failure of
the last one.
> https://virtuozzo.atlassian.net/browse/VSTOR-134205
> Feature: fix selftests
[Severity: Low]
This isn't a bug in the code, but the commit message carries a link to a
private Virtuozzo Jira ticket and a "Feature: fix selftests" tag.
Upstream reviewers can't open that tracker, and both lines would stay in the
permanent upstream history if the patch is merged as is.
Could these two lines be dropped from the commit message before the patch
is submitted upstream?
The run.sh change itself looks correct.
--
Sashiko AI review · https://sashiko.vzint.dev/#/patchset/20261027155236.1226178-1-eva.kurchatova@virtuozzo.com?part=6
_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel
next prev parent reply other threads:[~2026-10-27 15:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 15:51 [Devel] [PATCH hci-8.1 v2 0/7] selftests: fix sticky failure in runners Eva Kurchatova
2026-10-27 15:51 ` [Devel] [PATCH hci-8.1 v2 1/7] ms/selftests/bpf: Upon failures, exit with code 1 in test_xsk.sh Eva Kurchatova
2026-10-27 15:55 ` no-reply
2026-10-27 15:51 ` [Devel] [PATCH hci-8.1 v2 2/7] selftests/memfd: fail run_hugetlbfs_test.sh when a test fails Eva Kurchatova
2026-10-27 15:55 ` no-reply
2026-10-27 15:51 ` [Devel] [PATCH hci-8.1 v2 3/7] selftests: sigaltstack: report the failures the signal handler records Eva Kurchatova
2026-10-27 15:56 ` no-reply
2026-10-27 15:51 ` [Devel] [PATCH hci-8.1 v2 4/7] selftests/zram: fail when a step fails Eva Kurchatova
2026-10-27 15:57 ` no-reply
2026-10-27 15:51 ` [Devel] [PATCH hci-8.1 v2 5/7] ms/selftests/futex: futex_waitv wouldblock test should fail Eva Kurchatova
2026-10-27 15:56 ` no-reply
2026-10-27 15:51 ` [Devel] [PATCH hci-8.1 v2 6/7] selftests/futex: fail run.sh when a test fails Eva Kurchatova
2026-10-27 15:58 ` no-reply [this message]
2026-10-27 15:51 ` [Devel] [PATCH hci-8.1 v2 7/7] selftests/futex: fail futex_waitv when the waiter failed Eva Kurchatova
2026-10-27 15:58 ` no-reply
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=010701a17e15aaaa-eddeaea9-941c-4121-9d40-a28cfd2365f6-000000@eu-central-1.amazonses.com \
--to=no-reply@sashiko.virtuozzo.com \
--cc=devel@openvz.org \
--cc=eva.kurchatova@virtuozzo.com \
--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.