GUI acceptance tests using environment deployed from packages.

Build: #2042 was successful

Job: Chrome metadata test was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
18 minutes
Revision
d4a37ebda8d9cad234b655aae75d29294552ebb5
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
  • 18 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  42688      0 --:--:-- --:--:-- --:--:-- 42688
Error response from daemon: Cannot kill container: 8caa373d4e5c: Container 8caa373d4e5cc6c35d7b8520149491a6296bb47caef81d826b43d7965c251c62 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
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]
W0322 12:09:48.239352     428 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
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  4653  100  4653    0     0  48468      0 --:--:-- --:--:-- --:--:-- 47969
Error response from daemon: Cannot kill container: b4548b995dda: Container b4548b995dda41d502f413b22b5a337ab834c3c2df80632199440a66c42034b4 is not running
Error response from daemon: Cannot kill container: 1865d8b79707: Container 1865d8b79707c0fc407d570fe876924cc9836281a64ee611b05f30ba5c6029bd is not running
Error response from daemon: Cannot kill container: 44729bf94ab4: Container 44729bf94ab4c876c2739bb90cedac572d22eb9ee010f07cdc99eca92b7cc493 is not running
Error response from daemon: Cannot kill container: dd485011fd2e: Container dd485011fd2ebf2b5000dcec9d9fdf67114522c933d0c78a48b0b5bd4d63c0b5 is not running
Error response from daemon: Cannot kill container: 6e8ef0f6d5fe: Container 6e8ef0f6d5fe4840ffd6dd7da992991885fdbeb5ee4035ac9422dc66e3c3a878 is not running
Error response from daemon: Cannot kill container: 25e48ed0669f: Container 25e48ed0669ffaa71e005688c31a3c4f9638d4a719adfcb21e48fce11df43605 is not running
Error response from daemon: Cannot kill container: 8b1035bbdceb: Container 8b1035bbdceb9bd1527b8be5a43107b88b1c3c646da04e99bc2ca0d795badd40 is not running
Error response from daemon: Cannot kill container: ffa017aded55: Container ffa017aded5529539cf6bdc9264472d71c392527481b163ac5a101fe07a22f71 is not running
Error response from daemon: Cannot kill container: 1ad316da3e80: Container 1ad316da3e8015564049b3388f2f723a7d8ac2b46c5d26514fcc7e7c1bd9a45d is not running
Error response from daemon: Cannot kill container: 087175c312bc: Container 087175c312bcdeedf7a8f1bf87b8ccb998c89ba0184668709ace774458545ea4 is not running
Error response from daemon: Cannot kill container: 209bbfc413c2: Container 209bbfc413c20e6a20293df034fe7a4af7ad3df6bb9d7324eb00a33808205025 is not running
Error response from daemon: Cannot kill container: 98394ff3ebf0: Container 98394ff3ebf07a35524af7d485fa5c5cedd9b419556a30401e504680a670de9b is not running
Error response from daemon: Cannot kill container: 27696de0c0be: Container 27696de0c0be2c63ed1633754130cf200020668c409eb0b31cb45661168ef946 is not running
Error response from daemon: Cannot kill container: 5af4eff11d88: Container 5af4eff11d88f60fc052cda3dbadd34f2fc8d8da6c050b984456b2e0ba16fe18 is not running
Error response from daemon: Cannot kill container: 6a6e1112195f: Container 6a6e1112195feee45b2fb6cb3bb9163977cb6313b2dabf58ab9ce6fbcc86c040 is not running
Error response from daemon: Cannot kill container: 2d05f22a00d6: Container 2d05f22a00d67b38175e3051797b13c3a6a77d7920ceca09592962c628c88bcd is not running