GUI acceptance tests using environment deployed from packages.

Build: #2140 failed

Job: Chrome metadata test was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
30 minutes
Revision
dfd405a02fa2a4bab1ba6431bc2638a43a9cd1cb
Total tests
24
Successful since
#1943 ()

Configuration changes

Job Chrome metadata test with key ODSRV-GAPT-MTC no longer exists.

Tests

  • 24 tests in total
  • 29 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  39769      0 --:--:-- --:--:-- --:--:-- 39769
Error response from daemon: Cannot kill container: 5d60ce425135: Container 5d60ce425135f5f171aaa5b78346fd0ddb46c08e03a0b81d88cd8399a0d6b9fd 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-MTC/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-MTC/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-MTC/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-MTC/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-MTC/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-MTC/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-MTC/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-MTC/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-MTC/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]
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
W0516 20:10:15.733664     439 warnings.go:70] policy/v1beta1 PodDisruptionBudget is deprecated in v1.21+, unavailable in v1.25+; use policy/v1 PodDisruptionBudget
  % 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  31020      0 --:--:-- --:--:-- --:--:-- 31020
Error response from daemon: Cannot kill container: 110caa503f9c: Container 110caa503f9cb41e7751759dbb17f9fde95e3ee9bbf48a1a53a4aaa4b6fec40e is not running
Error response from daemon: Cannot kill container: 5074e801cdfe: Container 5074e801cdfeefad7c9e7aa86ba30ce88030b9c1754db85e9a54967c2bf1c025 is not running
Error response from daemon: Cannot kill container: 19c6583fa353: Container 19c6583fa35310cbc2bc1e27588b0c5e5095110bd2d2fe76e09930be4f5b7b31 is not running
Error response from daemon: Cannot kill container: bb070b624a04: Container bb070b624a04e08369a35628a2e3ba6a01f57be4a7ce67ba3d998d67f460e867 is not running
Error response from daemon: Cannot kill container: 89374c2f7fe8: Container 89374c2f7fe802dca7729b03e34ac8f9e9fb6f8790d68064a5b3f56b4331441d is not running
Error response from daemon: Cannot kill container: d1dfd9d29f45: Container d1dfd9d29f45f8869698b6691138f0fa0436d47e7dde8fce9eda3426da2130b6 is not running
Error response from daemon: Cannot kill container: 50cae2ecbf8f: Container 50cae2ecbf8fd1ff10b8050513092d6509bbbe0bbe412a084e191e9a3961757e is not running
Error response from daemon: Cannot kill container: 9df3bcd3607d: Container 9df3bcd3607d2d850cf6b6a2bf09b7335439beba96acdf78dbe15b00ad0d26a8 is not running
Error response from daemon: Cannot kill container: 2f23af4b384d: Container 2f23af4b384d17a1b45b3c37defddf512b3a0199348b205a47fc94263c0867ad is not running
Error response from daemon: Cannot kill container: 1a5e3629ce8b: Container 1a5e3629ce8bf5427d26f0985fcdf36e80de7bef2914661265a4faf274967932 is not running
Error response from daemon: Cannot kill container: aada561e89ae: Container aada561e89ae844b60c687cd4f5a9555ab456792554d56351e67c7d3c15e5ad1 is not running
Error response from daemon: Cannot kill container: 56c97c1e8a01: Container 56c97c1e8a01e54f5dd894f54bd01c2f8dc3603f06c323b26e62c9e40d26fa1c is not running
Error response from daemon: Cannot kill container: d00981a0aa0e: Container d00981a0aa0ee89b0926da794bce0151c9f3807263bf3237bdb868989f018bda is not running
Error response from daemon: Cannot kill container: 40d85d86bf1a: Container 40d85d86bf1aec29f2e06dc5d185b419e0ba579c78c02c5f1ba3f4c7f113f1bc is not running
Error response from daemon: Cannot kill container: b1a0445109b6: Container b1a0445109b6eae3505bbec04c41f92b099f608d38acad7c1a81149d9512e59d is not running
Error response from daemon: Cannot kill container: b3bf6e64d442: Container b3bf6e64d442f256edab807907451b4efadb1493f9d7c9a4d4446846da9da079 is not running