GUI acceptance tests using environment deployed from packages.

Build: #2273 failed

Job: Oneprovider ACL files was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
12 minutes
Revision
624ddd1dfa241fb01c10e610d5a920a26351648e
Total tests
8
Successful since
#2262 ()

Tests

  • 8 tests in total
  • 11 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  48468      0 --:--:-- --:--:-- --:--:-- 48468
Error response from daemon: Cannot kill container: e51baf96311e: Container e51baf96311ef17222bcfc08a71ea962cca9f7061280795b7690947f854919d5 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-COAF/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAF/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAF/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAF/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAF/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAF/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-COAF/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-COAF/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-COAF/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]
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:55:30.204166     446 warnings.go:70] policy/v1beta1 PodDisruptionBudget is deprecated in v1.21+, unavailable in v1.25+; use policy/v1 PodDisruptionBudget
cp: cannot stat 'onedata/one_env/sources_info.yaml': No such file or directory
  % 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 --:--:-- --:--:-- --:--:-- 46069
Error response from daemon: Cannot kill container: b1cfcb7f3af3: Container b1cfcb7f3af38704e7e791c819a4072a4049921ec2df8cd382c3e09b50458078 is not running
Error response from daemon: Cannot kill container: ede743143d5e: Container ede743143d5e6712636290def8018c0a2c800d5e48c01bf70293888760ae227a is not running
Error response from daemon: Cannot kill container: 48876531ba1c: Container 48876531ba1c9b4eb89ff6997bebdd153838cb00be8a643af708073285e289bd is not running
Error response from daemon: Cannot kill container: b16799accdcb: Container b16799accdcb371ca9c176458d64bc0c4cbbc700a50969fe638dedee881e08de is not running
Error response from daemon: Cannot kill container: 0b40e74ca2ce: Container 0b40e74ca2ce8bbecd3b68342718b742226c386dfed032e18cdc08d0f912945f is not running
Error response from daemon: Cannot kill container: 31dc66e85a41: Container 31dc66e85a41be5182eed212fb093ec730aaab87af63576aa29e5e087d1313b7 is not running
Error response from daemon: Cannot kill container: 4788b4a2e979: Container 4788b4a2e979046b1c0cf0003edb82745e6093167bdf01424e3c3b707d57b8cc is not running
Error response from daemon: Cannot kill container: e0a69addccb9: Container e0a69addccb9f4295454434e4cda8e419975ba9a617ba4556fdd23a1c0336789 is not running
Error response from daemon: Cannot kill container: 5864e4ea716b: Container 5864e4ea716bfa64829ea3bac8e767a4740a3c65c6d23bf8fee937a74a5a8a34 is not running
Error response from daemon: Cannot kill container: 79a0c4f78263: Container 79a0c4f782637cfefa8bd495640642e6053e6dacd9510dc12bba12fe1b8529ff is not running
Error response from daemon: Cannot kill container: b840396fdb77: Container b840396fdb77da10537f696cfcab02a619c515ed2dff7e16c53c11dabe1258f5 is not running
Error response from daemon: Cannot kill container: 05f3eccf7acf: Container 05f3eccf7acff0e0fa50a2dfff62fe005270f98ee5ebe6587a02ddb2c21bc931 is not running
Error response from daemon: Cannot kill container: 84a42d329e49: Container 84a42d329e496c0a5b489ae3303e3fceb1a5b49af638537291e7558b3baf736a is not running
Error response from daemon: Cannot kill container: 66a8a4077eec: Container 66a8a4077eec5cb63508815afe3a0e0be4abbf324ae16f0a790c50ec39d2ce49 is not running
Error response from daemon: Cannot kill container: b0d30d2dcf29: Container b0d30d2dcf29035bc6231bbb6d72b138b3bb42f7dd977890b805fc17b16123ee is not running
Error response from daemon: Cannot kill container: eeddb38469c3: Container eeddb38469c34a5e0c8c43172903cc43dd73ca65f40448707cd46fe4273ad9ec is not running