Summary: | [CI][RESUME]igt@i915_pm_rpm@modeset-non-lpsp - skip - Test requirement: setup_environment(), SKIP | ||
---|---|---|---|
Product: | DRI | Reporter: | Lakshmi <lakshminarayana.vudum> |
Component: | IGT | Assignee: | Default DRI bug account <dri-devel> |
Status: | RESOLVED MOVED | QA Contact: | |
Severity: | normal | ||
Priority: | not set | CC: | intel-gfx-bugs, tomi.p.sarvela |
Version: | DRI git | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | TGL | i915 features: | power/runtime PM |
Description
Lakshmi
2019-10-22 06:07:38 UTC
The CI Bug Log issue associated to this bug has been updated. ### New filters associated * TGL: igt@i915_pm_rpm@modeset-non-lpsp - skip - Test requirement: setup_environment(), SKIP - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7104/re-tgl-u/igt@i915_pm_rpm@modeset-non-lpsp.html I'm getting access denied when trying to look at the log: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7104/re-tgl-u/igt@i915_pm_rpm@modeset-non-lpsp.html (In reply to Don Hiatt from comment #2) > I'm getting access denied when trying to look at the log: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7104/re-tgl-u/ > igt@i915_pm_rpm@modeset-non-lpsp.html CC'ing Tomi. CI_DRM_7104 re-tgl-u run was messed up due to unnecessary manual intervention here the lab: it was four overlapping runs in one. The reports have been re-run, and some of the visible results might have been changed as only one of the runs is considered valid. A CI Bug Log filter associated to this bug has been updated: {- TGL: igt@i915_pm_rpm@modeset-non-lpsp - skip - Test requirement: setup_environment(), SKIP -} {+ TGL: igt@i915_pm_rpm@modeset-non-lpsp|igt@i915_pm_rpm@gem-mmap-cpu - skip - Test requirement: setup_environment(), SKIP +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7181/re-tgl-u/igt@i915_pm_rpm@gem-mmap-cpu.html setup_environment() (tests/i915/i915_pm_rpm.c) requires that the DUT suspends, otherwise tests are skipped (as gem-mmap-cpu in the latest run). I recently added some logging to IGT (see below) and it is showing that the DUT's pm_status is active but we are expecting it to be suspended. The test only allows 10 seconds to suspend before giving up. This appears to be just a race in the IGT where occasionally DUTs take longer that 10 seconds, hence the reason we only see this occasionally. Since this is an IGT issue, I think the severity is medium. We should probably add some additional retries to close this race condition. (i915_pm_rpm:910) igt_pm-WARNING: timeout: pm_status expected:suspended, got:active Subtest gem-mmap-cpu: SKIP (In reply to Don Hiatt from comment #6) > setup_environment() (tests/i915/i915_pm_rpm.c) requires that the DUT > suspends, otherwise tests are skipped (as gem-mmap-cpu in the latest run). > > I recently added some logging to IGT (see below) and it is showing that the > DUT's pm_status is active but we are expecting it to be suspended. The test > only allows 10 seconds to suspend before giving up. This appears to be just > a race in the IGT where occasionally DUTs take longer that 10 seconds, hence > the reason we only see this occasionally. > > Since this is an IGT issue, I think the severity is medium. We should > probably add some additional retries to close this race condition. > > > (i915_pm_rpm:910) igt_pm-WARNING: timeout: pm_status expected:suspended, > got:active > Subtest gem-mmap-cpu: SKIP Changing the component to IGT. -- 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/igt-gpu-tools/issues/35. |
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.