All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 109380] [CI][BAT] igt@kms_chamelium@*- warn/fail - Last errno: 113, No route to host
Date: Fri, 16 Aug 2019 07:47:55 +0000	[thread overview]
Message-ID: <bug-109380-502-LZmYoqEvgR@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-109380-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1566 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=109380

Arek Hiler <arkadiusz.hiler@intel.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|medium                      |high

--- Comment #4 from Arek Hiler <arkadiusz.hiler@intel.com> ---
Other than occasional flukes here and there the biggest offender 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 just 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.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2993 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2019-08-16  7:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-109380-502@http.bugs.freedesktop.org/>
2019-01-18 12:39 ` [Bug 109380] [CI][BAT] igt@kms_chamelium@*suspend* - warn - Last errno: 113, No route to host bugzilla-daemon
2019-01-18 12:39 ` bugzilla-daemon
2019-05-15  6:33 ` bugzilla-daemon
2019-05-15  6:35 ` [Bug 109380] [CI][BAT] igt@kms_chamelium@*- warn/fail " bugzilla-daemon
2019-08-16  7:47 ` bugzilla-daemon [this message]
2019-08-16  8:36 ` bugzilla-daemon
2019-08-16 13:31 ` bugzilla-daemon
2019-08-20  4:56 ` bugzilla-daemon
2019-09-05 11:06 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-109380-502-LZmYoqEvgR@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.