From: Petri Latvala <petri.latvala@intel.com>
To: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t] tests/igt_command_line.sh: Log what went wrong
Date: Mon, 11 Nov 2019 12:13:57 +0200 [thread overview]
Message-ID: <20191111101357.GN25209@platvala-desk.ger.corp.intel.com> (raw)
In-Reply-To: <20191108144957.312005-1-arkadiusz.hiler@intel.com>
On Fri, Nov 08, 2019 at 04:49:57PM +0200, Arkadiusz Hiler wrote:
> The following error looks quite mysterious:
>
> $ ../../tests/igt_command_line.sh kms_ccs
> ./kms_ccs:
> Checking invalid option handling...
> Checking valid option handling...
> Checking subtest enumeration...
> FAIL: ./kms_ccs
>
> Let's add some explanation when we fail the subtests enumeration checks
> so people are not completely baffled when they get failures from the CI.
>
> Cc: Mika Kahola <mika.kahola@intel.com>
> Cc: Petri Latvala <petri.latvala@intel.com>
> Signed-off-by: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
Reviewed-by: Petri Latvala <petri.latvala@intel.com>
> ---
> tests/igt_command_line.sh | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/tests/igt_command_line.sh b/tests/igt_command_line.sh
> index a019e3a5..291b6526 100755
> --- a/tests/igt_command_line.sh
> +++ b/tests/igt_command_line.sh
> @@ -79,10 +79,12 @@ check_test ()
> LIST=`./$test --list-subtests`
> RET=$?
> if [ $RET -ne 0 -a $RET -ne 79 ]; then
> + echo " test does not exit with 0 or 79 with --list-subtests!"
> fail $test
> fi
>
> if [ $RET -eq 79 -a -n "$LIST" ]; then
> + echo " test seems to be using igt_simple_main() (no subtests) and yet --list-subtests is NOT empty!"
> fail $test
> fi
>
> @@ -91,6 +93,7 @@ check_test ()
> # on the running kernel. If selftests are not enabled,
> # they will output nothing and exit with 0.
> if [ "$testname" != "i915_selftest" -a "$testname" != "drm_mm" -a "$testname" != "kms_selftest" -a "$testname" != "dmabuf" ]; then
> + echo " test does seem to be using igt_main() (should have subtests) and yet --list-subtests is empty!"
> fail $test
> fi
> fi
> --
> 2.23.0
>
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
prev parent reply other threads:[~2019-11-11 10:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-08 14:49 [igt-dev] [PATCH i-g-t] tests/igt_command_line.sh: Log what went wrong Arkadiusz Hiler
2019-11-08 15:45 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2019-11-10 6:17 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2019-11-11 10:13 ` Petri Latvala [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=20191111101357.GN25209@platvala-desk.ger.corp.intel.com \
--to=petri.latvala@intel.com \
--cc=arkadiusz.hiler@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