GUI acceptance tests using environment deployed from packages.

Build: #2273 failed

Job: Onezone tokens was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
11 minutes
Revision
624ddd1dfa241fb01c10e610d5a920a26351648e
Total tests
8
Successful since
#2201 ()

Tests

  • 8 tests in total
  • 11 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  38454      0 --:--:-- --:--:-- --:--:-- 38454
Error response from daemon: Cannot kill container: b60c0ab9f0ea: Container b60c0ab9f0ea39861c8732e0cb6fc3f790ab3f7865bc985df32d52a5c079c9d0 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-COTT/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COTT/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COTT/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COTT/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COTT/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COTT/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-COTT/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-COTT/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-COTT/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]
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
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
W0824 20:06:26.814600     510 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  49500      0 --:--:-- --:--:-- --:--:-- 49500
Error response from daemon: Cannot kill container: 33aa45759c4d: Container 33aa45759c4ded7820da98587c5ecb14e8222afc86d578eee67e3591671ac37b is not running
Error response from daemon: Cannot kill container: 81d0baf7e134: Container 81d0baf7e1345b61c912ffe62480b66f06d945dc0e8ad5adab36301d2da7868c is not running
Error response from daemon: Cannot kill container: 75187ab89c98: Container 75187ab89c98d3d3eba88ca59f94208ba564e5ce64653198a77c4e1782c58420 is not running
Error response from daemon: Cannot kill container: 13e194732842: Container 13e1947328424002183459cb3a7f6db7136d33df17d58c6479b0ed2bab15cc01 is not running
Error response from daemon: Cannot kill container: 644d57ec095a: Container 644d57ec095a6b1cf24bcc88cf44bac66c81d5ca13734b84d001977dae8ad75c is not running
Error response from daemon: Cannot kill container: 500bcd5ab597: Container 500bcd5ab59708aa8f335cf28edd5aa1b7e8143190535d1f8b2ec46b459f927d is not running
Error response from daemon: Cannot kill container: 97f9942d863c: Container 97f9942d863c2bcdd1d8b1cafb475c73e7a1d841e84c52b073929c2f511d90f8 is not running
Error response from daemon: Cannot kill container: 971de34eb671: Container 971de34eb67149a0c56333ed16f13af8afbfacee2da931f80eb4bd46add62f60 is not running
Error response from daemon: Cannot kill container: 6da27bc5fd01: Container 6da27bc5fd01e6c781b7c352c84416497a2337a571012978ce8e4f902b400126 is not running
Error response from daemon: Cannot kill container: 934683df982b: Container 934683df982bd7d3d654a58331fe75eeb89c9c69796788d466f2605a76d65b4d is not running
Error response from daemon: Cannot kill container: 578f3ab195f1: Container 578f3ab195f105524c4c856929c334a873cea04dacdc010bb4ec3f1bed4f3370 is not running
Error response from daemon: Cannot kill container: d41bbe4d2f41: Container d41bbe4d2f41dd96f46f0bbb6cb74aa8583a3edf4316f840253279886614b827 is not running
Error response from daemon: Cannot kill container: 3e93c2ec95f4: Container 3e93c2ec95f4279eb8da44a8754ea130d4fd07d92f299df2b00e24feebeeab2b is not running
Error response from daemon: Cannot kill container: 388830e9b6f1: Container 388830e9b6f1d59078a41136d7dde34a0f10adfd60dcef4c9b2478b659323745 is not running
Error response from daemon: Cannot kill container: 05b718c36e0a: Container 05b718c36e0a93634bb5a539916e2b96b9cc211f6f6da80f85e7f1c8e7f8cace is not running
Error response from daemon: Cannot kill container: 0770233f406f: Container 0770233f406f68e103288f8c3ca6513fa91c192e7991ec642e49a3caf1d69400 is not running
Error response from daemon: Cannot kill container: b248d72e19c8: Container b248d72e19c834a27ab2ff77c11eb51f32a2c7dd18a41281242410c94d5b0748 is not running
Error response from daemon: Cannot kill container: 2354ee4ece95: Container 2354ee4ece95064516c8008a9848d690eca3dac5ee6159739aedba24cf0358fe is not running
Error response from daemon: Cannot kill container: 51d4e541d037: Container 51d4e541d0370673ec280271887cdbb80dbc697432010181bb3b17fbef14ed90 is not running
Error response from daemon: Cannot kill container: a1ec95d8280f: Container a1ec95d8280f03d64dcaa405b6b856842353f104c6c5e26adc902e35a83f9fd9 is not running