From: Daniel Vetter <daniel.vetter@ffwll.ch>
To: IGT development <igt-dev@lists.freedesktop.org>
Cc: Daniel Vetter <daniel.vetter@intel.com>
Subject: [igt-dev] [PATCH i-g-t 3/9] lib/tests: make sure igt_skip in igt_fork is forbidden
Date: Wed, 13 Feb 2019 11:35:45 +0100 [thread overview]
Message-ID: <20190213103551.5438-3-daniel.vetter@ffwll.ch> (raw)
In-Reply-To: <20190213103551.5438-1-daniel.vetter@ffwll.ch>
Another corner case to check.
v2: Rebase. Note that we still have the SIG + 128 exit code, that's
how igt_waitchildren forwards child death to the parent's exit code.
Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
---
lib/tests/igt_fork.c | 14 ++++++++++++++
1 file changed, 14 insertions(+)
diff --git a/lib/tests/igt_fork.c b/lib/tests/igt_fork.c
index 8d3c1bd02288..6769e84a6989 100644
--- a/lib/tests/igt_fork.c
+++ b/lib/tests/igt_fork.c
@@ -43,6 +43,15 @@
char test[] = "test";
char *argv_run[] = { test };
+static void igt_fork_vs_skip(void)
+{
+ igt_fork(i, 1) {
+ igt_skip("skipping");
+ }
+
+ igt_waitchildren();
+}
+
static void igt_fork_vs_assert(void)
{
igt_fork(i, 1) {
@@ -79,6 +88,11 @@ int main(int argc, char **argv)
{
int ret;
+ /* check that igt_assert is forwarded */
ret = do_fork(igt_fork_vs_assert);
internal_assert(WEXITSTATUS(ret) == IGT_EXIT_FAILURE);
+
+ /* check that igt_skip within a fork blows up */
+ ret = do_fork(igt_fork_vs_skip);
+ internal_assert(WEXITSTATUS(ret) == SIGABRT + 128);
}
--
2.20.1
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-02-13 10:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-13 10:35 [igt-dev] [PATCH i-g-t 1/9] lib/tests: Drop NIH exit status handling Daniel Vetter
2019-02-13 10:35 ` [igt-dev] [PATCH i-g-t 2/9] lib/tests: Check that igt_assert forwards correctly through igt_fork Daniel Vetter
2019-02-13 10:35 ` Daniel Vetter [this message]
2019-02-13 10:35 ` [igt-dev] [PATCH i-g-t 4/9] lib: Don't leak children in igt_waitchildren_timeout Daniel Vetter
2019-02-13 10:35 ` [igt-dev] [PATCH i-g-t 5/9] tests/gem_exec_reuse: Don't leak the hang detector Daniel Vetter
2019-02-13 10:35 ` [igt-dev] [PATCH i-g-t 6/9] tests/i915_missed_irq: Don't leave the hang detector hanging Daniel Vetter
2019-02-13 10:35 ` [igt-dev] [PATCH i-g-t 7/9] lib: Make sure we leak no child processes Daniel Vetter
2019-02-13 10:35 ` [igt-dev] [PATCH i-g-t 8/9] lib: Drop igt_child_done Daniel Vetter
2019-02-13 10:35 ` [igt-dev] [PATCH i-g-t 9/9] lib: Drop IGT_EXIT_TIMEOUT Daniel Vetter
2019-02-13 10:49 ` [igt-dev] [PATCH i-g-t 1/9] lib/tests: Drop NIH exit status handling Chris Wilson
2019-02-13 10:51 ` Chris Wilson
2019-02-13 13:13 ` Daniel Vetter
2019-02-14 9:53 ` [igt-dev] ✗ Fi.CI.BAT: failure for series starting with [i-g-t,1/9] lib/tests: Drop NIH exit status handling (rev2) Patchwork
2019-02-14 15:00 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/9] lib/tests: Drop NIH exit status handling (rev3) Patchwork
2019-02-14 20:13 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2019-02-15 9:37 ` Daniel Vetter
2019-02-15 17:53 ` [igt-dev] ✗ Fi.CI.BAT: failure for series starting with [i-g-t,1/9] lib/tests: Drop NIH exit status handling (rev4) Patchwork
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=20190213103551.5438-3-daniel.vetter@ffwll.ch \
--to=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=igt-dev@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox