GUI acceptance tests using environment deployed from packages.

Build: #2142 failed

Job: Chrome metadata test was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
19 minutes
Revision
3f6eba726c9f477b80c64f61e18d18c4a18e4f06
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  50576      0 --:--:-- --:--:-- --:--:-- 50576
Error response from daemon: Cannot kill container: e95c61bea364: Container e95c61bea3648995cf58eb8fe33971b0094fc22fdf32ec15afbde046d987ef58 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
W0518 10:50:22.180010     445 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  30814      0 --:--:-- --:--:-- --:--:-- 30814
Error response from daemon: Cannot kill container: b303012e5cc7: Container b303012e5cc7d51042316fbe053692b5f10c36b1594f8e79b08d969be3cb2573 is not running
Error response from daemon: Cannot kill container: 92fda4819a71: Container 92fda4819a71ff400aeaa4551184644879f41b6d89edcedb5b765e71d932553a is not running
Error response from daemon: Cannot kill container: c16e65aaf3f7: Container c16e65aaf3f7b7ce6c91efe8be0a33feb48763537ec88ebc7be50a04b86f225e is not running
Error response from daemon: Cannot kill container: c225e96eef18: Container c225e96eef184cc7452d67c74ebea1e15d8e57dd0ea4fa3388738bd15ebbb080 is not running
Error response from daemon: Cannot kill container: c0d67d9044d4: Container c0d67d9044d44dd8456621581c1e52d7df193d35ad12bcca6a282db8a9eabf76 is not running
Error response from daemon: Cannot kill container: 03509f74a58a: Container 03509f74a58a3e9c15dfb1b2dbbcf86741f97db9bb1530d74f5c59bce291ccb8 is not running
Error response from daemon: Cannot kill container: 25ed670f7685: Container 25ed670f768539ac48eb46391faafe9322bf2244b243c859bfa6fbf70d64628a is not running
Error response from daemon: Cannot kill container: be91c24ce914: Container be91c24ce914aa72d82de0d288e7a60b184e5891189e1455a0b307cd1ca7e09b is not running
Error response from daemon: Cannot kill container: 6d2615c8474a: Container 6d2615c8474a3b0a874b19747a1ffa926be3d00325a2d3abe34d558ffde3087c is not running
Error response from daemon: Cannot kill container: 87741200785f: Container 87741200785fcdae363d91e5cd52785b5ca9190dbf1cbdc8d45fe9368037d3c0 is not running
Error response from daemon: Cannot kill container: c700c2af83e9: Container c700c2af83e98e94cf6b86a0ebade06bd7b10cbba7306dc7f8a6613a7d8b9b45 is not running
Error response from daemon: Cannot kill container: df9244592ea8: Container df9244592ea87105c80a4d570aa1dcbe31c498fdd342473bf3e7307de186509d is not running
Error response from daemon: Cannot kill container: 3193f48ed026: Container 3193f48ed026117a61ec02bcbd30a9b1b691e406148533b0a6972f384b0b13e2 is not running
Error response from daemon: Cannot kill container: 9fd6a8ddfb64: Container 9fd6a8ddfb648e4c037c226e161c075c8d807594b37c677c221d04f5a91788c1 is not running
Error response from daemon: Cannot kill container: 949f5afd0467: Container 949f5afd04674fcbf3629cdaae9f7cce690afb7bb7b11a17eeeedc22c8dadcfa is not running
Error response from daemon: Cannot kill container: 0dc26270dc70: Container 0dc26270dc702c0894dd4cdf416827179a7c88dba2e0d54345c46dd1cfa1bac3 is not running