| What | Removed | Added |
|---|---|---|
| Assignee | intel-gfx-bugs@lists.freedesktop.org | dri-devel@lists.freedesktop.org |
| QA Contact | intel-gfx-bugs@lists.freedesktop.org | |
| Component | DRM/Intel | IGT |
Moving to IGT as this is something the tests need to learn how= to deal with.
The CI Bug Log issue associated to this bug has been updated. ### New filters associated * CHAMELIUM: igt@kms_chamelium@*suspend* - warn - Last errno: 113, = No route to host - https://inte= l-gfx-ci.01.org/tree/drm-tip/Patchwork_11299/fi-kbl-7567u/igt@kms_chame= lium@common-hpd-after-suspend.html - https://intel-gfx= -ci.01.org/tree/drm-tip/IGTPW_2246/fi-kbl-7567u/igt@kms_chamelium@c= ommon-hpd-after-suspend.html - https://inte= l-gfx-ci.01.org/tree/drm-tip/Patchwork_11973/fi-kbl-7567u/igt@kms_chame= lium@common-hpd-after-suspend.html - https://intel-gfx= -ci.01.org/tree/drm-tip/IGTPW_2256/fi-kbl-7567u/igt@kms_chamelium@c= ommon-hpd-after-suspend.html - https://intel-gfx= -ci.01.org/tree/drm-tip/IGTPW_2259/fi-kbl-7567u/igt@kms_chamelium@c= ommon-hpd-after-suspend.html
A CI Bug Log filter associated to this bug has been updated:
{- CHAMELIUM: igt@kms_chamelium@*suspend* - warn - Last errno: 113,=
No route to
host -}
{+ CHAMELIUM: igt@kms_chamelium@* - warn/fail - Last errno: 113, No=
route to
host +}
New failures caught by the filter:
*
https://intel-gfx-c=
i.01.org/tree/drm-tip/drmtip_284/fi-kbl-7500u/igt@kms_chamelium@hdm=
i-cmp-planes-random.html
*
https://intel-gfx-c=
i.01.org/tree/drm-tip/drmtip_284/fi-kbl-7567u/igt@kms_chamelium@hdm=
i-cmp-planes-random.html
*
https://intel-gfx-ci.01.org/tree/=
drm-tip/drmtip_285/fi-kbl-7500u/igt@kms_chamelium@dp-audio.html
*
https://intel-gfx-ci.01.org/tree/=
drm-tip/drmtip_285/fi-kbl-7567u/igt@kms_chamelium@dp-audio.html=
| What | Removed | Added |
|---|---|---|
| Summary | [CI][BAT] igt@kms_chamelium@*suspend* - warn - Last = errno: 113, No route to host | [CI][BAT] igt@kms_chamelium@*- warn/fail - Last errn= o: 113, No route to host |
| What | Removed | Added |
|---|---|---|
| Priority | medium | high |
Other than occasional flukes here and there the biggest offend= er seems to be *after-suspend* family of subtest. The most representative scenario looks like that: 1. schedule something on chamelium 2. got to sleep 3. scheduled thing triggers 4. wake up 5. check whether we see the changes reflected through DRM and pass 6. exit triggring chamelium cleanup During 6 we have a failed RPC because network is not up yet after waking up, which overwrites the test results to WARN. Solution: introduce chamelium_wait_online(int timeout) that pings the device and bails out after timeout. Always call it after waking up. Everything else looks like sporadic network issues, but we have seen it jus= t a few times in the last months. We can investigate them further once we will = get rid of the main source of the noise. Impact on users: none, it's a CI/test issue. Impact on testing: potentially huge, as some of the tests may leave us with chamelium ports unplugged adding to the flip-flopping of the 2x tests. Bumping priority to high, as it is easy to solve and important for keeping = the CI noise down.
Related bug about Chamelium not having all ports plugged in: