CI_DRM_3126 new IGT tests: igt@gem_concurrent_blit@4kib-tiny-prw-blt-overwrite-source-read-rcs-child igt@gem_concurrent_blit@4kib-tiny-prw-blt-intermix-bcs-child incompletes SNB-shards. https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3126/shard-snb5/igt@gem_concurrent_blit@4kib-tiny-prw-blt-overwrite-source-read-rcs-child.html https://intel-gfx-ci.01.org/tree/drm-tip/igt@gem_concurrent_blit@4kib-tiny-prw-blt-intermix-bcs-child.html
<marta_> Adrinael, you mentioned something about being wrong testlist for shards on CI_DRM_3026, could you elaborate. I have already filed bugs for this run... <Adrinael> CI_DRM_3126 <Adrinael> It was running everything ever on accident <Adrinael> ivyl, ^ right? <marta_> but it was only 3 new drv_selftests and 3 new gem tests, for sure we have more than that blacklisted <ivyl> yep, due to elaborated nature of deployment method, and streamilining it to use just "make install" an inevitable error occured on the human-Jenkins boundary. <ivyl> marta_: it run with ALL ALL, but it got cancelled pretty quickly <ivyl> and then rerun properly <ivyl> what you see is the merge of both <Adrinael> tools_test@* got "broken" by make install -deployment btw * Weine (~dweineha@134.134.139.76) has joined <ivyl> as jenkins haven't cleaned staging area for results <Adrinael> marta_, if you file a bug on igt@tools_test@tools_test, make it an IGT bug <ivyl> so sorry about confusion, it wasn't intended and I hoped the rerun will fix it <ivyl> but as you can see we have the few leftovers <marta_> OK, I will archive if needed when I results from the next run. * Ahuj (Thunderbir@nat/intel/x-ngcmqbhsvahecvri) has joined <ivyl> results from -27 already came in and they look clean, we also should have results for -28 in half an hour or so <marta_> dolphin, disregard my comments on BUGS: 102970 and 102971 ^^. These test should not have been part of CI_DRM_3026, I will archive the bugs from cibuglog, but of course we will keep them in fdo.
That's not a test bug; the shard run timed out.
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.