[Bug 111208] [CI][BAT] boot - fail - no link is up in the logs

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Mon Jul 29 11:31:02 UTC 2019


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

--- Comment #6 from Arek Hiler <arkadiusz.hiler at intel.com> ---
This is kind of catch-all bug for all the boot failures, even though it claims
that no "link is up" in the logs. 

Even if we look at a successful boot for a run that we got result from (e.g.
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6545/fi-cml-u/boot0.log)  there
is nothing about network link in the boot dmesg.

So a boot failure here is defined as follows:

1. machine was responding and we deployed the new testing assets (kernel, IGT,
etc.) - at this point it's marked as "should participate in the run"
2. we haven't got any results of the machine, this can mean multiple thing:
 a) machine haven't booted to the testing kernel correctly
 b) Jenkins failed to connect to the machine
 c) igt_runner/piglit/... failed to produce results.json
 d) ...?

Sadly, we don't have any way of automatically telling one from the other yet.
We are concerned only with stderr, -out and dmesg. We would need to also import
the Jenkins' log in and probably some other extra data to be able to
effectively filter the known issues.

At this point this should be considered as purely infrastructure
issue/limitation and the results should be examined manually for any visible
patterns until we improve. Customer impact: none.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20190729/50da9e69/attachment-0001.html>


More information about the intel-gfx-bugs mailing list