GUI acceptance tests using environment deployed from packages.

Build: #2134 failed

Job: Chrome metadata test was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
19 minutes
Revision
72d4158537fcbe5e765cfeaf323ebd441ede24a2
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  49500      0 --:--:-- --:--:-- --:--:-- 49500
Error response from daemon: Cannot kill container: 9a83f045c34e: Container 9a83f045c34e447fbd6d5d53fa4363b93c9c9266f97e581873ea8edf336f900f 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
W0506 11:57:33.385916     438 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  47969      0 --:--:-- --:--:-- --:--:-- 48468
Error from server (NotFound): pods "dev-oneprovider-krakow-0" not found
Error response from daemon: Cannot kill container: b024cbda7df4: Container b024cbda7df45cf5ad6872b7d943794b9c8650179f0fbe94d7e5acbc236c102b is not running
Error response from daemon: Cannot kill container: 02b5a2cf4b11: Container 02b5a2cf4b1114afe1073598c1f794d919d0201beb79d8bf9988588fe310978d is not running
Error response from daemon: Cannot kill container: 3e4b9f36c43d: Container 3e4b9f36c43dc7ac7806fa074e34d80e19c2b9addb9865f2091c07d5dfb24391 is not running
Error response from daemon: Cannot kill container: bd3e628051a9: Container bd3e628051a91f982a1be002900d11442fd9395747c42a8994658532d4454800 is not running
Error response from daemon: Cannot kill container: 2532eb885753: Container 2532eb88575398b05b56abe82c8b965e8d7a56b61bc4727b31751187327cfbdb is not running
Error response from daemon: Cannot kill container: 21ff6d2b64eb: Container 21ff6d2b64eb7c89c0aed966ceb78234f77c13fa9ba6866be4b5969ffdb962bc is not running
Error response from daemon: Cannot kill container: 3e817a682b45: Container 3e817a682b45cc350de1a6120f5bf74ad12b3229b8790243585502814d9cf4a7 is not running
Error response from daemon: Cannot kill container: 61d638f4e2d7: Container 61d638f4e2d7e28d812fe58da7f0f4a24f39704c0c428f5bfe4aa2176c25d6f0 is not running
Error response from daemon: Cannot kill container: 58cd42d9cce0: Container 58cd42d9cce0cd329c28879acb8cc437d59d428adb4dd5b9d4af101e2ff3f51c is not running
Error response from daemon: Cannot kill container: c63facabcb8e: Container c63facabcb8e72ee72562fda5f3f267c287aec3f6f444e9e0bd5133f8aab1b74 is not running
Error response from daemon: Cannot kill container: d42dc92c7cb8: Container d42dc92c7cb861072189716aa1b512994da3b546a20fbd048b6fa0b9172e171b is not running
Error response from daemon: Cannot kill container: 0febb131e181: Container 0febb131e1816c39e1bf885b55c1a89284f50598de8ab04e3ee75d07b3fd5b8e is not running
Error response from daemon: Cannot kill container: e023a669300c: Container e023a669300c35b3059415b522950d28cc3b8efc56f4526c87776b16d17f0588 is not running
Error response from daemon: Cannot kill container: e631ddf13865: Container e631ddf1386505591a8d720fb9d04acc1d26c340bceb0292065a07322c698fa5 is not running
Error response from daemon: Cannot kill container: daf08e5352ca: Container daf08e5352ca64e3e48d33e9293911e278947b65800dc9217cd304eefcdc4429 is not running
Error response from daemon: Cannot kill container: e63ce4c69d18: Container e63ce4c69d18e5e9efa41ac9d19ff2ff7552e646ee5dd19585a80d86c1b581db is not running