Summary: | [CI] igt@kms_chamelium@* - fail - Failed assertion: !chamelium->env.fault_occurred - Last errno: 101, Network is unreachable (kms_chamelium:2833) igt_chamelium-CRITICAL: Chamelium RPC call failed: libcurl failed to execute the HTTP POST transaction, expl | ||
---|---|---|---|
Product: | DRI | Reporter: | Marta Löfstedt <marta.lofstedt> |
Component: | IGT | Assignee: | Default DRI bug account <dri-devel> |
Status: | CLOSED WORKSFORME | QA Contact: | |
Severity: | normal | ||
Priority: | medium | CC: | intel-gfx-bugs |
Version: | DRI git | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | ReadyForDev | ||
i915 platform: | KBL, SKL | i915 features: | display/Other |
Description
Marta Löfstedt
2018-03-19 07:58:43 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_3/fi-kbl-7500u/igt@kms_chamelium@dp-frame-dump.html https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_3/fi-skl-6700k2/igt@kms_chamelium@dp-frame-dump.html (kms_chamelium:2087) igt_chamelium-CRITICAL: Test assertion failure function chamelium_rpc, file ../lib/igt_chamelium.c:302: (kms_chamelium:2087) igt_chamelium-CRITICAL: Failed assertion: !chamelium->env.fault_occurred (kms_chamelium:2087) igt_chamelium-CRITICAL: Last errno: 101, Network is unreachable (kms_chamelium:2087) igt_chamelium-CRITICAL: Chamelium RPC call failed: libcurl failed to execute the HTTP POST transaction, explaining: Couldn't connect to server Test kms_chamelium failed. There is also these: https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_3/fi-kbl-7500u/igt@kms_chamelium@hdmi-hpd-after-suspend.html https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_3/fi-skl-6700k2/igt@kms_chamelium@hdmi-hpd-after-suspend.html (kms_chamelium:1769) igt_chamelium-CRITICAL: Test assertion failure function chamelium_rpc, file ../lib/igt_chamelium.c:302: (kms_chamelium:1769) igt_chamelium-CRITICAL: Failed assertion: !chamelium->env.fault_occurred (kms_chamelium:1769) igt_chamelium-CRITICAL: Last errno: 113, No route to host (kms_chamelium:1769) igt_chamelium-CRITICAL: Chamelium RPC call failed: libcurl failed to execute the HTTP POST transaction, explaining: Failed to connect to 192.168.1.221 port 9992: No route to host Test kms_chamelium failed. https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_11/fi-kbl-7500u/igt@kms_chamelium@vga-edid-read.html https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_12/fi-skl-6700k2/igt@kms_chamelium@dp-hpd-storm.html (kms_chamelium:3125) igt_chamelium-CRITICAL: Test assertion failure function chamelium_rpc, file ../lib/igt_chamelium.c:302: (kms_chamelium:3125) igt_chamelium-CRITICAL: Failed assertion: !chamelium->env.fault_occurred (kms_chamelium:3125) igt_chamelium-CRITICAL: Last errno: 101, Network is unreachable (kms_chamelium:3125) igt_chamelium-CRITICAL: Chamelium RPC call failed: libcurl failed to execute the HTTP POST transaction, explaining: Couldn't connect to server Test kms_chamelium failed. https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_12/fi-skl-6700k2/igt@kms_chamelium@dp-crc-fast.html (kms_chamelium:2999) igt_chamelium-CRITICAL: Test assertion failure function chamelium_rpc, file ../lib/igt_chamelium.c:302: (kms_chamelium:2999) igt_chamelium-CRITICAL: Failed assertion: !chamelium->env.fault_occurred (kms_chamelium:2999) igt_chamelium-CRITICAL: Last errno: 113, No route to host (kms_chamelium:2999) igt_chamelium-CRITICAL: Chamelium RPC call failed: libcurl failed to execute the HTTP POST transaction, explaining: Failed to connect to 192.168.1.220 port 9992: No route to host Test kms_chamelium failed. https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_14/fi-kbl-7500u/igt@kms_chamelium@dp-crc-single.html (kms_chamelium:2600) igt_chamelium-CRITICAL: Test assertion failure function chamelium_rpc, file ../lib/igt_chamelium.c:302: (kms_chamelium:2600) igt_chamelium-CRITICAL: Failed assertion: !chamelium->env.fault_occurred (kms_chamelium:2600) igt_chamelium-CRITICAL: Chamelium RPC call failed: RPC failed at server. <class 'chameleond.devices.input_flow.InputFlowError'>:DP FSM failed Subtest dp-crc-single failed. |
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.