GUI acceptance tests using environment deployed from packages.

Build: #2144 was successful

Job: Chrome metadata test was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
18 minutes
Revision
3f6eba726c9f477b80c64f61e18d18c4a18e4f06
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
  • 17 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  48468      0 --:--:-- --:--:-- --:--:-- 48468
Error response from daemon: Cannot kill container: c62ae709ffcd: Container c62ae709ffcd5176e81a7249c9686a4945dc80c842006a0e81548c3af1c1a558 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
W0519 20:54:37.939455     438 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  45174      0 --:--:-- --:--:-- --:--:-- 45174
Error response from daemon: Cannot kill container: f1f80f52ac45: Container f1f80f52ac452f1c91903bfd5d554ceb64029b02462cc300f1a235886a0e43c8 is not running
Error response from daemon: Cannot kill container: b8edf304d9a8: Container b8edf304d9a84e67a4063368ed6224bc18309f1b20a2eda0fe058b29bf332d8d is not running
Error response from daemon: Cannot kill container: bbd186edc621: Container bbd186edc62190844835458ed2ac8900a39df5316c46c34e0dd018fe60347a5c is not running
Error response from daemon: Cannot kill container: 4f9d42645039: Container 4f9d42645039db371ce2aed537d08917a13d246fca89281f081f6ca8c86f39f8 is not running
Error response from daemon: Cannot kill container: caf8a16affb3: Container caf8a16affb3e27b71809c925d679d9c4eaa16392356c3f1f65569c20828c9d3 is not running
Error response from daemon: Cannot kill container: 6d810a063f2a: Container 6d810a063f2a240c3caf969f465c26a1356ad6ea26832a65f1248a2c4e50ef79 is not running
Error response from daemon: Cannot kill container: 22b47c321961: Container 22b47c3219615e3459ad6d48af5214a829432a4f263636cc78cca4a9fbfcfb3f is not running
Error response from daemon: Cannot kill container: e7145fb30e3c: Container e7145fb30e3c6e9566315b98b7ffe6d86b92b0cba1e185937d6b218bc199d0c8 is not running
Error response from daemon: Cannot kill container: 1bf1941a8f79: Container 1bf1941a8f79cb453183fc9e510961a7e9551746ccd94484a0a58a37af950555 is not running
Error response from daemon: Cannot kill container: ce29b2234fb2: Container ce29b2234fb2e535b3ea1c4a25f86a556b5940eaa6108c6695c98cac3fd2d524 is not running
Error response from daemon: Cannot kill container: 97d3d6d9731f: Container 97d3d6d9731fb28c58119993d98cd0563d4d51ba086ea4068eb51c7cd5075d13 is not running
Error response from daemon: Cannot kill container: 1d59da3f7e2e: Container 1d59da3f7e2e8348a8081606a1540e31a33687775df40472c0993cfbbf15b54a is not running
Error response from daemon: Cannot kill container: 17c26328137d: Container 17c26328137d02cb7f6417fa91e34a33fce74149c191dab8dee6283347638465 is not running
Error response from daemon: Cannot kill container: 18e63300cfcb: Container 18e63300cfcb80af914807543c5070d26cdb3d51bbc03e20a64cfc2763411004 is not running
Error response from daemon: Cannot kill container: 14395c23bd0c: Container 14395c23bd0cff53a4448f528e8f4f0e2c335dcd9bbe1f3169077260ca01e4ef is not running
Error response from daemon: Cannot kill container: ca62430a7fc3: Container ca62430a7fc328c45c0da88899332a133ab2b2863eda9379353e4940a2858eab is not running