GUI acceptance tests using environment deployed from packages.

Build: #2133 was successful

Job: Chrome metadata test was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
20 minutes
Revision
8490c925f492c6fa084fa157e3410fcfda0ec6eb
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
  • 19 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  46530      0 --:--:-- --:--:-- --:--:-- 46530
Error response from daemon: Cannot kill container: 82b74ee1963c: Container 82b74ee1963c0ccfd9f6f295b70c5271db2e9d8e515ceebf819946f3f5f1d0f3 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]
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
W0506 07:53:28.763335     441 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  46530      0 --:--:-- --:--:-- --:--:-- 46530
Error response from daemon: Cannot kill container: f7146fdfec15: Container f7146fdfec15170a0f491bc4a97c5376226580ef6cf2fd2557e29e38be6bed04 is not running
Error response from daemon: Cannot kill container: e232445808b6: Container e232445808b6a94a881eb4791327e085f111fc801f1ded49f5c992d717319d09 is not running
Error response from daemon: Cannot kill container: 6a724218d05b: Container 6a724218d05b13560b3b4e068041b2ca8da775d9b529aaab634e883032742576 is not running
Error response from daemon: Cannot kill container: 9f3175711a5f: Container 9f3175711a5fecde59c9b4b1101951d2e4e7eab6ab44afb34f98feb397d65e8e is not running
Error response from daemon: Cannot kill container: a21d2d984a67: Container a21d2d984a67e446d455ff2791d354c6eadc27ad32d9276f0919ad4913ecd372 is not running
Error response from daemon: Cannot kill container: e0fe0bdff961: Container e0fe0bdff9615e04400c476ab538fb13e917f77b54d365b821680a7d69fde02b is not running
Error response from daemon: Cannot kill container: f71e765f61a8: Container f71e765f61a87c9ad1db5da32e70f990a02b75b62729536212d0a5c4896a8075 is not running
Error response from daemon: Cannot kill container: 9f970893edc9: Container 9f970893edc9c7cb2f874b7261db93916c1708151cac1877d9a0cd44e3b53ff5 is not running
Error response from daemon: Cannot kill container: 382ba055df2d: Container 382ba055df2def1166e770d1561e9fe6ae9031eec5b1142e65adf7cd13cd64f7 is not running
Error response from daemon: Cannot kill container: 3c9fa03b23b2: Container 3c9fa03b23b26154b82341ca61651fccfa5ee85fff051c330f27c72c0897c9a3 is not running
Error response from daemon: Cannot kill container: 298806e1a420: Container 298806e1a420e9f432c32c0b9881ff0b7198874b0a4a831df73ae04abd7961e3 is not running
Error response from daemon: Cannot kill container: dfee7b2f0d4c: Container dfee7b2f0d4c1c5e1ba9ee6f82e5f76260b665ee38b9ea02a24a744bd823b5cc is not running
Error response from daemon: Cannot kill container: 7cdf0a6f87a8: Container 7cdf0a6f87a8d0fb1f412565b145f8ee418eed88353053cb68e0c4ec4e603489 is not running
Error response from daemon: Cannot kill container: 01af68c29f12: Container 01af68c29f12c029ce207a9ef10bd41cb7c7e22eaa303e4ed5aad8832c19c804 is not running
Error response from daemon: Cannot kill container: b6b626aa8202: Container b6b626aa8202d090368eb9202622410342c2776f09dd501f732fadc2afc98d28 is not running
Error response from daemon: Cannot kill container: f9c867511488: Container f9c867511488efa64c8438676eca63a024a80a0c9f5f180c17829b6bff8226bc is not running