GUI acceptance tests using environment deployed from packages.

Build: #2265 was successful

Job: Chrome metadata test was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
2 minutes
Revision
5049698a34395b30e4aeaf70b767f7a38cd18cb6
Total tests
1
Successful since
#2201 ()

Configuration changes

Job Chrome metadata test with key ODSRV-GAPT-MTC no longer exists.

Tests

  • 1 test in total
  • 1 minute 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  46530      0 --:--:-- --:--:-- --:--:-- 46530
Error response from daemon: Cannot kill container: 7b388993bdee: Container 7b388993bdee7b2c5915b4ebf6e5bdaccf8e6fafdf4a92f3bfa90fc07a36df7c 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-MTC/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-MTC/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-MTC/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-MTC/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-MTC/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-MTC/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-MTC/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-MTC/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-MTC/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
W0817 20:35:37.531433     457 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  47000      0 --:--:-- --:--:-- --:--:-- 47000
Error response from daemon: Cannot kill container: 2af83ea78fc8: Container 2af83ea78fc83f777737fbbad9b34aa6c8ce39ff25dd09ee3b7449c6cd2c8927 is not running
Error response from daemon: Cannot kill container: 165ee308b76a: Container 165ee308b76a4a9806f6443932b86df31b34b521967080ce8156226d4d4d6462 is not running
Error response from daemon: Cannot kill container: 0c3f88351cdb: Container 0c3f88351cdbd9037dd0c74e83caffe535845fc1d6d65b2321f554b1129bb9da is not running
Error response from daemon: Cannot kill container: ccded69048cf: Container ccded69048cfa4860a1d4f722eb638e98c166f08b69de6233f77e3069c3f05da is not running
Error response from daemon: Cannot kill container: 1c53d019ecd3: Container 1c53d019ecd309e5388a7fb9953f8af881aeff19b91431ae3f457586c73f00b7 is not running
Error response from daemon: Cannot kill container: 68cf7b09af85: Container 68cf7b09af85035288a1cda77f066bb61002c24807fd07ca3e41832a7dc06891 is not running
Error response from daemon: Cannot kill container: 4a02e3b824f0: Container 4a02e3b824f0b16385f06e5d9cb937d871a7fca9991c2e7a6aa0c8e73212f6b4 is not running
Error response from daemon: Cannot kill container: ea234421b80a: Container ea234421b80a1ca4384ecb950280b441fcc731379c2495ae53cd3df6e87677cd is not running
Error response from daemon: Cannot kill container: 3318b8a3b55f: Container 3318b8a3b55ff839407cfe2986a97375d30aab28f1167284bfb6a487909cebde is not running
Error response from daemon: Cannot kill container: a001155a1665: Container a001155a16650961c88d1b65775f0efcbb1992a6fbbed8a6e1e0e950db0af050 is not running
Error response from daemon: Cannot kill container: 39ed14c079aa: Container 39ed14c079aa712a1231db2ed132afeb9425da6e7c13dafc756dcbf6c127019e is not running
Error response from daemon: Cannot kill container: bae7b19c3fe4: Container bae7b19c3fe497b73823480afe0e053237e47f93bc2c732a03d9d78abffafa53 is not running
Error response from daemon: Cannot kill container: 960dc4110833: Container 960dc4110833c68a24e5152e814419624a0708f17a94f848c5cd1397056fcbaf is not running
Error response from daemon: Cannot kill container: 41d6725216a3: Container 41d6725216a3b14834e074b74fd34eedb1ba428d362ac1da99f0ab516c9be530 is not running
Error response from daemon: Cannot kill container: 0676774c46cd: Container 0676774c46cd2123153bd2a9a69b0198193e5a2e14c7a02eb3d5552d77ca0bb2 is not running
Error response from daemon: Cannot kill container: 682276fffecb: Container 682276fffecb59093bdad230666528fd9dbb22590ef97fd336dd3d0b360169b1 is not running