GUI acceptance tests using environment deployed from packages.

Build: #2303 failed

Job: Onezone tokens delete was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
25 minutes
Revision
7d15704b4b14f8c1de0ec72a1c9b7b6437cbb31a
Total tests
10
Successful since
#2283 ()

Tests

  • 10 tests in total
  • 23 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  32089      0 --:--:-- --:--:-- --:--:-- 32089
Error response from daemon: Cannot kill container: f3a529661fbe: Container f3a529661fbe238f122532f42035d7d78b4a3a3aaa3558f3f17990df4c22732e 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-COTD/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COTD/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COTD/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COTD/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COTD/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COTD/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-COTD/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-COTD/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-COTD/onedata/onezone_swagger/bamboos'...
error: failed to create clusterrolebinding: clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
/usr/local/lib/python3.8/dist-packages/pytest_selenium/drivers/crossbrowsertesting.py:72: SyntaxWarning: "is not" with a literal. Did you mean "!="?
  if report.when == 'setup' or info.get('test_score') is not 'fail':
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]
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
W0908 20:42:25.241997     507 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  45174      0 --:--:-- --:--:-- --:--:-- 45174
Error response from daemon: Cannot kill container: 594a2c10277c: Container 594a2c10277cb0ca6acab4b8a53928634ea54780505852aca759816aa6248873 is not running
Error response from daemon: Cannot kill container: cc5cb76417fe: Container cc5cb76417fea7d8664561f3d2728170ea133ca3cf88918b634d414a24ab73a7 is not running
Error response from daemon: Cannot kill container: 849700b5f3b7: Container 849700b5f3b7d5a6f53c55ee4665600094ebbfa3331e5821c3381cf5a20189a0 is not running
Error response from daemon: Cannot kill container: 1e5b75990939: Container 1e5b75990939559556e5ba839da32508876e8812da7305009ecdf38348788c5b is not running
Error response from daemon: Cannot kill container: c9ea58acd80f: Container c9ea58acd80f9601dfc772a1eef279e993b926626ca7c2607905b667a1183aff is not running
Error response from daemon: Cannot kill container: 6ab0da3b0e13: Container 6ab0da3b0e137a8c1fb12d92513ec46b3659852dd1344b337a012e65c635f274 is not running
Error response from daemon: Cannot kill container: 8d63f2f05168: Container 8d63f2f0516871d36b10945a7556091de40faa09a29c58c67c08ffd9cdb74989 is not running
Error response from daemon: Cannot kill container: dac956eb7562: Container dac956eb7562e218e078a3fa06adbaeb01f76d50d98e5ef6a33154a24c924838 is not running
Error response from daemon: Cannot kill container: a6a76bfa48b6: Container a6a76bfa48b62f3c0ba6e45e5962ee9cba21349aeaa6e15b45f44655a108d51f is not running
Error response from daemon: Cannot kill container: 5f377be27ce5: Container 5f377be27ce503d83e47dada61ab7e79caef40f74d8626ae38c76e678124143d is not running
Error response from daemon: Cannot kill container: 026784064ef7: Container 026784064ef7519e5acf14e123bbe12952e2e24bfe85a8feddd017591b757d9e is not running
Error response from daemon: Cannot kill container: 7b8e3b71d908: Container 7b8e3b71d9085ca1c50100c3422eb941944e767830e6a6a8b6c9ad53ca5fe9c1 is not running
Error response from daemon: Cannot kill container: b0b117d937aa: Container b0b117d937aa6854a31aa94805e5ed35fbc067f9eaba6eb984651b1d97ef78c8 is not running
Error response from daemon: Cannot kill container: bc3829a7cb3f: Container bc3829a7cb3fb55dfa99030bcadb275490624e112430563ebef376af2256ee50 is not running
Error response from daemon: Cannot kill container: e49882585eb2: Container e49882585eb2cc340ff981906e7c8c40527c1c833b66670cb6bdcbf3ef194369 is not running
Error response from daemon: Cannot kill container: 4be1005d3bfb: Container 4be1005d3bfb6fdb0295bdb3fa394d91dcb5f7b022bf827df8b686a309f5258b is not running
Error response from daemon: Cannot kill container: 714732a03e68: Container 714732a03e68d4636e2d1c07bb29ebc683615ec0ea66c45c0fcc6bdd938e3d84 is not running
Error response from daemon: Cannot kill container: 75109737c658: Container 75109737c658347f70e6f88676fbfc2f658d32d1081044822f43a2882d6c6b63 is not running
Error response from daemon: Cannot kill container: 8d3d755e11cd: Container 8d3d755e11cd38f78d0a09ef5555d263e5c121f4fbd9cc3cf8479fa7a6d56366 is not running
Error response from daemon: Cannot kill container: 9eac88d38086: Container 9eac88d380869d1ee022bb6322507272242439fdb457b1af47c71e2abaf04ea3 is not running