From: Patchwork <patchwork@emeril.freedesktop.org>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] ✗ Fi.CI.BAT: failure for runner: Exit with 0 on dry-run
Date: Tue, 19 Feb 2019 10:11:44 -0000 [thread overview]
Message-ID: <20190219101144.5013.76934@emeril.freedesktop.org> (raw)
In-Reply-To: <20190219095853.30623-1-petri.latvala@intel.com>
== Series Details ==
Series: runner: Exit with 0 on dry-run
URL : https://patchwork.freedesktop.org/series/56887/
State : failure
== Summary ==
IGT patchset build failed on latest successful build
368e76156f752e6ed6ac32ed9f400567aef7d3fc runner: Exit with 2 when overall timeout exceeded
A file containing a list of tests to run
-o, --overwrite If the results-path already exists, delete it
--ignore-missing Ignored but accepted, for piglit compatibility
Incompatible options:
-m, --multiple-mode Run multiple subtests in the same binary execution.
If a testlist file is given, consecutive subtests are
run in the same execution if they are from the same
binary. Note that in that case relative ordering of the
subtest execution is dictated by the test binary, not
the testlist
--inactivity-timeout <seconds>
Kill the running test after <seconds> of inactivity in
the test's stdout, stderr, or dmesg
--overall-timeout <seconds>
Don't execute more tests after <seconds> has elapsed
--use-watchdog Use hardware watchdog for lethal enforcement of the
above timeout. Killing the test process is still
attempted at timeout trigger.
--piglit-style-dmesg Filter dmesg like piglit does. Piglit considers matches
against a short filter list to mean the test result
should be changed to dmesg-warn/dmesg-fail. Without
this option everything except matches against a
(longer) filter list means the test result should
change.
[test_root] Directory that contains the IGT tests. The environment
variable IGT_TEST_ROOT will be used if set, overriding
this option if given.
Cannot open /home/cidrm/igt-gpu-tools/build/tmpdirpd1NmP/test-list.txt
(runner_test:12145) CRITICAL: Test assertion failure function __real_main196, file ../runner/runner_tests.c:776:
(runner_test:12145) CRITICAL: Failed assertion: !execute(&state, &settings, &list)
(runner_test:12145) CRITICAL: Last errno: 2, No such file or directory
Subtest dry-run-option failed.
**** DEBUG ****
(runner_test:12145) CRITICAL: Test assertion failure function __real_main196, file ../runner/runner_tests.c:776:
(runner_test:12145) CRITICAL: Failed assertion: !execute(&state, &settings, &list)
(runner_test:12145) CRITICAL: Last errno: 2, No such file or directory
(runner_test:12145) igt_core-INFO: Stack trace:
(runner_test:12145) igt_core-INFO: #0 ../lib/igt_core.c:1471 __igt_fail_assert()
(runner_test:12145) igt_core-INFO: #1 ../runner/runner_tests.c:777 __real_main196()
(runner_test:12145) igt_core-INFO: #2 ../runner/runner_tests.c:196 main()
(runner_test:12145) igt_core-INFO: #3 ../csu/libc-start.c:344 __libc_start_main()
(runner_test:12145) igt_core-INFO: #4 [_start+0x2a]
**** END ****
-------
Full log written to /home/cidrm/igt-gpu-tools/build/meson-logs/testlog.txt
FAILED: meson-test
/usr/bin/python3 -u /usr/bin/meson test --no-rebuild --print-errorlogs
ninja: build stopped: subcommand failed.
_______________________________________________
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-19 10:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-19 9:58 [igt-dev] [PATCH i-g-t] runner: Exit with 0 on dry-run Petri Latvala
2019-02-19 10:11 ` Patchwork [this message]
2019-02-19 10:18 ` [igt-dev] [PATCH i-g-t v2] " Petri Latvala
2019-02-19 12:13 ` Arkadiusz Hiler
2019-02-19 11:22 ` [igt-dev] ✓ Fi.CI.BAT: success for runner: Exit with 0 on dry-run (rev2) Patchwork
2019-02-19 13:42 ` [igt-dev] ✗ Fi.CI.IGT: failure " 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=20190219101144.5013.76934@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--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