6:03 p.m.
On Sat, Nov 24, 2018 at 9:49 AM Dan Kenigsberg <danken(a)redhat.com> wrote:
On Sat, 24 Nov 2018, 13:50 Greg Sheremeta <gshereme(a)redhat.com wrote:
> Correct, that vdsm patch is unrelated.
>
> The docker-based selenium testing infrastructure did not initialize
> correctly. Firefox started but chrome did not download correctly.
> [
>
https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/11365/test...
> ]
>
> Unable to find image 'selenium/node-chrome-debug:3.9.1-actinium' locally
> Trying to pull repository docker.io/selenium/node-chrome-debug ...
> 3.9.1-actinium: Pulling from docker.io/selenium/node-chrome-debug
> 1be7f2b886e8 <http://docker.io/selenium/node-chrome-debug1be7f2b886e8>;: Already
exists
> 6fbc4a21b806: Already exists
> c71a6f8e1378: Already exists
> 4be3072e5a37: Already exists
> 06c6d2f59700: Already exists
> edcd5e9f2f91: Already exists
> 0eeaf787f757: Already exists
> c949dee5af7e: Already exists
> df88a49b4162: Already exists
> ce3c6f42fd24: Already exists
> 6d845a39af3f: Pulling fs layer
> 11d16a965e13: Pulling fs layer
> 1294e9b42691: Pulling fs layer
> 04b0c053828d: Pulling fs layer
> cf044f1d0e2a: Pulling fs layer
> 8f84ccb3a86a: Pulling fs layer
> be9a1d0955bd: Pulling fs layer
> 872e5c8a3ad8: Pulling fs layer
> 07efee6f27e7: Pulling fs layer
> 5c6207de8f09: Pulling fs layer
> b932cacc6ddb: Pulling fs layer
> c057ca8f4e65: Pulling fs layer
> bbe16010d6ab: Pulling fs layer
> 645ca3607a4c: Pulling fs layer
> cf044f1d0e2a: Waiting
> 04b0c053828d: Waiting
> 8f84ccb3a86a: Waiting
> be9a1d0955bd: Waiting
> c057ca8f4e65: Waiting
> 5c6207de8f09: Waiting
> b932cacc6ddb: Waiting
> bbe16010d6ab: Waiting
> 645ca3607a4c: Waiting
> 07efee6f27e7: Waiting
> 872e5c8a3ad8: Waiting*/usr/bin/docker-current: error pulling image configuration:
unknown blob.
> *See '/usr/bin/docker-current run --help'.
>
>
> checking chrome node
> executing shell: *curl http://:5555/wd/hub/static/resource/hub.html
> <--- that URL won't work :)*
>
> % Total % Received % Xferd Average Speed Time Time Time
> Current
> Dload Upload Total Spent Left
> Speed
>
> 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:--
> 0
> curl: (6) Could not resolve host: ; Unknown error
>
> checking firefox node
> executing shell: curl
> http://172.18.0.3:5555/wd/hub/static/resource/hub.html
> <!DOCTYPE html>
> <title>WebDriver Hub</title>
>
>
> This is the first time I've seen something like this with this test. Did
> it happen only the one time?
>
I have no idea. I didn't not even know that such a test had existed.
Yep, we make sure the UI loads, user can login and navigate, etc. -- all
automated.
ovirt CI tries to cache yum repos it pulls from. Do you know if it does so
with docker repos?
I don't know. The selenium ones are standard from dockerhub [
https://hub.docker.com/u/selenium/]
>
> On Sat, Nov 24, 2018 at 2:35 AM Dan Kenigsberg <danken(a)redhat.com> wrote:
>
>> I just noticed that a vdsm change to gluster tests
>> https://gerrit.ovirt.org/#/c/95596/ failed in the change queue, on
>>
>> WebDriverException in _init_browser connecting to hub
>>
>>
>>
https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/11365/test...
>>
>> The failure is clearly unrelated to the patch; maybe one of you can
>> explain why the test fails?
>>
>
>
> --
>
> GREG SHEREMETA
>
> SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX
>
> Red Hat NA
>
> <https://www.redhat.com/>
>
> gshereme(a)redhat.com IRC: gshereme
> <https://red.ht/sig>
>
--
GREG SHEREMETA
SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX
Red Hat NA
<https://www.redhat.com/>
gshereme(a)redhat.com IRC: gshereme
<https://red.ht/sig>