GUI acceptance tests using environment deployed from packages.

Build: #2103 was successful

Job: Chrome metadata test was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
17 minutes
Revision
90fc7afe3680c7ff2b4e3e422371d0941ed8ee84
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
  • 17 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  48978      0 --:--:-- --:--:-- --:--:-- 49500
Error response from daemon: Cannot kill container: ea885f7ccdd5: Container ea885f7ccdd5b1fda4a11c38815d348a35746742687b79cba6ceacf1d2e7974f 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
W0414 13:51:50.676053     436 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 --:--:-- --:--:-- --:--:-- 46069
Error response from daemon: Cannot kill container: 800976af4aac: Container 800976af4aac4971dd485dd78f3576ddafbdd198d65519a6eb435c4d7c1ddf9e is not running
Error response from daemon: Cannot kill container: b131ad96a181: Container b131ad96a1818394442040ef1da7fb46768a466761191300d230e60d39ad606d is not running
Error response from daemon: Cannot kill container: 5658f9dd9dc2: Container 5658f9dd9dc2df2294ba7c2ea12d1ce784e8d79cda5f475813d681cf815882c8 is not running
Error response from daemon: Cannot kill container: 90826cf0bf7c: Container 90826cf0bf7c9a678cddaea095a5656a1c52bcb7077e44f8cbb058188f996d4b is not running
Error response from daemon: Cannot kill container: fc4a954e1b42: Container fc4a954e1b42d2133bc9a03efb9ad41319b993fbd78b4d097a896260038eea85 is not running
Error response from daemon: Cannot kill container: e1680b9f4c7b: Container e1680b9f4c7b2c4ed9db904a3d98700a2454c02609838d8be150bd75ffce4718 is not running
Error response from daemon: Cannot kill container: 439f98a5cc76: Container 439f98a5cc768a154984b967938348dfdf2785209a5a2b4f5a3e92b1c546b978 is not running
Error response from daemon: Cannot kill container: 295a47309d15: Container 295a47309d15ba21a91382d1c24921ecc24d333cd60f572c65bfc29ec2958757 is not running
Error response from daemon: Cannot kill container: 4e7b89b72431: Container 4e7b89b72431c679f68cc0a6dbd6da39090148647909f7db00a3b123afde801f is not running
Error response from daemon: Cannot kill container: b24e3248b77b: Container b24e3248b77bc379338fee6022af0c9281f4b4b58264e61b9e1638016a3b7e66 is not running
Error response from daemon: Cannot kill container: 3bba7a7e01e6: Container 3bba7a7e01e6570f6b0ec3bc698166463a91d4a7bafb5f04668f1da837852608 is not running
Error response from daemon: Cannot kill container: be433eee571e: Container be433eee571ee389111a88da7009e88cc8eb495a5d3a906bef38d3c96cde1724 is not running
Error response from daemon: Cannot kill container: 94f690e8b45f: Container 94f690e8b45fc5c60c56b022ac6da3760f003bb42b516b36f43d2a633ac22d73 is not running
Error response from daemon: Cannot kill container: 5473f71a9cf2: Container 5473f71a9cf2a5e82aa65561e909b80d7376df609421618121ab5652798749b3 is not running
Error response from daemon: Cannot kill container: ecf568a39773: Container ecf568a3977350ff8243b97f2e5064eb8db0d3d1c30e4493ed8897d77143f28c is not running
Error response from daemon: Cannot kill container: fe6ecdbd54d3: Container fe6ecdbd54d3daeb9e6f4c53e29fc56255f1d002e92104ab3b151032bea0a267 is not running