GUI acceptance tests using environment deployed from packages.

Build: #2163 was successful

Job: POSIX multiuser was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
20 minutes
Revision
2a6ac951983b0da397726653daa1ebcdbbe74ca8
Total tests
8
Successful since
#1943 ()

Tests

  • 8 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  42300      0 --:--:-- --:--:-- --:--:-- 42688
Error response from daemon: Cannot kill container: e26b90eae8c4: Container e26b90eae8c4c2e9fb6acaeff13900b7daa8f10288f41d59888d9a152887644d 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-CPTM/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CPTM/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CPTM/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CPTM/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CPTM/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CPTM/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-CPTM/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-CPTM/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-CPTM/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
W0603 19:59:11.470818     433 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  40112      0 --:--:-- --:--:-- --:--:-- 40112
Error from server (NotFound): pods "dev-oneprovider-krakow-0" not found
Error response from daemon: Cannot kill container: 47681636e95e: Container 47681636e95e6e868585601f0acde1b141549f5642a25a307bbcf9ff16eacb0e is not running
Error response from daemon: Cannot kill container: ac022c65cbbf: Container ac022c65cbbf1f0aa4c5c6c65664d4470a26810dc8ca8bd82e94aacbeea16255 is not running
Error response from daemon: Cannot kill container: b63857d38dcb: Container b63857d38dcb25b81843c1b6eaf684ca941dc56f4585629cdb967d7bfbf8278d is not running
Error response from daemon: Cannot kill container: b2613bea3a4a: Container b2613bea3a4a156eaefb8036f1fe63684fe2b2ef917262bf1c4c23ea7503466b is not running
Error response from daemon: Cannot kill container: ac937153d440: Container ac937153d4407b397777e2c4a539bda25e231e059d87be0a1150bda6a24585d0 is not running
Error response from daemon: Cannot kill container: 48c46a6d0660: Container 48c46a6d06603638f3778e38bf0056f51d89d8db9a759d7c60f498b01d4a63e8 is not running
Error response from daemon: Cannot kill container: f1c3f8dba8d3: Container f1c3f8dba8d302c3428676258d290a44419e5229311f90013fdcbf142822ac92 is not running
Error response from daemon: Cannot kill container: a67e2023a279: Container a67e2023a2795d7609bee379fef6b38ab11f1cfc5e14ddae29e68f38938d7bfd is not running
Error response from daemon: Cannot kill container: 803bfbdcf6eb: Container 803bfbdcf6eb9b029796895a29de19e60ec954a045389365b0c90ec2e22833c4 is not running
Error response from daemon: Cannot kill container: f6088bd78a40: Container f6088bd78a40c8c620afd43bd4f58ffae10a9d226e12c2f24a672eb695273b93 is not running
Error response from daemon: Cannot kill container: 4b70f4c452f4: Container 4b70f4c452f4a222fb2187aa316e52f4e5a00b09031f4a7eeccd83e666710797 is not running
Error response from daemon: Cannot kill container: 4e5c4f0dba22: Container 4e5c4f0dba2250aa4ed706e99d82c028b6c3998cec2c71263961142b1e53a1a1 is not running
Error response from daemon: Cannot kill container: 92ca43448a06: Container 92ca43448a06b091f28df54faccf1e85dcbc4119f1e9ad67235b22f1f01d6d91 is not running
Error response from daemon: Cannot kill container: a4bc541519e5: Container a4bc541519e53fbd3c2780bf60047f92a0e0f526607f796ef963cb821f321974 is not running
Error response from daemon: Cannot kill container: ba12d7dfb861: Container ba12d7dfb8617b5b252d72f9b6e185f488b51b09758c503957ce05fdb952f929 is not running
Error response from daemon: Cannot kill container: 6e41e6f1cbf9: Container 6e41e6f1cbf99de47aab3b5bdd0d143cc1a0db8e70558affe58f9c4effe75079 is not running