| Summary: | [Ci] igt@perf_pmu@semaphore-wait-* - fail - Failed assertion: (double)(val[1] - val[0]) <= (1.0 + (tolerance)) * (double)(slept) && (double)(val[1] - val[0]) >= (1.0 - (tolerance)) * (double)(slept) (perf_pmu:21315) CRITICAL: 'val[1] - val[0]' != | ||
|---|---|---|---|
| Product: | DRI | Reporter: | Marta Löfstedt <marta.lofstedt> |
| Component: | DRM/Intel | Assignee: | Kimmo Nikkanen <knikkane> |
| Status: | CLOSED WORKSFORME | 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: | BXT, GLK | i915 features: | Perf/PMU |
|
Description
Marta Löfstedt
2018-02-08 06:50:43 UTC
I pulled in these from bug 104829 https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3712/shard-apl1/igt@perf_pmu@semaphore-wait-vecs0.html https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3712/shard-glkb3/igt@perf_pmu@semaphore-wait-vecs0.html https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3707/shard-apl7/igt@perf_pmu@semaphore-wait-bcs0.html https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3706/shard-glkb6/igt@perf_pmu@semaphore-wait-bcs0.html https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4231/shard-glkb2/igt@perf_pmu@semaphore-wait-idle-bcs0.html (perf_pmu:1850) CRITICAL: Test assertion failure function sema_wait, file perf_pmu.c:631: (perf_pmu:1850) CRITICAL: Failed assertion: (double)(val[1] - val[0]) <= (1.0 + (tolerance)) * (double)(slept) && (double)(val[1] - val[0]) >= (1.0 - (tolerance)) * (double)(slept) (perf_pmu:1850) CRITICAL: 'val[1] - val[0]' != 'slept' (445000000.000000 not within 5.000000% tolerance of 500340906.000000) Subtest semaphore-wait-idle-bcs0 failed. https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4231/shard-apl6/igt@perf_pmu@semaphore-wait-idle-bcs0.html (perf_pmu:1818) CRITICAL: Test assertion failure function sema_wait, file perf_pmu.c:631: (perf_pmu:1818) CRITICAL: Failed assertion: (double)(val[1] - val[0]) <= (1.0 + (tolerance)) * (double)(slept) && (double)(val[1] - val[0]) >= (1.0 - (tolerance)) * (double)(slept) (perf_pmu:1818) CRITICAL: 'val[1] - val[0]' != 'slept' (470000000.000000 not within 5.000000% tolerance of 500020929.000000) Subtest semaphore-wait-idle-bcs0 failed. https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4248/shard-glkb3/igt@perf_pmu@semaphore-wait-idle-rcs0.html (perf_pmu:1603) CRITICAL: Test assertion failure function sema_wait, file perf_pmu.c:637: (perf_pmu:1603) CRITICAL: Failed assertion: (double)(val[1] - val[0]) <= (1.0 + (tolerance)) * (double)(slept) && (double)(val[1] - val[0]) >= (1.0 - (tolerance)) * (double)(slept) (perf_pmu:1603) CRITICAL: 'val[1] - val[0]' != 'slept' (450000000.000000 not within 5.000000% tolerance of 500144729.000000) Subtest semaphore-wait-idle-rcs0 failed. https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4251/shard-apl4/igt@perf_pmu@semaphore-wait-rcs0.html (perf_pmu:2067) CRITICAL: Test assertion failure function sema_wait, file perf_pmu.c:637: (perf_pmu:2067) CRITICAL: Failed assertion: (double)(val[1] - val[0]) <= (1.0 + (tolerance)) * (double)(slept) && (double)(val[1] - val[0]) >= (1.0 - (tolerance)) * (double)(slept) (perf_pmu:2067) CRITICAL: 'val[1] - val[0]' != 'slept' (475000000.000000 not within 5.000000% tolerance of 500339680.000000) Subtest semaphore-wait-rcs0 failed. https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3777/shard-glkb1/igt@perf_pmu@semaphore-wait-vcs0.html (perf_pmu:1610) CRITICAL: Test assertion failure function sema_wait, file perf_pmu.c:648: (perf_pmu:1610) CRITICAL: Failed assertion: (double)(val[1] - val[0]) <= (1.0 + (tolerance)) * (double)(slept) && (double)(val[1] - val[0]) >= (1.0 - (tolerance)) * (double)(slept) (perf_pmu:1610) CRITICAL: 'val[1] - val[0]' != 'slept' (450000000.000000 not within +5.000000%/-5.000000% tolerance of 500354890.000000) Subtest semaphore-wait-vcs0 failed. Last seen: CI_DRM_3785: 2018-02-16 / 235 runs ago |
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.