GUI acceptance tests using environment deployed from packages.

Build: #2096 failed

Job: Storage sync was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
22 minutes
Revision
55bf187d0d4ebfece7f274afc16ccd4ba4d3d0b1
Total tests
7
Successful since
#1968 ()

Tests

  • 7 tests in total
  • 22 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
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  4653  100  4653    0     0  40460      0 --:--:-- --:--:-- --:--:-- 40112
Error response from daemon: Cannot kill container: 769c5f7e22d5: Container 769c5f7e22d592cbd4c8366f2c676b733d746ee614c76c33f1e9f1254848cc84 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-CSST/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CSST/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CSST/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CSST/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CSST/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CSST/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-CSST/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-CSST/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-CSST/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
W0412 09:34:25.512868     435 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  18762      0 --:--:-- --:--:-- --:--:-- 18838
Error response from daemon: Cannot kill container: 76155191ffeb: Container 76155191ffeb1ba5f8bd6b35f3360b6398389fcc20ea07ba7be2b76d57479bed is not running
Error response from daemon: Cannot kill container: 70f767328855: Container 70f767328855b5c21497f975ad5f165a1eba61dfe6da4df0086bb9ae5e7dde31 is not running
Error response from daemon: Cannot kill container: 4ebf6d90810c: Container 4ebf6d90810c6b6e062009d8e2e256a20f63122ad63607ba76ea9f40bb55bdd6 is not running
Error response from daemon: Cannot kill container: 66b86174d31d: Container 66b86174d31de90b891008dbbcdc08e1b1692c4416d6ec5e7b9bcf1293d5e8f3 is not running
Error response from daemon: Cannot kill container: 648a6da20cfb: Container 648a6da20cfbdf55fa2c5e4b455ff34520908e99eba650b0623e1c345ef0966f is not running
Error response from daemon: Cannot kill container: 7254219f4013: Container 7254219f401356b9de1142a81b426a62dae04a0fa34a55c2680d12ad8ed0cbf9 is not running
Error response from daemon: Cannot kill container: 19cd3d825aed: Container 19cd3d825aedd495a64ab93b590b4d943df36523a21339fd07f8eec50f7dabcb is not running
Error response from daemon: Cannot kill container: 14a7eb081428: Container 14a7eb0814281816feafed4f9523f5f261daf8597c2e4434640fe74e5053780d is not running
Error response from daemon: Cannot kill container: c020bb9bd423: Container c020bb9bd4234b51d94fffc902fb54ba02a4f235d4089aa9167af9d5ab6b348a is not running
Error response from daemon: Cannot kill container: 84687cd299e3: Container 84687cd299e3084c4eda742b3ceeed3099d1e7ae219e677441777990a6439f93 is not running
Error response from daemon: Cannot kill container: 094fe4348a83: Container 094fe4348a83579259b388fdd444c689a9e7e062b2c93e63d02e7c50ec59d4bc is not running
Error response from daemon: Cannot kill container: 77a61d273d69: Container 77a61d273d692ba76ae134084cbbd65158f89e87e7a2b7f028aa9f512e5968de is not running
Error response from daemon: Cannot kill container: 4d93876d32ae: Container 4d93876d32ae9bedebbd6ddbb7580c0ac3a1754c58006c6472881bfd97bf7b9e is not running
Error response from daemon: Cannot kill container: 0dce44ca91cd: Container 0dce44ca91cdbfa5dce035793b8c7f45beb0834d97c55dc68701960913f65034 is not running
Error response from daemon: Cannot kill container: ebe31b2cff36: Container ebe31b2cff36eb7a11c3f83ed374fcf65f491eac92a1e2643270177ea4a92cf6 is not running
Error response from daemon: Cannot kill container: 883bd5cc885c: Container 883bd5cc885c3844e61b42e7986eeb737bfda36f3a17165ce29f5fa5ae4c3c72 is not running