| Summary: | [CI][SHARDS] igt@perf_pmu@busy-double-start-vecs0 - fail - Failed assertion: val2 == 0 | ||
|---|---|---|---|
| Product: | DRI | Reporter: | Martin Peres <martin.peres> |
| Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
| Status: | RESOLVED MOVED | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
| Severity: | normal | ||
| Priority: | low | CC: | intel-gfx-bugs |
| Version: | XOrg git | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | SKL | i915 features: | Perf/PMU |
|
Description
Martin Peres
2019-08-20 06:59:36 UTC
The CI Bug Log issue associated to this bug has been updated. ### New filters associated * SKL: igt@perf_pmu@busy-double-start-vecs0 - fail - Failed assertion: val2 == 0 - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6736/shard-skl10/igt@perf_pmu@busy-double-start-vecs0.html A CI Bug Log filter associated to this bug has been updated:
{- SKL: igt@perf_pmu@busy-double-start-vecs0 - fail - Failed assertion: val2 == 0 -}
{+ SKL: igt@perf_pmu@busy-double-start-(vecs0|vcs0) - fail - Failed assertion: val2 == 0 +}
New failures caught by the filter:
* https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6824/shard-skl2/igt@perf_pmu@busy-double-start-vcs0.html
Setting the priority and severity of this bug top default as this bug is not assessed yet. A CI Bug Log filter associated to this bug has been updated:
{- SKL: igt@perf_pmu@busy-double-start-(vecs0|vcs0) - fail - Failed assertion: val2 == 0 -}
{+ SKL: igt@perf_pmu@busy-double-start-(vecs0|vcs0|bcs0) - fail - Failed assertion: val2 == 0 +}
New failures caught by the filter:
* https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6917/shard-skl7/igt@perf_pmu@busy-double-start-bcs0.html
Tests the busyness of engine after 2 batches are running as well as after the engine is idle. The failure is that the value after idle (val2) is not 0 meaning the perf pmu reports busyness even after waiting for engine to idle. Machines affected: SKL Repro rate: 30% The test documents that it has a higher rate of false positives, hence setting priority to low. -- 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/377. |
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.