GUI acceptance tests using environment deployed from packages.

Build: #2178 failed

Job: Chrome onezone automations tests was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
53 minutes
Revision
8046c81cb26d07683c2acee37fe8f6bde9d9a654
Total tests
37
Successful since
#1998 ()

Configuration changes

Job Chrome onezone automations tests with key ODSRV-GAPT-COZATT no longer exists.

Tests

  • 37 tests in total
  • 52 minutes taken in total.

Error summary

The build generated some errors. See the full build log for more details.

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  4653  100  4653    0     0  47479      0 --:--:-- --:--:-- --:--:-- 47479
Error response from daemon: Cannot kill container: 5e05925d4f8a: Container 5e05925d4f8a1fa4ba7e3c2298e9c5f16b983e1626561771a97cfe135e9f4e27 is not running
Submodule 'bamboos' (ssh://git@git.onedata.org:7999/vfs/bamboos.git) registered for path 'bamboos'
Submodule 'cdmi_swagger' (ssh://git@git.onedata.org:7999/vfs/cdmi-swagger.git) registered for path 'cdmi_swagger'
Submodule 'one_env' (ssh://git@git.onedata.org:7999/vfs/one-env.git) registered for path 'one_env'
Submodule 'onepanel_swagger' (ssh://git@git.onedata.org:7999/vfs/onepanel-swagger.git) registered for path 'onepanel_swagger'
Submodule 'oneprovider_swagger' (ssh://git@git.onedata.org:7999/vfs/oneprovider-swagger.git) registered for path 'oneprovider_swagger'
Submodule 'onezone_swagger' (ssh://git@git.onedata.org:7999/vfs/onezone-swagger.git) registered for path 'onezone_swagger'
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COZATT/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COZATT/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COZATT/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COZATT/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COZATT/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COZATT/onedata/onezone_swagger'...
Submodule 'bamboos' (ssh://git@git.onedata.org:7999/vfs/bamboos.git) registered for path 'onepanel_swagger/bamboos'
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COZATT/onedata/onepanel_swagger/bamboos'...
Submodule 'bamboos' (ssh://git@git.onedata.org:7999/vfs/bamboos.git) registered for path 'oneprovider_swagger/bamboos'
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COZATT/onedata/oneprovider_swagger/bamboos'...
Submodule 'bamboos' (ssh://git@git.onedata.org:7999/vfs/bamboos.git) registered for path 'onezone_swagger/bamboos'
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COZATT/onedata/onezone_swagger/bamboos'...
error: failed to create clusterrolebinding: clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
Error: could not find tiller
error: failed to create clusterrolebinding: clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
Defaulted container "oneprovider" out of: oneprovider, onezone-registration-token (init)
protocol version mismatch -- is your shell clean?
(see the rsync man page for an explanation)
rsync error: protocol incompatibility (code 2) at compat.c(178) [Receiver=3.1.2]
command terminated with exit code 126
Defaulted container "oneprovider" out of: oneprovider, onezone-registration-token (init)
protocol version mismatch -- is your shell clean?
(see the rsync man page for an explanation)
rsync error: protocol incompatibility (code 2) at compat.c(178) [Receiver=3.1.2]
command terminated with exit code 126
Defaulted container "oneprovider" out of: oneprovider, onezone-registration-token (init)
protocol version mismatch -- is your shell clean?
(see the rsync man page for an explanation)
rsync error: protocol incompatibility (code 2) at compat.c(178) [Receiver=3.1.2]
command terminated with exit code 126
protocol version mismatch -- is your shell clean?
(see the rsync man page for an explanation)
rsync error: protocol incompatibility (code 2) at compat.c(178) [Receiver=3.1.2]
command terminated with exit code 126
protocol version mismatch -- is your shell clean?
(see the rsync man page for an explanation)
rsync error: protocol incompatibility (code 2) at compat.c(178) [Receiver=3.1.2]
command terminated with exit code 126
protocol version mismatch -- is your shell clean?
(see the rsync man page for an explanation)
rsync error: protocol incompatibility (code 2) at compat.c(178) [Receiver=3.1.2]
command terminated with exit code 126
W0620 11:34:50.393922     430 warnings.go:70] policy/v1beta1 PodDisruptionBudget is deprecated in v1.21+, unavailable in v1.25+; use policy/v1 PodDisruptionBudget
cp: cannot stat 'onedata/one_env/sources_info.yaml': No such file or directory
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  4653  100  4653    0     0  36637      0 --:--:-- --:--:-- --:--:-- 36637
Error response from daemon: Cannot kill container: 1229d71fae63: Container 1229d71fae632680485fcc4cd41e751ce137967b9ede6209d059157d3879248d is not running
Error response from daemon: Cannot kill container: 3b935fc4e2b9: Container 3b935fc4e2b9315fb54c7b808b081bba63437648846216c36843f810786608fb is not running
Error response from daemon: Cannot kill container: 3bf400daa144: Container 3bf400daa1440f8e8b1ae7f718fcd075582bdbd1cf1b23facf4d490a35831049 is not running
Error response from daemon: Cannot kill container: bd7634083fb6: Container bd7634083fb6621e408fa640bd202d51665f8bcce58ae9549bbf7e56cb648a9b is not running
Error response from daemon: Cannot kill container: 3687f1335a74: Container 3687f1335a746f25a0314dda71682f8ceafcd55053d5360b998d2f3b53e48020 is not running
Error response from daemon: Cannot kill container: 4dd1d5eb7f27: Container 4dd1d5eb7f274f74c7c4c5aeaf49d6ee3ac3dc5a8dd30095db10ec594f4154bc is not running
Error response from daemon: Cannot kill container: 0cbd8c47b384: Container 0cbd8c47b384919f0684c4c8baa909ac2ecce22283fcdafb4f014ee7d733f005 is not running
Error response from daemon: Cannot kill container: 35378b907e06: Container 35378b907e06a931c7abbde78648b38ae5f176fc0f21f40a373c314487bb60b6 is not running
Error response from daemon: Cannot kill container: 1d8819a8bbae: Container 1d8819a8bbae1c52732e73ea591d9644e0d50176658c997dac0080a67875b022 is not running
Error response from daemon: Cannot kill container: b3f26d823d31: Container b3f26d823d31278c4b1f5f5e21d114c37fa0c4fb2b7cdcf6fa24facc5e1183e1 is not running
Error response from daemon: Cannot kill container: 8ce368f65c6c: Container 8ce368f65c6c3a3e930f136c2bfc7a03fe67827f7715040a2937ac3ce6ff7907 is not running
Error response from daemon: Cannot kill container: ada9e5723022: Container ada9e5723022a239a752fdc02782cfd4f6982f414cf4239ef87a522a7d26960f is not running
Error response from daemon: Cannot kill container: 0b64fcaf31e0: Container 0b64fcaf31e07bb71c1c4f2982f34f3255a6f9c301582379512dae1b62ad27bf is not running
Error response from daemon: Cannot kill container: 5ce33ca747d9: Container 5ce33ca747d9cef570aa87922719c22b982d8769231ec0bc8f6d540b5122585e is not running
Error response from daemon: Cannot kill container: 616722b16e57: Container 616722b16e57e9c0f433b8c286d13397526dcbfa25534e46768a46a5ad5ffe05 is not running
Error response from daemon: Cannot kill container: f8a13470fdb1: Container f8a13470fdb1d3702e7da6fa7b0bf7eb700eef17bf20c97ebe6bc8d1422bad0a is not running