[Bug 111318] New: [CI][DRMTIP] igt at kms_chamelium@dp-mode-timings - fail - Chamelium RPC call failed: libcurl failed to execute the HTTP POST transaction, explaining: Failed to connect to .* No route to host

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Wed Aug 7 12:42:24 UTC 2019


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

            Bug ID: 111318
           Summary: [CI][DRMTIP] igt at kms_chamelium@dp-mode-timings - fail
                    -  Chamelium RPC call failed: libcurl failed to
                    execute the HTTP POST transaction, explaining:  Failed
                    to connect to .* No route to host
           Product: DRI
           Version: DRI git
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: lakshminarayana.vudum at intel.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_337/fi-kbl-7500u/igt@kms_chamelium@dp-mode-timings.html

https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_337/fi-kbl-7567u/igt@kms_chamelium@dp-mode-timings.html

kms_chamelium:1395) igt_chamelium-CRITICAL: Failed assertion:
!chamelium->env.fault_occurred
(kms_chamelium:1395) igt_chamelium-CRITICAL: Last errno: 113, No route to host
(kms_chamelium:1395) igt_chamelium-CRITICAL: Chamelium RPC call failed: libcurl
failed to execute the HTTP POST transaction, explaining:  Failed to connect to
192.168.1.224 port 9992: No route to host
Test kms_chamelium failed.

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


More information about the intel-gfx-bugs mailing list