GUI acceptance tests using environment deployed from packages.

Build: #2205 failed

Job: Oneprovider ACL files was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
14 minutes
Revision
1fe3e42089bf1cc76fd057bfa36bd47351e44af9
Total tests
8
Successful since
#2201 ()

Tests

  • 8 tests in total
  • 13 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  47000      0 --:--:-- --:--:-- --:--:-- 47000
Error response from daemon: Cannot kill container: a9b136ed10f0: Container a9b136ed10f0bd9566e6ffd43193ec177b02c745944e540a96ff3844dcfbf477 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-COAF/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAF/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAF/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAF/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAF/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAF/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-COAF/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-COAF/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-COAF/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
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]
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
W0706 21:59:57.274407     444 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  33963      0 --:--:-- --:--:-- --:--:-- 33963
Error response from daemon: Cannot kill container: c58d06990365: Container c58d069903659a718d74ed6bb635ec06368e1e4b347fe60c9d41338a012af314 is not running
Error response from daemon: Cannot kill container: 56cae20de5f2: Container 56cae20de5f2cdcb2b6516173abf9e99ba592ca6a95d7f92a1a252081dfdee24 is not running
Error response from daemon: Cannot kill container: 270a932a0ee1: Container 270a932a0ee158252572342604639c431a5809ea7eb4ce8eea996907f3482d2f is not running
Error response from daemon: Cannot kill container: f7af37ac8e6a: Container f7af37ac8e6a489846c6bc9b06240df1f924e0b073775c672046e1e9a1c532e7 is not running
Error response from daemon: Cannot kill container: dab3bb2eecd2: Container dab3bb2eecd28fa3f7f469369c180ea1ab23934a4454f346393d1fed73971e5d is not running
Error response from daemon: Cannot kill container: f6bcd7e2ad60: Container f6bcd7e2ad60c5157da8e8f1191c83f2a4bc755cdbb6f491888ff150487e6f03 is not running
Error response from daemon: Cannot kill container: f5bd6b73b521: Container f5bd6b73b521438a51ee4a8206ae7b52e9719506511fffb9e23406e10c919db0 is not running
Error response from daemon: Cannot kill container: f964b831bc78: Container f964b831bc788a8bebd28ece9b39266aac4cb30252c557d96cd7bcaaaac2f76e is not running
Error response from daemon: Cannot kill container: b17def7ea0d5: Container b17def7ea0d5c8a93dc66494704a9050e57bf4a0313020f56f845d6bf2e46f9d is not running
Error response from daemon: Cannot kill container: 0c764cf4b7d9: Container 0c764cf4b7d9714df4af64eb3583f038839ba3caf2c16d6d00fb4e8f49072aba is not running
Error response from daemon: Cannot kill container: f87eb9ed0602: Container f87eb9ed0602a46da7fafbfb5652804564bb3e2924b5210aa8ea1ec1dd90364e is not running
Error response from daemon: Cannot kill container: 5881e364f327: Container 5881e364f3279f2a50c726f43052237ffb13588ca579bbdf4b0f6453b076655e is not running
Error response from daemon: Cannot kill container: 8984e04a1ec7: Container 8984e04a1ec706f300d90b709562453c2ac5961b0c4e8d86e838fa59b17c746a is not running
Error response from daemon: Cannot kill container: 3c1fcd9e4a8b: Container 3c1fcd9e4a8b7f229172e2db15ddc151ed31cc88dbe24cfd9613adaccf4b6504 is not running
Error response from daemon: Cannot kill container: 48a2ee52faaa: Container 48a2ee52faaab785fd4ee4c7b65c2e3927ee415436313326f85a22cf8cf9dd64 is not running
Error response from daemon: Cannot kill container: ded489645518: Container ded4896455180cff0ae2696e942df67495ed62a96e6ad611376714e71cc3b7ee is not running