GUI acceptance tests using environment deployed from packages.

Build: #2129 failed

Job: Chrome metadata test was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
20 minutes
Revision
39fb434fa4268b56f32dccaa52527f3591cd9ea8
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
  • 19 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  41176      0 --:--:-- --:--:-- --:--:-- 41176
Error response from daemon: Cannot kill container: 0adac45fe855: Container 0adac45fe85580282ff43100027022c23794ba6396941c6ac1a4cc656d3b632f 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]
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]
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
W0504 10:55:50.882819     437 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  20407      0 --:--:-- --:--:-- --:--:-- 20407
Error from server (NotFound): pods "dev-oneprovider-krakow-0" not found
Error response from daemon: Cannot kill container: 19084fc1c968: Container 19084fc1c9685ba8809663c46c4018aff1ea1811292b6e3602e1cf24cfa69c08 is not running
Error response from daemon: Cannot kill container: 421f7fc131a5: Container 421f7fc131a5edb179cb0a4fd7ce014d2b62168e5150653ccc500676d85ea0a6 is not running
Error response from daemon: Cannot kill container: c619a3b9d8e1: Container c619a3b9d8e1c3340683ad3ca0fa1138d8bd5912568d7bd08939f04669b433e1 is not running
Error response from daemon: Cannot kill container: ac0c4d950b82: Container ac0c4d950b8265b690affb07b26f5dffef81302aa82212c52f9def294bc6fdab is not running
Error response from daemon: Cannot kill container: 345fa27c07df: Container 345fa27c07dfb43513b66dc77a566ca44ec43d721f76dcdd436271f490fba350 is not running
Error response from daemon: Cannot kill container: 60a94cc42bfc: Container 60a94cc42bfc4cfab5232c4eba056823a371435dbe26c180d19cca4ce4d2d6b3 is not running
Error response from daemon: Cannot kill container: f6fdac3630b4: Container f6fdac3630b4095f0e9cd767950143cde25ffaf70a3ad730670d52160ae9034a is not running
Error response from daemon: Cannot kill container: c9504ea906fb: Container c9504ea906fbab59c1e3514284ef2949f33428f62328b6ebe4897fdc351bbc0c is not running
Error response from daemon: Cannot kill container: e039bd30dd55: Container e039bd30dd554ee53aecbdd0ffdf62fbc2f2a77b6ef6c28d4c13b5a39fc686f2 is not running
Error response from daemon: Cannot kill container: 7b908a28cf3a: Container 7b908a28cf3a5ee826c1631c101ab56e6dbb6883b650ddfcad72bf565c1774cd is not running
Error response from daemon: Cannot kill container: f674f6bcdf83: Container f674f6bcdf83afdb1b77d86455634ca1feebf6765f52753d2e421323fd92e85d is not running
Error response from daemon: Cannot kill container: 371ae3356b79: Container 371ae3356b79efe3ec3cd23c32cdeef086eaa23bfa386f51cf504d947f05c14b is not running
Error response from daemon: Cannot kill container: 548a5e8686ee: Container 548a5e8686ee45556bbf7fcde67d13a09f4e3b8780c00a5dd9945e97f3daa39c is not running
Error response from daemon: Cannot kill container: c0b0b8e78bd7: Container c0b0b8e78bd70a209ee72ad1862daf61ab22349d677083f05899bd47c2d1b180 is not running
Error response from daemon: Cannot kill container: f92edf28c0d4: Container f92edf28c0d4462a4673203f5756f11bbefeb9cee843274d27f07a2cb395db71 is not running
Error response from daemon: Cannot kill container: 02f061c73cfc: Container 02f061c73cfc092618aa3a150a74cee0f5e3f9b2fb74a7ad49a8931d8f25bc13 is not running