Hi,

none of my UI-sanity-tests-optimization patches was merged so this is not related to my recent work.

Regards, Marcin

On 3/7/19 8:48 AM, Galit Rosenthal wrote:
Hi, 

we are failing basic suite master (vdsm) 

Can you please have a look at the issue? 

Error Message:
Message: Error forwarding the new session new session request for webdriver should contain a location header or an 'application/json;charset=UTF-8' response body with the session ID.

from the [2]:

08:22:04 + xmllint --format /dev/shm/ost/deployment-basic-suite-master/008_basic_ui_sanity.py.junit.xml
08:22:04 <?xml version="1.0" encoding="UTF-8"?>
08:22:04 <testsuite name="nosetests" tests="7" errors="1" failures="0" skip="0">
08:22:04   <testcase classname="008_basic_ui_sanity" name="init" time="0.001"/>
08:22:04   <testcase classname="008_basic_ui_sanity" name="start_grid" time="144.413">
08:22:04     <system-out><![CDATA[executing shell: docker ps
08:22:04 CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES
08:22:04 
08:22:04 
08:22:04 executing shell: docker rm -f grid_node_chrome grid_node_firefox selenium-hub
08:22:04 
08:22:04 Error response from daemon: No such container: grid_node_chrome
08:22:04 Error response from daemon: No such container: grid_node_firefox
08:22:04 Error response from daemon: No such container: selenium-hub
08:22:04 
08:22:04 executing shell: docker kill grid_node_chrome grid_node_firefox selenium-hub
08:22:04 
08:22:04 Error response from daemon: Cannot kill container grid_node_chrome: No such container: grid_node_chrome
08:22:04 Error response from daemon: Cannot kill container grid_node_firefox: No such container: grid_node_firefox
08:22:04 Error response from daemon: Cannot kill container selenium-hub: No such container: selenium-hub
08:22:04 
08:22:04 executing shell: docker ps
08:22:04 CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES
08:22:04 
08:22:04 
08:22:04 executing shell: docker network ls
08:22:04 NETWORK ID          NAME                DRIVER              SCOPE
08:22:04 f710c07f46da        bridge              bridge              local
08:22:04 7d05935c9513        host                host                local
08:22:04 415e4fd8022f        none                null                local
08:22:04 
08:22:04 
08:22:04 executing shell: docker network rm grid
08:22:04 
08:22:04 Error response from daemon: network grid not found
08:22:04 
08:22:04 executing shell: docker network ls
08:22:04 NETWORK ID          NAME                DRIVER              SCOPE
08:22:04 f710c07f46da        bridge              bridge              local
08:22:04 7d05935c9513        host                host                local
08:22:04 415e4fd8022f        none                null                local
08:22:04 
08:22:04 
08:22:04 executing shell: docker network ls
08:22:04 NETWORK ID          NAME                DRIVER              SCOPE
08:22:04 f710c07f46da        bridge              bridge              local
08:22:04 7d05935c9513        host                host                local
08:22:04 415e4fd8022f        none                null                local
08:22:04 
08:22:04 
08:22:04 creating docker network for grid
08:22:04 executing shell: docker network create grid
08:22:04 7406c15c141eccac968e5fba9f091d83831a29c92fc9f61b95bc4fba47f5e73f
08:22:04 

Global link to the CQ fail[3]


--

GALIT ROSENTHAL

SOFTWARE ENGINEER

Red Hat 

galit@gmail.com    T: 972-9-7692230