GUI acceptance tests using environment deployed from packages.

Build: #2269 was successful

Job: Chrome metadata test was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
2 minutes
Revision
4276446edcb3bb0038d36305eb41777ffee4dfd6
Total tests
1
Successful since
#2201 ()

Configuration changes

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

Tests

  • 1 test in total
  • 1 minute 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  46069      0 --:--:-- --:--:-- --:--:-- 46530
Error response from daemon: Cannot kill container: 7b959ebe5df6: Container 7b959ebe5df64cd1a7eb2eecaf44393de6f353a4831f04f65781872f601c8f31 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
W0822 19:46:11.287346     448 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  43485      0 --:--:-- --:--:-- --:--:-- 43485
Error response from daemon: Cannot kill container: f2a65292a4a8: Container f2a65292a4a8051d687261c48e9f4b36253b262adcbb07ff99b9ea4fb3c2e599 is not running
Error response from daemon: Cannot kill container: c6f0bf0b72da: Container c6f0bf0b72da0472d8f3bf50a7d481eb00db6d1fbcf2244ff9cefecd0666fa64 is not running
Error response from daemon: Cannot kill container: 1f14faa72921: Container 1f14faa7292107fa42c77996a5cde8c2516714a2d47cef578030601b9ad36e00 is not running
Error response from daemon: Cannot kill container: 8dbb8ac27d9d: Container 8dbb8ac27d9d5aa8b6761c0208e93de68bc1e07cb025da55a706b9adf080ae7d is not running
Error response from daemon: Cannot kill container: 299fd010126f: Container 299fd010126fed42c4a57cab5218f7831f228490f446a063faddc65d588ce7e5 is not running
Error response from daemon: Cannot kill container: dcafafca1953: Container dcafafca195318751cdb3476320553ef918466f8ba647fc11f0f8afe396a76ae is not running
Error response from daemon: Cannot kill container: 39dcef66b915: Container 39dcef66b915ddbb36a8fa7dc36b238aa1b78668d506c02d25d02ce37b3027b8 is not running
Error response from daemon: Cannot kill container: 8286e0346c17: Container 8286e0346c171dfce44c646770dd37859f0acac53b3bb875ab7158cf35625518 is not running
Error response from daemon: Cannot kill container: 2b551092aaa5: Container 2b551092aaa57c71b50ce46057356417bceb3a17ac8ac3da44e86437759305e8 is not running
Error response from daemon: Cannot kill container: 858a4a2a0b61: Container 858a4a2a0b612437418842ce3b139d4015b61bd904d951ba74456b347bc7667b is not running
Error response from daemon: Cannot kill container: 4116af0fc371: Container 4116af0fc3718b3d10787c7344cc262e6d1fefa3e1b199c7a06979a4ace89f94 is not running
Error response from daemon: Cannot kill container: 8a3f70748863: Container 8a3f7074886387fb9595e1a22814e81c7d0cbfb92773e412033a2c018dab4289 is not running
Error response from daemon: Cannot kill container: 0f61fa24eb35: Container 0f61fa24eb35a4f993fb12d982fb10bff8158b49593421a5ff83ecbad9d9e6ce is not running
Error response from daemon: Cannot kill container: d276b6301170: No such container: d276b6301170
Error: No such container: d276b6301170
Error response from daemon: Cannot kill container: a6952cbfa5b2: No such container: a6952cbfa5b2
Error: No such container: a6952cbfa5b2
Error response from daemon: Cannot kill container: 8366211e4e07: No such container: 8366211e4e07
Error: No such container: 8366211e4e07