GUI acceptance tests using environment deployed from packages.

Build: #2107 failed

Job: POSIX multiuser was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
20 minutes
Revision
616ef003a0a36dc00e59f722ca7550385601e480
Total tests
8
Successful since
#1943 ()

Tests

  • 8 tests in total
  • 19 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  42688      0 --:--:-- --:--:-- --:--:-- 42688
Error response from daemon: Cannot kill container: d9ccd6ac2377: Container d9ccd6ac2377523d4adab7054b0d214d0202edc9aa5e52f9dbb3ab254c9ec07b 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]
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
W0419 08:29:23.745856     439 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  34984      0 --:--:-- --:--:-- --:--:-- 34984
Error response from daemon: Cannot kill container: 18ef84a6fe91: Container 18ef84a6fe91c2dc139e1c62e4263707779da577efd1100ae44be97c6c8da680 is not running
Error response from daemon: Cannot kill container: eab20c3725a0: Container eab20c3725a0a25a08610c0a9ef3f27733b52f70b0de82ddfb09c7e956ed4c60 is not running
Error response from daemon: Cannot kill container: 899ed319b17c: Container 899ed319b17c12c1aff6958703b35a4f33f2172355d79342d561b97a41a12ba3 is not running
Error response from daemon: Cannot kill container: a4f79e3249c0: Container a4f79e3249c0bcb9e953b523ab818e074a5c63f3c8d5736f9aa0b42e5660811e is not running
Error response from daemon: Cannot kill container: bef109ff967e: Container bef109ff967e6e64604b1b2c42bd19a7f22551a6a8905d7231938a508f4dd464 is not running
Error response from daemon: Cannot kill container: c15a45c9b594: Container c15a45c9b5944b20d639918e6f812559862238a8a59435a12b9dc9e5594564e3 is not running
Error response from daemon: Cannot kill container: d28941e89c06: Container d28941e89c064d3350bab992cfe1fdf26d00108e77d1827dfc44709a35c9d92a is not running
Error response from daemon: Cannot kill container: 6f447bc7b373: Container 6f447bc7b373a9e577332fbe9e1d2fbb863d6057b5305c5e2d930b74a1cf80f8 is not running
Error response from daemon: Cannot kill container: fbceb7a360d6: Container fbceb7a360d654b9a9f2cdc39974c5fbe592ffed59aac4e6ec947802cfc4b63b is not running
Error response from daemon: Cannot kill container: df45dd1c9dfa: Container df45dd1c9dfa13d92156846ae4395a43fadb0a4466676b53f2fcfcec0d503fd7 is not running
Error response from daemon: Cannot kill container: 1d269bb39665: Container 1d269bb39665538e5d130427c2b015810f0a7e53acd9e11900b8241831e76511 is not running
Error response from daemon: Cannot kill container: 3a4d4f5e2dda: Container 3a4d4f5e2dda6cf969178613b82712e96ff33a1fc0d8304751af17d883884d8a is not running
Error response from daemon: Cannot kill container: 21d0b9ebbf56: Container 21d0b9ebbf56b7d0060225489628b9e98bf8ff31f1a17040e1599a5ce934c940 is not running
Error response from daemon: Cannot kill container: 9e88e7044aba: Container 9e88e7044abadf924bb30f50fde4b3e4dfbec9126d1e86644d901197942c599f is not running
Error response from daemon: Cannot kill container: 0e4fc004214f: Container 0e4fc004214fb8072f0e8b0ff0495a4d6f129fb7d01c192596852b3e009a1932 is not running
Error response from daemon: Cannot kill container: 7cc218482458: Container 7cc21848245828880f4a2a29a92df8a934dedba58f13ee8612b452b5c667ff34 is not running