Summary: | [CI][SHARDS] igt@vgem_basic@unload - skip - Test requirement: module_unload() == 0, Last errno: 11, Resource temporarily unavailable, SKIP | ||
---|---|---|---|
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: | not set | ||
Priority: | not set | CC: | intel-gfx-bugs |
Version: | XOrg git | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | ReadyForDev | ||
i915 platform: | ICL | i915 features: |
Description
Martin Peres
2019-03-28 12:49:25 UTC
*** This bug has been marked as a duplicate of bug 110274 *** https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3545/shard-iclb4/igt@vgem_basic@unload.html Starting subtest: unload Test requirement not met in function test_unload, file ../tests/vgem_basic.c:335: Test requirement: module_unload() == 0 Last errno: 11, Resource temporarily unavailable Subtest unload: SKIP (0.016s) The CI Bug Log issue associated to this bug has been updated. ### New filters associated * ICL: igt@vgem_basic@unload - skip - Test requirement: module_unload() == 0, SKIP - https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3545/shard-iclb4/igt@vgem_basic@unload.html Why reopening this and not the one it's a duplicate of? (In reply to Francesco Balestrieri from comment #4) > Why reopening this and not the one it's a duplicate of? Bug 110274 was archived. Since both the issues are exactly the same, no difference in Bug 110274 and Bug 110272. The above skip has appeared in pre-merge testing. There's no oops; userspace has the vgem /dev/dri/cardN open somewhere. -- 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/254. |
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.