GUI acceptance tests using environment deployed from packages.

Build: #2193 failed

Job: Onezone harvesters index was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
14 minutes
Revision
466b4a1341ba42e3ce27e138642da6627c86d0c6
Total tests
5
Successful since
#2190 ()

Tests

  • 5 tests in total
  • 13 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: a51ef3f3f203: Container a51ef3f3f20346db8da562d48dbf42295c9bf1c9319f3282b44e9accb60cf5d4 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-COHI/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COHI/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COHI/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COHI/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COHI/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COHI/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-COHI/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-COHI/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-COHI/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
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
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
W0701 01:20:02.380047     451 warnings.go:70] policy/v1beta1 PodDisruptionBudget is deprecated in v1.21+, unavailable in v1.25+; use policy/v1 PodDisruptionBudget
cp: cannot stat 'onedata/one_env/sources_info.yaml': No such file or directory
  % 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  43896      0 --:--:-- --:--:-- --:--:-- 44314
Error response from daemon: Cannot kill container: 1afd1cf71f36: Container 1afd1cf71f367fa74450d522e70483ff89becaebcd242d25af7d317b7125ffbf is not running
Error response from daemon: Cannot kill container: 7bba6b1278d0: Container 7bba6b1278d02b8799da739d0a1aab10f8ef98d9e67e658168271d80d45e08ea is not running
Error response from daemon: Cannot kill container: 9954ad98d63f: Container 9954ad98d63f2fce1368d29e235d68ab58cdb01fb11872d59970272994dfdadf is not running
Error response from daemon: Cannot kill container: 7e0a1f77132e: Container 7e0a1f77132e5eb9cec109335078a7e76983154dd854a9fb4b058239a12de377 is not running
Error response from daemon: Cannot kill container: 3536918992a5: Container 3536918992a5991cb5bc55fc58236b485f6e544ba51f3d8174585bacbbb3de24 is not running
Error response from daemon: Cannot kill container: 416899a98476: Container 416899a984766b2f9ada4c36b641869f555b983b9ebbbfacb42c42f24d9217c5 is not running
Error response from daemon: Cannot kill container: ed83514df457: Container ed83514df457d977e6191b91fc7597790f1416c2904d5fd46839f04949751cc9 is not running
Error response from daemon: Cannot kill container: 60eb227ef029: Container 60eb227ef0299758672ba5cdabaea201635a9423d9159715200a2c24741f75e1 is not running
Error response from daemon: Cannot kill container: 3d8339326a81: Container 3d8339326a816a96133a9a07419764d2423bae5ac0e9ea02eeaff77e14e912b7 is not running
Error response from daemon: Cannot kill container: 25776d5fc99d: Container 25776d5fc99d222b0a5dfef92fbcf0d88a52c614a43af516467a592b6c0ac010 is not running
Error response from daemon: Cannot kill container: 2fe7673f68b1: Container 2fe7673f68b185a3948f6fdce5d0c7df4b72a31d44a71f7183605a732b25832a is not running
Error response from daemon: Cannot kill container: 5316c6ab927a: Container 5316c6ab927a095cb676e08c7308c024d670d987c7a0ffecc1c78d1c6c335062 is not running
Error response from daemon: Cannot kill container: c3066fbd7ce0: Container c3066fbd7ce0495584cf56d08181c09e623da9aa1596bd13f0c32d75717d698c is not running
Error response from daemon: Cannot kill container: 88b33ea611cd: Container 88b33ea611cd54846a2323bf76228ba51866f19a180ad67838104ab3d60031af is not running
Error response from daemon: Cannot kill container: 258c59155ae4: Container 258c59155ae4fdf8e3e9d6c1095ed6d8f2624ce65f4205e9518da9088bdefb53 is not running
Error response from daemon: Cannot kill container: e08e8768dfc8: Container e08e8768dfc84b3e170b2236154017c1456269f891ef558c9a0bfbd060488789 is not running