GUI acceptance tests using environment deployed from packages.

Build: #2188 failed

Job: Chrome metadata test was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
17 minutes
Revision
b4d860b5861bbdf70e232df4cd30025ff9f48d0e
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
  • 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  48978      0 --:--:-- --:--:-- --:--:-- 48978
Error response from daemon: Cannot kill container: e7889465b8e7: Container e7889465b8e72bbef5a3667e7494ca95832c3bfecc097fbf3dfaa44f7b4291c6 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
W0629 20:11:14.966130     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  37829      0 --:--:-- --:--:-- --:--:-- 37829
Error response from daemon: Cannot kill container: b2674138c64e: Container b2674138c64ea8db9ae1476cc64cef5927c1b6016f7d4c656d6586f876eb8f6f is not running
Error response from daemon: Cannot kill container: d897b0bd3e5d: Container d897b0bd3e5d5356715bf1eee82de8f9a47b32aa4119f67cbc8b3abf0fdf30c0 is not running
Error response from daemon: Cannot kill container: 9611c9f48740: Container 9611c9f48740a21a327e68ddf516bfb4da3535148adfce39a862f299e219417e is not running
Error response from daemon: Cannot kill container: 6761939944e7: Container 6761939944e7680671e1f3879846b438692f12c94d59b74425aeae26a65c8fb3 is not running
Error response from daemon: Cannot kill container: 1feb1b9e808e: Container 1feb1b9e808eeb21d8035b15e5566258af01b747ed1927f47da69d3311e33f2d is not running
Error response from daemon: Cannot kill container: a014dc937c7e: Container a014dc937c7eee9ab8630b90189662f4acfb087f668cdbeb574bdd74dd2217d9 is not running
Error response from daemon: Cannot kill container: 52d8d95f1653: Container 52d8d95f1653fed504e3aa0930705b570c7232c3e672272b31b232f1d5c787f1 is not running
Error response from daemon: Cannot kill container: 45aab37bc0b1: Container 45aab37bc0b1419f06678681ecd021f20709d3295e98050020e9c1ea3cc04057 is not running
Error response from daemon: Cannot kill container: 143d4c7f2c09: Container 143d4c7f2c0930e4840e9d9e0ba6c2f33c56fab1ce9d398e78903ee570602f6f is not running
Error response from daemon: Cannot kill container: 24380d6c07f7: Container 24380d6c07f758b9cf71c81cd4181c9d6f8ce5e10ca59ef8f21f01601c18a739 is not running
Error response from daemon: Cannot kill container: 31edf3ec2116: Container 31edf3ec211685dc6652ae5ae376606f2dee1d73ccd992d26dfd50fd8285d16a is not running
Error response from daemon: Cannot kill container: a34897e301fe: Container a34897e301feb03d9f63a6c66fdbb64025a1d058b8a1d6e1791d4c836eccb2c9 is not running
Error response from daemon: Cannot kill container: ec0948f30840: Container ec0948f3084071e68cb935fe38640361b65515737e6f1c78290788c52d8a4685 is not running
Error response from daemon: Cannot kill container: a46c7e19878c: Container a46c7e19878c60230dc3e720802c53f2dc3d654ed2e3848f699c09d2d7a9ea51 is not running
Error response from daemon: Cannot kill container: c9ca48b52e52: Container c9ca48b52e52e374726385ee30801431b3873e0adfcefad076ed0747f0a5a19c is not running
Error response from daemon: Cannot kill container: ef4e8b5732d7: Container ef4e8b5732d751ba325075c545c616d6c991c913c501ee0dd6e34e84d430691c is not running