| Summary: | [CI] igt@perf_pmu@multi-client-vcs0 - fail - Failed assertion: (double)(val[1]) <= (1.0 + (tolerance)) * (double)(slept) && (double)(val[1]) >= (1.0 - (tolerance)) * (double)(slept) | ||
|---|---|---|---|
| Product: | DRI | Reporter: | Marta Löfstedt <marta.lofstedt> |
| Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
| Status: | CLOSED FIXED | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
| Severity: | normal | ||
| Priority: | medium | CC: | intel-gfx-bugs |
| Version: | DRI git | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | ReadyForDev | ||
| i915 platform: | HSW | i915 features: | Perf/OA |
|
Description
Marta Löfstedt
2017-11-27 09:11:37 UTC
*** This bug has been marked as a duplicate of bug 103886 *** reproduced: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4014/shard-hsw8/igt@perf_pmu@multi-client-vcs0.html (perf_pmu:5578) CRITICAL: Test assertion failure function multi_client, file perf_pmu.c:655: (perf_pmu:5578) CRITICAL: Failed assertion: (double)(val[1]) <= (1.0 + (tolerance)) * (double)(slept) && (double)(val[1]) >= (1.0 - (tolerance)) * (double)(slept) (perf_pmu:5578) CRITICAL: 'val[1]' != 'slept' (150000000.000000 not within 5.000000% tolerance of 166748714.000000) Subtest multi-client-vcs0 failed. commit 53f2b4b4ce2372da0b3b741d934dd5a9110ac1e2 (HEAD, upstream/master) Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Mon Nov 27 10:52:40 2017 +0000 igt/perf_pmu: Keep batch_duration_ns as the minimum measurement duration We have chosen batch_duration_ns to be the minimum duration we need to meet our accuracy requirements for legacy ringbuffer PMU sampling. As such, we need to be careful to use multiples of it during tests, and not split it into different phases within a test, like multi_client does. Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com> Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com> |
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.