https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_28/fi-bdw-gvtdvm/igt@perf@buffer-fill.html (perf:2910) CRITICAL: Test assertion failure function test_buffer_fill, file ../tests/perf.c:2471: (perf:2910) CRITICAL: Failed assertion: n_periodic_reports * report_size > report_size * n_full_oa_reports * 0.45 Subtest buffer-fill failed.
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_49/fi-bdw-gvtdvm/igt@perf@enable-disable.html (perf:1642) CRITICAL: Test assertion failure function test_enable_disable, file ../tests/perf.c:2609: (perf:1642) CRITICAL: Failed assertion: (n_periodic_reports * report_size) > (report_size * n_full_oa_reports * 0.45) Subtest enable-disable failed.
Also seen on SKL: https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_80/fi-skl-gvtdvm/igt@perf@enable-disable.html (perf:1194) CRITICAL: Test assertion failure function test_enable_disable, file ../tests/perf.c:2613: (perf:1194) CRITICAL: Failed assertion: (n_periodic_reports * report_size) > (report_size * n_full_oa_reports * 0.45) Subtest enable-disable failed.(pe
Also seen is a slight different variant: https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_90/fi-bdw-gvtdvm/igt@perf@buffer-fill.html (perf:1431) CRITICAL: Test assertion failure function test_buffer_fill, file ../tests/perf.c:2475: (perf:1431) CRITICAL: Failed assertion: n_periodic_reports * report_size > report_size * n_full_oa_reports * 0.45 Subtest buffer-fill failed.
The test verifies enable/disable function of report generation into the OA buffer. - Open a perf stream with report generation disabled - Ensure that there are no reports generated for time duration that it takes to fill the entire buffer - Enable report generation - Wait for the half the OA buffer to be filled (based on report periodicity, report size and OA buffer size) - Read all reports generated until the delta between first and the last read report matches half the time taken to fill the entire OA buffer. - Make sure that the number of reports generated is within 45% to 55% of the expected number of reports. The failure is that the number of reports do not fall in this range. Machines affected: skl and bdw Repro rate: 0.6% The test seems to ignore spurious reports and hence falls short of 45% by 10 - 15 reports. Test logic must be updated to reflect spurious reports by checking if the timestamp delta between the previous and current reports is greater than the periodic interval. Severity: Low Priority: Medium
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/intel/issues/114.
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.