Created attachment 72049 [details] prime_udl dmesg Environment: ------------------------- Kernel: (drm-intel-next-queued)c0c36b941b6f0be6ac74f340040cbb29d6a0b06c Some additional commit info: Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Wed Dec 19 16:08:43 2012 +0000 drm/i915: Return the real error code from intel_set_mode() Description: ------------------------- After running I-G-T/prime_udl, screen output: prime_test: failed test 1 prime_test: failed test 2 -1
Blargh, we need to teach prime_udl skip support.
This should be fixed with commit c97a45ff098ba1e9772b5d1ebeedf52ec2b64652 Author: Daniel Vetter <daniel.vetter@ffwll.ch> Date: Thu Apr 4 11:36:27 2013 +0200 tests/prime_udl: skip harder in intel-gpu-tools.
Created attachment 78751 [details] dmesg: prime_udl (In reply to comment #2) > This should be fixed with > > commit c97a45ff098ba1e9772b5d1ebeedf52ec2b64652 > Author: Daniel Vetter <daniel.vetter@ffwll.ch> > Date: Thu Apr 4 11:36:27 2013 +0200 > > tests/prime_udl: skip harder > > in intel-gpu-tools. I have tried this commit and the latest intel-gpu-tools source, both of them failed on this case. I tested it with -next-queued and -nightly top. STD-OUT: -------------- [root@x-pk2 tests]# ./prime_udl failed to find intel and udl GPU
Ah, a little bit of dirt in stderr, but the test should still have correctly returned the skip error code (77). commit 53d251ac23d8a3f5c4d0144794788a1423a5fa14 Author: Daniel Vetter <daniel.vetter@ffwll.ch> Date: Thu May 2 08:10:15 2013 +0200 tests/prime_udl: don't put dirt into stderr when skipping Does your testrunner unconditionally fail a test if there's stderr output? piglit only marks it as "warn".
(In reply to comment #4) > Ah, a little bit of dirt in stderr, but the test should still have correctly > returned the skip error code (77). > > commit 53d251ac23d8a3f5c4d0144794788a1423a5fa14 > Author: Daniel Vetter <daniel.vetter@ffwll.ch> > Date: Thu May 2 08:10:15 2013 +0200 > > tests/prime_udl: don't put dirt into stderr when skipping > > > Does your testrunner unconditionally fail a test if there's stderr output? > piglit only marks it as "warn". OK, I know the return value of skipped case is 77 now, verified here.
Closing old verified.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.