From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH igt] lib: compute exitcode first
Date: Tue, 3 May 2016 11:22:33 +0100 [thread overview]
Message-ID: <57287BE9.3050402@linux.intel.com> (raw)
In-Reply-To: <1462269947-28245-1-git-send-email-chris@chris-wilson.co.uk>
On 03/05/16 11:05, Chris Wilson wrote:
> Before we print the exitcode to the debug/kmsg logs, we should inspect
> what it's final value will be. For example, in the case of running
> multiple subtests which all happen to be skipped, igt_exitcode is 0, but
> the final exit code will be 77.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> ---
> lib/igt_core.c | 28 ++++++++++++++++------------
> 1 file changed, 16 insertions(+), 12 deletions(-)
>
> diff --git a/lib/igt_core.c b/lib/igt_core.c
> index b0bc60c..8c4bbc4 100644
> --- a/lib/igt_core.c
> +++ b/lib/igt_core.c
> @@ -1258,10 +1258,22 @@ void igt_exit(void)
> exit(IGT_EXIT_INVALID);
> }
>
> -
> if (igt_only_list_subtests())
> exit(IGT_EXIT_SUCCESS);
>
> + /* Calling this without calling one of the above is a failure */
> + assert(!tests_with_subtests ||
test_with_subtests
With that fixed it seems to work,
Tested-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Regards,
Tvrtko
> + skipped_one ||
> + succeeded_one ||
> + failed_one);
> +
> + if (test_with_subtests && !failed_one) {
> + if (succeeded_one)
> + igt_exitcode = IGT_EXIT_SUCCESS;
> + else
> + igt_exitcode = IGT_EXIT_SKIP;
> + }
> +
> kmsg(KMSG_INFO "%s: exiting, ret=%d\n", command_str, igt_exitcode);
> igt_debug("Exiting with status code %d\n", igt_exitcode);
>
> @@ -1288,19 +1300,11 @@ void igt_exit(void)
> result = "FAIL";
> }
>
> - printf("%s (%.3fs)\n", result, time_elapsed(&subtest_time, &now));
> - exit(igt_exitcode);
> + printf("%s (%.3fs)\n",
> + result, time_elapsed(&subtest_time, &now));
> }
>
> - /* Calling this without calling one of the above is a failure */
> - assert(skipped_one || succeeded_one || failed_one);
> -
> - if (failed_one)
> - exit(igt_exitcode);
> - else if (succeeded_one)
> - exit(IGT_EXIT_SUCCESS);
> - else
> - exit(IGT_EXIT_SKIP);
> + exit(igt_exitcode);
> }
>
> /* fork support code */
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2016-05-03 10:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-03 10:05 [PATCH igt] lib: compute exitcode first Chris Wilson
2016-05-03 10:22 ` Tvrtko Ursulin [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=57287BE9.3050402@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@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