GUI acceptance tests using environment deployed from packages.

Build: #2140 failed

Job: Oneprovider datasets was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
34 minutes
Revision
dfd405a02fa2a4bab1ba6431bc2638a43a9cd1cb
Total tests
18
Successful since
#2082 ()

Tests

  • 18 tests in total
  • 33 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  45617      0 --:--:-- --:--:-- --:--:-- 45617
Error response from daemon: Cannot kill container: b568984423c1: Container b568984423c100154d4e3dba24fb57758ac8b1f84f31a1cdca4841ac5ec2b392 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-CODT/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODT/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODT/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODT/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODT/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODT/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-CODT/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-CODT/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-CODT/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
W0516 20:44:43.446567     439 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  41176      0 --:--:-- --:--:-- --:--:-- 41176
Error response from daemon: Cannot kill container: 48f64773d1e1: Container 48f64773d1e17cd4640be1960445149d3217841ce556c402dc32355b4acbfbd2 is not running
Error response from daemon: Cannot kill container: dee0d46299bc: Container dee0d46299bc581f60752e05eaa32180b3e69a1f2dec479a7ff9ab8eae342e06 is not running
Error response from daemon: Cannot kill container: d6ecd9d8a58f: Container d6ecd9d8a58fd7242d2d26f8c696a86cfe948cb9d08abbaf32c7f6c7ae198d73 is not running
Error response from daemon: Cannot kill container: eac0d9c040ac: Container eac0d9c040ac302a454eadf3841b4355d5ac28d2a4427e880720d5f3220840d5 is not running
Error response from daemon: Cannot kill container: 44321c5fb6a7: Container 44321c5fb6a7216eb60147959a1ed618a44a2c0d6e0bdd4961955bd1bf640f49 is not running
Error response from daemon: Cannot kill container: 31ae9f20867d: Container 31ae9f20867d01eacab0b0ab5e6a61954aebd0a0ab4f8d566e5fdbbc76105014 is not running
Error response from daemon: Cannot kill container: 3cf94a022d1b: Container 3cf94a022d1b91541b5583c802f6ff32ac2d4733c50c84a825ba64a74b63ea78 is not running
Error response from daemon: Cannot kill container: 90ef3dd75881: Container 90ef3dd7588142b366cff59be129db52b663b8409f21715d6288e2bd4dd72ccb is not running
Error response from daemon: Cannot kill container: 910e72bf5ef0: Container 910e72bf5ef00044f4e59d662dca390a181f8fd23b958605cce7013d87ca3f0f is not running
Error response from daemon: Cannot kill container: e12359e48c7f: Container e12359e48c7f824fe1ea5f839f90390be54cb25fbbfed2e149d062edd4fd6a35 is not running
Error response from daemon: Cannot kill container: ad9a897302f0: Container ad9a897302f0b45cfbb443fcfdb2004d742d8d02bd4aa9b36469a56541746dce is not running
Error response from daemon: Cannot kill container: a218f721c528: Container a218f721c528f3665e790a3605e29d5cb15647def2fbe2cf16b104347cd8e342 is not running
Error response from daemon: Cannot kill container: fd1bee16b9d9: Container fd1bee16b9d976afd7c3ded8d5d367792dbfe07400f3844631f557f21efdf333 is not running
Error response from daemon: removal of container fd1bee16b9d9 is already in progress
Error response from daemon: Cannot kill container: 09a4d5052c04: No such container: 09a4d5052c04
Error: No such container: 09a4d5052c04
Error response from daemon: Cannot kill container: 52bd3881eed3: No such container: 52bd3881eed3
Error: No such container: 52bd3881eed3
Error response from daemon: Cannot kill container: 7cbbf0bb8fcb: No such container: 7cbbf0bb8fcb
Error: No such container: 7cbbf0bb8fcb