GUI acceptance tests using environment deployed from packages.

Build: #2194 failed

Job: Chrome metadata test was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
29 minutes
Revision
7962320fc91339139caa9ba1e01bf289858ec429
Total tests
24
Successful since
#2187 ()

Configuration changes

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

Tests

  • 24 tests in total
  • 28 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  39769      0 --:--:-- --:--:-- --:--:-- 39769
Error response from daemon: Cannot kill container: 1659d387f13f: Container 1659d387f13fda1e040dec0b36213b0d3cc46cb8b79bfe1e1a39edb272cbd7ac 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
W0701 07:27:11.290887     453 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  24619      0 --:--:-- --:--:-- --:--:-- 29264
Error response from daemon: Cannot kill container: cc96c32e67eb: Container cc96c32e67eb231c66e9325d74849aa6321d6f38f78e56a0dc57f9787fa12538 is not running
Error response from daemon: Cannot kill container: 687d1ef1267a: Container 687d1ef1267a75fa27d0bf9c01ef053a392ab2359191e472dddaeda06c95ed91 is not running
Error response from daemon: Cannot kill container: 252389d6b9c7: Container 252389d6b9c729afdcfc704b63c24cb835ad66fbe378701b019de90e35297a73 is not running
Error response from daemon: Cannot kill container: 278f2d2fccc1: Container 278f2d2fccc115f5147301a27303beecafd27a1d5203eb4a02708cd8f96829c5 is not running
Error response from daemon: Cannot kill container: 1fe9ceaf649d: Container 1fe9ceaf649dd4282c02f538470a9ba634dfae204c90d50f0f5fe908ad68f59f is not running
Error response from daemon: Cannot kill container: 7191240f0fa8: Container 7191240f0fa87d1f3587c4d5d3d91112fde5cd74dabc40de29f999ee814ef047 is not running
Error response from daemon: Cannot kill container: 205114c4fa09: Container 205114c4fa092c1ed486427f6fff302260c09d7c604e968654e81538f610f099 is not running
Error response from daemon: Cannot kill container: 29c84372a7ec: Container 29c84372a7ec6e68e1888427a1cca7823b56ad0885ffec4233f8985d1272f1f8 is not running
Error response from daemon: Cannot kill container: 330c119a7a7f: Container 330c119a7a7f8bfd6351044bc045eacecdeeb29ec93d475006f25ffdc717edad is not running
Error response from daemon: Cannot kill container: 94d50cc07125: Container 94d50cc0712510f14e660db45e2c95154b930204b45571df98e974116c67b922 is not running
Error response from daemon: Cannot kill container: 1ad851c0756f: Container 1ad851c0756f99ab08069e71ade758fde98e4369ceb13c51ad66dd75c48de1aa is not running
Error response from daemon: Cannot kill container: 6e7f031a4cbb: Container 6e7f031a4cbbe4ca7b053d9bb275a2c6108e02a7ec2518d6a193f510ecb08d12 is not running
Error response from daemon: Cannot kill container: 5ad1a07833ad: Container 5ad1a07833adfd2a5e9b09ee2dc2c8f457420f23031b9bb6cc579f47a8bfd5b0 is not running
Error response from daemon: Cannot kill container: ac873e4fecfc: Container ac873e4fecfc7b6cdda8b33392ad7e6ec3fc0f997973076e18c1194641dcd375 is not running
Error response from daemon: Cannot kill container: 6be1e04b9384: Container 6be1e04b93845915214a8946706dc363bfb7148265ba698ce4f79b8e1b7f4682 is not running
Error response from daemon: Cannot kill container: 2799a0cd5123: Container 2799a0cd5123488ee8d5d57dfe5447f6b26ad5fc9d4b224a95e5bead80b1369a is not running