All shards IGT_4018, note Ci is under 4.15.0-rc1 fire at this time so maybe this is related to the fire. https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4018/shard-apl6/igt@perf_pmu@invalid-init.html https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4018/shard-glkb1/igt@perf_pmu@invalid-init.html https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4018/shard-hsw7/igt@perf_pmu@invalid-init.html https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4018/shard-kbl7/igt@perf_pmu@invalid-init.html https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4018/shard-snb2/igt@perf_pmu@invalid-init.html (perf_pmu:2301) CRITICAL: Test assertion failure function invalid_init, file perf_pmu.c:691: (perf_pmu:2301) CRITICAL: Failed assertion: (*__errno_location ()) == 22 (perf_pmu:2301) CRITICAL: Last errno: 19, No such device (perf_pmu:2301) CRITICAL: error: 19 != 22 Subtest invalid-init failed.
Just a small miscoordination between the kernel and igt both requiring an update. commit 380cc811486ba3fefbe3ebe4761afa7e169dcd3e (origin/master, origin/HEAD) Author: Tvrtko Ursulin <tvrtko.ursulin@intel.com> Date: Tue Nov 28 10:55:36 2017 +0000 tests/perf_pmu: Sync invalid-init with i915 changes i915 started returning -EINVAL for incorrect CPU. Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
The patch was merged to CI_DRM_3402, the issue have never been seen on CI. So I am fine closing it.
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.