GUI acceptance tests using environment deployed from packages.

Build: #2000 was successful

Job: Oneprovider hardlinks was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
19 minutes
Revision
3472d8727468cf978131865efabe3f31a6595f39
Total tests
11
Successful since
#1968 ()

Tests

  • 11 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  40815      0 --:--:-- --:--:-- --:--:-- 40815
Error response from daemon: Cannot kill container: 874e5fc77f7b: Container 874e5fc77f7b80922e39c9eace176a0ea08d3054ffeefe42692c6392de31f43b 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-COH/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COH/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COH/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COH/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COH/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COH/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-COH/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-COH/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-COH/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
W0226 01:32:43.198405     442 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  26895      0 --:--:-- --:--:-- --:--:-- 27052
Error response from daemon: Cannot kill container: c564ec695fe9: Container c564ec695fe962042b8e5956ba1ab2088f9626ba9d404b9b7fb172b9d34c91c3 is not running
Error response from daemon: Cannot kill container: 7093f1344e5d: Container 7093f1344e5d7ddc04c9144fcb76a4ba5e2ca584ad0db49eff079fd98dfd0a41 is not running
Error response from daemon: Cannot kill container: f03debac3a6a: Container f03debac3a6a76d47d56a490621067015e3d3e89057b1a7b8a234aba666bd364 is not running
Error response from daemon: Cannot kill container: e354d09a2d43: Container e354d09a2d43bff5e138385dd2f908e8e7f0df4a391cd9a302a5fb2855904315 is not running
Error response from daemon: Cannot kill container: 0e534f623422: Container 0e534f623422f55a42dd972eb35aa91d162f78b0c56d73f30a45a988d1b2bcb0 is not running
Error response from daemon: Cannot kill container: ae9a517ff793: Container ae9a517ff793071a2f2a4e9e3ff655c383682b8738e2f8b9ea6d99e1d48ef66c is not running
Error response from daemon: Cannot kill container: 3c2c510f49e2: Container 3c2c510f49e230f1dd2e0f538d729c90108c85b8ccd47aa42e947057f7674aac is not running
Error response from daemon: Cannot kill container: 6f570b708b28: Container 6f570b708b280769eee54f29a1e38566d3ccbbbdb446569a3e02fa6803b62f9a is not running
Error response from daemon: Cannot kill container: f792fdfb09d5: Container f792fdfb09d59ef51216e39bc617fe54642f30f94e95aa812d6b5b212abd0cdc is not running
Error response from daemon: Cannot kill container: b2bc1790c6d9: Container b2bc1790c6d9f6b8ef0f49a43baaa82aa8a0d2406cb7c8a3ce7e49ccb45229fb is not running
Error response from daemon: Cannot kill container: a1033197e679: Container a1033197e679ac94592753f2952c46808869c75cb9739175c37ab611319cb6ea is not running
Error response from daemon: Cannot kill container: 64727eb5a411: Container 64727eb5a4118bcfc1361db3c33493d17055035d132820a6aa754c510cd15dde is not running
Error response from daemon: Cannot kill container: 69139c42ca10: Container 69139c42ca106c9d0034329367e1526e188bcd5090a03bf2e93bd1ca46f4ef25 is not running
Error response from daemon: Cannot kill container: 5f4a952c69ff: Container 5f4a952c69ff5bb436750cbb6c08058b20d526440f071236cdc606dd5c178b14 is not running
Error response from daemon: Cannot kill container: 16dcc56d9f46: Container 16dcc56d9f46a113c098bae2d54ffcfa03eb7fff1d7fbcc6811efdd656c746d3 is not running
Error response from daemon: Cannot kill container: 92e5a5172a77: Container 92e5a5172a7761de9f2655665d56d0eacbdcb5addc05ac6077524c887179fd0a is not running