From: Patchwork <patchwork@emeril.freedesktop.org>
To: Ramalingam C <ramalingam.c@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: [igt-dev] ✗ Fi.CI.BAT: failure for kms_content_protection: Add Content Protection test
Date: Thu, 11 Oct 2018 14:34:40 -0000 [thread overview]
Message-ID: <20181011143440.403.25234@emeril.freedesktop.org> (raw)
In-Reply-To: <1539267515-3768-1-git-send-email-ramalingam.c@intel.com>
== Series Details ==
Series: kms_content_protection: Add Content Protection test
URL : https://patchwork.freedesktop.org/series/50869/
State : failure
== Summary ==
IGT patchset build failed on latest successful build
54cb1aeb4e50dea9f3abae632e317875d147c4ab tests: Add chamelium formats subtests to vc4 test lists
230/254 testcase check: vgem_basic OK 0.08 s
231/254 testcase check: vgem_slow OK 0.07 s
232/254 testcase check: prime_nv_api OK 0.09 s
233/254 testcase check: prime_nv_pcopy OK 0.10 s
234/254 testcase check: prime_nv_test OK 0.10 s
235/254 testcase check: kms_chamelium OK 0.07 s
236/254 testcase check: gem_eio OK 0.08 s
237/254 testcase check: gem_mocs_settings OK 0.06 s
238/254 testcase check: perf_pmu OK 0.08 s
239/254 testcase check: testdisplay OK 0.08 s
240/254 testcase check: amdgpu/amd_basic OK 0.09 s
241/254 testcase check: amdgpu/amd_cs_nop OK 0.07 s
242/254 testcase check: amdgpu/amd_prime OK 0.07 s
243/254 runner OK 1.32 s
244/254 assembler: test/mov OK 0.02 s
245/254 assembler: test/frc OK 0.02 s
246/254 assembler: test/regtype OK 0.02 s
247/254 assembler: test/rndd OK 0.02 s
248/254 assembler: test/rndu OK 0.01 s
249/254 assembler: test/rnde OK 0.01 s
250/254 assembler: test/rnde-intsrc OK 0.02 s
251/254 assembler: test/rndz OK 0.01 s
252/254 assembler: test/lzd OK 0.02 s
253/254 assembler: test/not OK 0.01 s
254/254 assembler: test/immediate OK 0.01 s
OK: 253
FAIL: 1
SKIP: 0
TIMEOUT: 0
The output from the failed tests:
167/254 testcase check: kms_content_protection FAIL 0.07 s
--- command ---
/home/cidrm/igt-gpu-tools/tests/igt_command_line.sh kms_content_protection
--- stdout ---
tests/kms_content_protection:
Checking invalid option handling...
Checking valid option handling...
Checking subtest enumeration...
FAIL: tests/kms_content_protection
-------
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:[~2018-10-11 14:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-11 14:18 [igt-dev] [PATCH i-g-t] kms_content_protection: Add Content Protection test Ramalingam C
2018-10-11 14:34 ` Patchwork [this message]
2018-10-11 15:03 ` Daniel Vetter
2018-10-12 13:53 ` C, Ramalingam
2018-10-12 14:02 ` [igt-dev] [PATCH i-g-t v2] " Ramalingam C
2018-10-17 11:53 ` [igt-dev] [PATCH i-g-t v3] " Ramalingam C
2018-10-12 16:36 ` [igt-dev] ✓ Fi.CI.BAT: success for kms_content_protection: Add Content Protection test (rev2) Patchwork
2018-10-12 19:10 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2018-10-17 13:17 ` [igt-dev] ✗ Fi.CI.BAT: failure for kms_content_protection: Add Content Protection test (rev3) Patchwork
2018-10-17 15:21 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2018-10-17 18:20 ` [igt-dev] ✓ Fi.CI.IGT: " 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=20181011143440.403.25234@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=igt-dev@lists.freedesktop.org \
--cc=ramalingam.c@intel.com \
/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