public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: Emil Velikov <emil.l.velikov@gmail.com>
Cc: igt-dev@lists.freedesktop.org
Subject: [igt-dev] ✗ Fi.CI.BAT: failure for tests/core_unauth_vs_render: new test for the relaxed DRM_AUTH handling (rev2)
Date: Wed, 06 Feb 2019 13:25:40 -0000	[thread overview]
Message-ID: <20190206132540.9302.94645@emeril.freedesktop.org> (raw)
In-Reply-To: <20190206131828.17018-1-emil.l.velikov@gmail.com>

== Series Details ==

Series: tests/core_unauth_vs_render: new test for the relaxed DRM_AUTH handling (rev2)
URL   : https://patchwork.freedesktop.org/series/55149/
State : failure

== Summary ==

IGT patchset build failed on latest successful build
592b854fead32c2b0dac7198edfb9a6bffd66932 tools/intel_watermark: Clean up the platform checks in the ilk+ code


OK:       266
FAIL:       1
SKIP:       0
TIMEOUT:    0


The output from the failed tests:

 19/267 testcase check: core_unauth_vs_render   FAIL     0.35 s

--- command ---
/home/cidrm/igt-gpu-tools/tests/igt_command_line.sh core_unauth_vs_render
--- stdout ---
tests/core_unauth_vs_render:
  Checking invalid option handling...
  Checking valid option handling...
  Checking subtest enumeration...
FAIL: tests/core_unauth_vs_render
--- stderr ---
(core_unauth_vs_render:31889) CRITICAL: Test assertion failure function __real_main166, file ../tests/core_unauth_vs_render.c:173:
(core_unauth_vs_render:31889) CRITICAL: Failed assertion: check_auth(master) == true
(core_unauth_vs_render:31889) CRITICAL: Last errno: 9, Bad file descriptor
Test core_unauth_vs_render failed.
**** DEBUG ****
(core_unauth_vs_render:31889) CRITICAL: Test assertion failure function __real_main166, file ../tests/core_unauth_vs_render.c:173:
(core_unauth_vs_render:31889) CRITICAL: Failed assertion: check_auth(master) == true
(core_unauth_vs_render:31889) CRITICAL: Last errno: 9, Bad file descriptor
****  END  ****
core_unauth_vs_render: ../lib/igt_core.c:1143: igt_fail: Assertion `igt_can_fail()' failed.
Received signal SIGABRT.
Stack trace: 
 #0 [fatal_sig_handler+0xd5]
 #1 [killpg+0x40]
 #2 [gsignal+0xc7]
 #3 [abort+0x141]
 #4 [uselocale+0x33a]
 #5 [__assert_fail+0x42]
 #6 [igt_fail+0xe4]
 #7 [__igt_fail_assert+0x198]
 #8 [__real_main166+0x91]
 #9 [main+0x44]
 #10 [__libc_start_main+0xe7]
 #11 [_start+0x2a]
-------

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

  reply	other threads:[~2019-02-06 13:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-06 13:18 [igt-dev] [PATCH i-g-t] tests/core_unauth_vs_render: new test for the relaxed DRM_AUTH handling Emil Velikov
2019-02-06 13:25 ` Patchwork [this message]
2019-02-07  8:59 ` Petri Latvala
2019-02-07 12:00   ` Emil Velikov
2019-02-07 12:08     ` Petri Latvala
2019-02-07 14:17 ` Daniel Vetter
2019-02-07 17:08   ` Emil Velikov
2019-02-07 17:47     ` Daniel Vetter

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=20190206132540.9302.94645@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=emil.l.velikov@gmail.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