GUI acceptance tests using environment deployed from packages.

Build: #2132 failed

Job: Chrome metadata test was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
19 minutes
Revision
39fb434fa4268b56f32dccaa52527f3591cd9ea8
Total tests
24
Successful since
#1943 ()

Configuration changes

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

Tests

  • 24 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  43083      0 --:--:-- --:--:-- --:--:-- 43083
Error response from daemon: Cannot kill container: 14d19cce25d7: Container 14d19cce25d74996433658074fd9ff35561893cd1d2ba41ecc806a878186ad0c 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
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
W0505 22:36:09.665042     437 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  48978      0 --:--:-- --:--:-- --:--:-- 48978
Error response from daemon: Cannot kill container: bc5b678cb897: Container bc5b678cb897b0d7a975f79239122e0fff58269d0eaf5b7648c397b73ed72693 is not running
Error response from daemon: Cannot kill container: 119645c3f2a5: Container 119645c3f2a56b1c38c83fd829e491ac4d5d23df3f4f869386a6a31294103b0f is not running
Error response from daemon: Cannot kill container: 129f90384e61: Container 129f90384e61700e1de15cb5106142c3f74fc659fe1e05aa619780c66b881ddf is not running
Error response from daemon: Cannot kill container: df1acc7747e1: Container df1acc7747e111484d0099205438d53a49a139e6f388d2415719f5c751500594 is not running
Error response from daemon: Cannot kill container: 7ed5b1c39471: Container 7ed5b1c394716664ca5146f9c2ad8d01c7576e3f1b7ddbccf8dfcaa0db1de397 is not running
Error response from daemon: Cannot kill container: b4e52cd802be: Container b4e52cd802be0bd9127cfb45d1b239a3bc92b8de3dde899172acb59d1c3b5a0b is not running
Error response from daemon: Cannot kill container: d47d24db0ad6: Container d47d24db0ad6fa17d9203364b7a8fe4a1a52b0784233c43ed59b357fc14b7595 is not running
Error response from daemon: Cannot kill container: ae41de8ccb1f: Container ae41de8ccb1fa13432dc4e9ded77a6df4d8915395da06b947c8d8c4aab2e817e is not running
Error response from daemon: Cannot kill container: 48af0964c03d: Container 48af0964c03d997c33244d3cbacabed2a0b0e40a74125d1629f0eed67757c3a2 is not running
Error response from daemon: Cannot kill container: 657fec3ffa3c: Container 657fec3ffa3c7f910290ce591cf2d42033c3dbd6495ddbc7bbb2b48ff9c8d967 is not running
Error response from daemon: Cannot kill container: 5ff938e918a9: Container 5ff938e918a9cf077dbd1af7e66b314778a8e3bc4bd33999b6c4e5fd2cf9d517 is not running
Error response from daemon: Cannot kill container: b8d0c34bf9ca: Container b8d0c34bf9ca9f9b0159e7c80aa8ce9402d753d4ac639a781c759652f474be87 is not running
Error response from daemon: Cannot kill container: a324a843536e: Container a324a843536e6ba6cbad07f06b3bf2d4b215f09ab34b63ef31134ab4a45a3014 is not running
Error response from daemon: Cannot kill container: dc7e5f93987b: Container dc7e5f93987b7c575de1e16211a88792f17f107eeea21ebf2b1175c9fa33440c is not running
Error response from daemon: Cannot kill container: b5f903f71c6c: Container b5f903f71c6ced2bc8691cda5cf4de2dbf30603879fcc12944f9707701128a5a is not running
Error response from daemon: Cannot kill container: ccf81568ec93: Container ccf81568ec938d965b9877c5fc1d34ccaded1ce5bbf017ae151edd2632d91651 is not running