From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Alan Maguire <alan.maguire@oracle.com>
Cc: dwarves@vger.kernel.org
Subject: Re: [PATCH dwarves 0/4] tests: unify behaviour, pass through fail
Date: Tue, 1 Oct 2024 11:37:51 -0300 [thread overview]
Message-ID: <ZvwJP_795_qiP9hk@x1> (raw)
In-Reply-To: <20241001114629.3947401-1-alan.maguire@oracle.com>
On Tue, Oct 01, 2024 at 12:46:25PM +0100, Alan Maguire wrote:
> The "tests" script has recently been added to support running tests;
> unify behaviour across all tests to
>
> 1. return 2 for cases where the test has to be skipped (versus 1
> for an actual failure)
> 2. for tests that require vmlinux, allow it to be speficied via
> environment variable; this allows the tests script to be run
> with a specific vmlinux not discoverable via pahole
>
> Patches 1-3 handle updating individual tests; patch 4 ensures that
> if we hit a failure, the tests script will return 1 to indicate
> that a test failed.
>
> Alan Maguire (4):
> tests/reproducible_builds: support envvar-specified vmlinux
> tests/btf_functions: return 2 to indicate test had to be skipped
> tests/reproducible_build: return 2 (skipped) if no vmlinux available
> tests: distinguish between failed/skipped tests
Thanks, applied.
- Arnaldo
prev parent reply other threads:[~2024-10-01 14:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-01 11:46 [PATCH dwarves 0/4] tests: unify behaviour, pass through fail Alan Maguire
2024-10-01 11:46 ` [PATCH dwarves 1/4] tests/reproducible_builds: support envvar-specified vmlinux Alan Maguire
2024-10-01 11:46 ` [PATCH dwarves 2/4] tests/btf_functions: return 2 to indicate test had to be skipped Alan Maguire
2024-10-01 11:46 ` [PATCH dwarves 3/4] tests/reproducible_build: return 2 (skipped) if no vmlinux available Alan Maguire
2024-10-01 11:46 ` [PATCH dwarves 4/4] tests: distinguish between failed/skipped tests Alan Maguire
2024-10-01 14:37 ` Arnaldo Carvalho de Melo [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=ZvwJP_795_qiP9hk@x1 \
--to=acme@kernel.org \
--cc=alan.maguire@oracle.com \
--cc=dwarves@vger.kernel.org \
/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.