GUI acceptance tests using environment deployed from packages.

Build: #2273 failed

Job: Chrome metadata test was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
4 minutes
Revision
624ddd1dfa241fb01c10e610d5a920a26351648e
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
  • 3 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  41544      0 --:--:-- --:--:-- --:--:-- 41918
Error response from daemon: Cannot kill container: 0f5f6e47d9bd: Container 0f5f6e47d9bd83d5949f65cefeaaf35a2eda9fc7a5cae3737ce78ba34b1482bc 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
W0824 19:30:06.143037     440 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  29826      0 --:--:-- --:--:-- --:--:-- 29826
Error response from daemon: Cannot kill container: f5759a0c6024: Container f5759a0c6024d8175ca1b41c4ca16c7a2d91e35e54ed19dc5ce38e46f79cfbbe is not running
Error response from daemon: Cannot kill container: e1a28626f263: Container e1a28626f26385f2388550b6249a79f6fe65cf027c765337892f1d587edf7726 is not running
Error response from daemon: Cannot kill container: 3062618a2e88: Container 3062618a2e88305c793c56f9144a517f47de69bc2ea76ea27e85df3f5adb371e is not running
Error response from daemon: Cannot kill container: 3428d2d34205: Container 3428d2d34205512c61d54e3c79889bd8a0f2acaa71269a8ddeca90855b7aeb69 is not running
Error response from daemon: Cannot kill container: 8f5c9eecc9aa: Container 8f5c9eecc9aad1d402257908bb61ee07c2b0ba8b3a436a3ff3049e337e14a045 is not running
Error response from daemon: Cannot kill container: a2f718c644ef: Container a2f718c644ef16eed662a779e04d8f61bb8ce92bbee2f7cbfc3e2492108ecf08 is not running
Error response from daemon: Cannot kill container: 588635b671d2: Container 588635b671d21a2b8aa44988e7eab2f19d0b238cb790e3aa96d3a569bd752bb1 is not running
Error response from daemon: Cannot kill container: 27a014aa8786: Container 27a014aa8786fdc91fc2f93cb4dbf1ef2e497fcd391a3201389fbac57fbc611e is not running
Error response from daemon: Cannot kill container: 0500186040e2: Container 0500186040e22cd391573ac5327ef8105cda62b008d3e9782d7d6026a394aefb is not running
Error response from daemon: Cannot kill container: 489495f947fb: Container 489495f947fb878ceddfbda60be5c3a833ecb24962a96df81f2b9e5302121c9c is not running
Error response from daemon: Cannot kill container: 9198fb56e5e7: Container 9198fb56e5e78cc195201e6884abbb90b51209e34c7ae7d24387fdbab1366232 is not running
Error response from daemon: Cannot kill container: e98dbab38550: Container e98dbab385505b80b504991ef7727c514212a38be8a4a3ad1c8d8c672e5ce42a is not running
Error response from daemon: Cannot kill container: ca0da834cf96: Container ca0da834cf96b1009401625a32c6afb2f5c98cd7040d2a777cab41b737b492ca is not running
Error response from daemon: Cannot kill container: 56bfb745ba94: Container 56bfb745ba9454482df35fdb98cc2addab3fe8b5615c3c1256a967780c8713e3 is not running
Error response from daemon: Cannot kill container: 21f6b68cba1c: Container 21f6b68cba1ccd6793b726dd22fa10ed3e403f1ed318b0854809aabdf1d6bc1f is not running
Error response from daemon: Cannot kill container: a48e3eb3e87c: Container a48e3eb3e87ce1d85a140321bde3cdf6e32b5ea0b6d9d61a597e27fd35837180 is not running