GUI acceptance tests using environment deployed from packages.

Build: #2058 failed

Job: Chrome metadata test was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
19 minutes
Revision
f9849bc17b2b7fe665e2a7df5ed9e5dea86d8360
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
  • 18 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  41918      0 --:--:-- --:--:-- --:--:-- 41918
Error response from daemon: Cannot kill container: a4b2f6d210be: Container a4b2f6d210beff40795365ea74b7100534b3c433661ce6d0959d1b4d94e977b4 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]
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
W0325 22:39:01.371322     435 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  46069      0 --:--:-- --:--:-- --:--:-- 46530
Error response from daemon: Cannot kill container: bc1f762c4e02: Container bc1f762c4e0280682012f6db5a3d4dcbe8dcb91bb64ec11b51c244e26215b719 is not running
Error response from daemon: Cannot kill container: 2af31b4ea938: Container 2af31b4ea93822a1dd643b356f40dc45dd14458b277ad4de72bfefc0945de8b8 is not running
Error response from daemon: Cannot kill container: 12ba0a359357: Container 12ba0a3593570575774a2a7c1a0d8230f2283f2804636048c5d9f1598f68cd40 is not running
Error response from daemon: Cannot kill container: 735a3806117b: Container 735a3806117bbb540a465fd88debcdd5a76f2324ffc4711daeb0a2ad1e50800f is not running
Error response from daemon: Cannot kill container: 67069b79645a: Container 67069b79645a881cae895fd364324b2505c82339ceec864d78bf262b16eb0991 is not running
Error response from daemon: Cannot kill container: 9648ff819379: Container 9648ff8193795f9fd936caebc2fe7c6e8dafb53fc5cbc389600a417e54439153 is not running
Error response from daemon: Cannot kill container: daa5f2b638ac: Container daa5f2b638acf0840c727a592fc5f73d46271d434d43481c4dc705480c380f9a is not running
Error response from daemon: Cannot kill container: 782e65e46ccf: Container 782e65e46ccf044fc1f716bb33da1b4ad787d860865e59bf82ff8f3da48dd8c8 is not running
Error response from daemon: Cannot kill container: 0927a01174ed: Container 0927a01174ed0b453fd351ed055f1718d487c0c2cd23fb1f606050d74fdc272f is not running
Error response from daemon: Cannot kill container: 97a5dc70ecf9: Container 97a5dc70ecf967796fc1a77bf03e30016b6a480e85d87b209c27159b607a4bd5 is not running
Error response from daemon: Cannot kill container: e595137ecb7d: Container e595137ecb7d51a44657fb42d33b698589657bc5536d42bc7ca9820c22d21676 is not running
Error response from daemon: Cannot kill container: 1877895c1a88: Container 1877895c1a8830ba52df44cd85a9ebe48c6ae0c1a20038ad6b5d1780db053712 is not running
Error response from daemon: Cannot kill container: 9674b37215ce: Container 9674b37215ce0e5b730b8e3c100cd4ddaacb29d4077e58e612b626764d781734 is not running
Error response from daemon: Cannot kill container: 87ad31525c20: Container 87ad31525c2026fc78cd612fea7a19a4314e13467942bbe8426fe8924e4d321c is not running
Error response from daemon: Cannot kill container: d8f41f310e64: Container d8f41f310e642aab9fe9ef56847f32763963d6b9cd2420ddbb45e771ad9f8ec2 is not running
Error response from daemon: Cannot kill container: 8d0de785a62d: Container 8d0de785a62dad2dfd16bd090cd625487300dbae0809f80f5a7c74fbd55d6c04 is not running