Bug 109555 - [CI][DRMTIP] igt@kms_cursor_legacy@2x-long-flip-vs-cursor-legacy - dmesg-fail - Failed assertion: !ret\n[^\n]+Last errno: 2, No such file or directory
Summary: [CI][DRMTIP] igt@kms_cursor_legacy@2x-long-flip-vs-cursor-legacy - dmesg-fail...
Status: CLOSED WORKSFORME
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: DRI git
Hardware: Other All
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard: Triaged, ReadyForDev
Keywords:
Depends on:
Blocks:
 
Reported: 2019-02-05 08:06 UTC by Lakshmi
Modified: 2019-05-27 07:18 UTC (History)
2 users (show)

See Also:
i915 platform: ICL
i915 features:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lakshmi 2019-02-05 08:06:53 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_204/fi-icl-u2/igt@kms_cursor_legacy@2x-long-flip-vs-cursor-legacy.html

https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_205/fi-icl-u2/igt@kms_cursor_legacy@2x-long-flip-vs-cursor-legacy.html

Starting subtest: 2x-long-flip-vs-cursor-legacy
(kms_cursor_legacy:1232) CRITICAL: Test assertion failure function flip_nonblocking, file ../tests/kms_cursor_legacy.c:265:
(kms_cursor_legacy:1232) CRITICAL: Failed assertion: !ret
(kms_cursor_legacy:1232) CRITICAL: Last errno: 2, No such file or directory
Subtest 2x-long-flip-vs-cursor-legacy failed.
Comment 1 CI Bug Log 2019-02-11 07:28:52 UTC
The CI Bug Log issue associated to this bug has been updated.

### New filters associated

* ICL: igt@kms_cursor_legacy@2x-long-flip-vs-cursor-legacy - dmesg-fail - Failed assertion: !ret\n[^\n]+Last errno: 2, No such file or directory (No new failures associated)
Comment 2 CI Bug Log 2019-04-11 10:06:45 UTC
A CI Bug Log filter associated to this bug has been updated:

{- ICL: igt@kms_cursor_legacy@2x-long-flip-vs-cursor-legacy - dmesg-fail - Failed assertion: !ret\n[^\n]+Last errno: 2, No such file or directory -}
{+ ICL: igt@kms_cursor_legacy@2x-long-flip-vs-cursor-legacy - dmesg-fail - Failed assertion: !ret +}

 No new failures caught with the new filter
Comment 3 Lakshmi 2019-04-11 10:14:46 UTC
(In reply to Lakshmi from comment #0)
> https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_204/fi-icl-u2/
> igt@kms_cursor_legacy@2x-long-flip-vs-cursor-legacy.html
> 
> https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_205/fi-icl-u2/
> igt@kms_cursor_legacy@2x-long-flip-vs-cursor-legacy.html
> 
> Starting subtest: 2x-long-flip-vs-cursor-legacy
> (kms_cursor_legacy:1232) CRITICAL: Test assertion failure function
> flip_nonblocking, file ../tests/kms_cursor_legacy.c:265:
> (kms_cursor_legacy:1232) CRITICAL: Failed assertion: !ret
> (kms_cursor_legacy:1232) CRITICAL: Last errno: 2, No such file or directory
> Subtest 2x-long-flip-vs-cursor-legacy failed.

No new failures reported yet on this bug.
Comment 4 Jani Saarinen 2019-04-25 18:57:25 UTC
Happened only once and no history available can this be closed?
Comment 5 CI Bug Log 2019-05-27 07:14:03 UTC
A CI Bug Log filter associated to this bug has been updated:

{- ICL: igt@kms_cursor_legacy@2x-long-flip-vs-cursor-legacy - dmesg-fail - Failed assertion: !ret -}
{+ ICL: igt@kms_cursor_legacy@2x-long-flip-vs-cursor-legacy - dmesg-fail - Failed assertion: !ret +}


  No new failures caught with the new filter
Comment 6 CI Bug Log 2019-05-27 07:14:32 UTC
A CI Bug Log filter associated to this bug has been updated:

{- ICL: igt@kms_cursor_legacy@2x-long-flip-vs-cursor-legacy - dmesg-fail - Failed assertion: !ret -}
{+ ICL: igt@kms_cursor_legacy@2x-long-flip-vs-cursor-legacy - dmesg-fail - Failed assertion: !ret +}


  No new failures caught with the new filter
Comment 7 Lakshmi 2019-05-27 07:17:01 UTC
This failure occurred only once 3 months ago. Closing this bug as WORKSFORME.
Comment 8 CI Bug Log 2019-05-27 07:18:40 UTC
The CI Bug Log issue associated to this bug has been archived.

New failures matching the above filters will not be associated to this bug anymore.


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.