GUI acceptance tests using environment deployed from packages.

Build: #2201 was successful

Job: Chrome metadata test was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
17 minutes
Revision
442fbc00c3ff98eb304229ca0f7f38a6c9aec746
Total tests
24
First to pass since
#2200 (Child of ODSRV-OZP-1760)

Configuration changes

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

Tests

  • 24 tests in total
  • 16 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  45174      0 --:--:-- --:--:-- --:--:-- 45617
Error response from daemon: Cannot kill container: bbb35d9dead1: Container bbb35d9dead16827d0a355eb0d0bb9578374612ed1efa89e489ba2eb5f483c9f 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
W0705 21:27:19.187189     444 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  47479      0 --:--:-- --:--:-- --:--:-- 47969
Error from server (NotFound): pods "dev-oneprovider-krakow-0" not found
Error response from daemon: Cannot kill container: bd2beef5010d: Container bd2beef5010d17bee09f2fde2fa8eab2be17021aa183becb2ec107dbd633997d is not running
Error response from daemon: Cannot kill container: e6611f436cc2: Container e6611f436cc262973ba35764e70e10cc9b28a17d40d19c6d5b9df13f27afc023 is not running
Error response from daemon: Cannot kill container: a75663ff1569: Container a75663ff156907856a997d7dc6bd1730b945b29e4897b159cbcfb155f2e25a61 is not running
Error response from daemon: Cannot kill container: 6b98322d72fd: Container 6b98322d72fd4f715b164b4ae9c7fa0f40cd2f705629dcdc527c84040e331db5 is not running
Error response from daemon: Cannot kill container: 6e325c10d87a: Container 6e325c10d87a8b9e837b7f951e41e98a8575eeec824abf40b50a66f2147c3537 is not running
Error response from daemon: Cannot kill container: 7242cceccb83: Container 7242cceccb835f4ac105eccf9af5e2e90c3ee9cbb076a3e9e17399390bc595b8 is not running
Error response from daemon: Cannot kill container: ba08f3c4ef60: Container ba08f3c4ef6049c8fdfb9757845b6d827cccf0087db2e42c282780001f1d379d is not running
Error response from daemon: Cannot kill container: 475b741dbeba: Container 475b741dbeba61ea4897a1781ae0e3448b70b016585892c399f19b5494a0f4be is not running
Error response from daemon: Cannot kill container: 68d3f7c99b10: Container 68d3f7c99b102e6e711c42e1869dd07415783bdfa344fb17439a2f8912a2bc25 is not running
Error response from daemon: Cannot kill container: 5f07ce8187e2: Container 5f07ce8187e2abfa17da863b73b386b5355f04be621648d64f4967402e8aa671 is not running
Error response from daemon: Cannot kill container: 1dc39cff6b0c: Container 1dc39cff6b0c63be1177ea6930d722e338cad483c5dd13f1359e19dbe44e2029 is not running
Error response from daemon: Cannot kill container: 078a8cd6479f: Container 078a8cd6479ff6877c53721970cdb86c522f59d3133bb78dbda05510297cfb21 is not running
Error response from daemon: Cannot kill container: d8a4fd73d683: Container d8a4fd73d68327e10b0d0d8062b381b339f1daed1ae8a3db65ba42e62c3e2de2 is not running
Error response from daemon: Cannot kill container: bfdfdd5bd448: Container bfdfdd5bd448efafcb66ec621849b63ac63350fabf11901b8969204d271ae565 is not running
Error response from daemon: Cannot kill container: 5afdb8cf4d98: Container 5afdb8cf4d98657841dfee157c1a25faa899dc6eca0c376ef58cb326d45caff1 is not running
Error response from daemon: Cannot kill container: 811b9446b2d7: Container 811b9446b2d7f2ea1ec91ad43b8dd7bb6d953bd6ed12dd897508b667ffcbcd23 is not running