GUI acceptance tests using environment deployed from packages.

Build: #2220 was successful

Job: Oneprovider datasets privileges was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
17 minutes
Revision
d2e32964f241bbfb4f020c187db4a4d5b66536a1
Total tests
11
Successful since
#2201 ()

Tests

  • 11 tests in total
  • 16 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: f82b26cf2510: Container f82b26cf2510c788f2e7dbd471abf15ae3c4a7fc9598fb5c4c8ccf4e9826aeca 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-CODP/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODP/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODP/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODP/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODP/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODP/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-CODP/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-CODP/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-CODP/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]
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
W0712 10:46:05.191748     458 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
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  4653  100  4653    0     0  40460      0 --:--:-- --:--:-- --:--:-- 40460
Error from server (NotFound): pods "dev-elasticsearch-0" not found
Error response from daemon: Cannot kill container: 026c62c2c737: Container 026c62c2c73734321fb87f3db6330a26ca2ebed49143699ea74abf228bf9d22d is not running
Error response from daemon: Cannot kill container: 5f35ece14a92: Container 5f35ece14a926a75af7c702e49c408553e5bb5ebad3d2c6f8c3598ebbe3a9d61 is not running
Error response from daemon: Cannot kill container: 2787ee93b644: Container 2787ee93b64415d22397de4c54fade7f58c49a7ffe38f9b5db1a3f9360fab3d9 is not running
Error response from daemon: Cannot kill container: b0ca297e1e59: Container b0ca297e1e595313bc6ec91a575f06d9f98874e5d6b77e4eef2a4c20fc1dcb10 is not running
Error response from daemon: Cannot kill container: e89c737ae16a: Container e89c737ae16a08343935de1ffc440d78bc6bf7ffcbb9bdf6f6a242041164640a is not running
Error response from daemon: Cannot kill container: c48e353481e4: Container c48e353481e43dceef8308583824a29b70b7d1d53ae3cfc63a66295358d4d014 is not running
Error response from daemon: Cannot kill container: 255da412894a: Container 255da412894a6771728dbf202344a9a7820432886f6c48d72ea5d7457804143b is not running
Error response from daemon: Cannot kill container: f5e3f91ccbea: Container f5e3f91ccbead165bc99302079843d86e618ee162a606305bcfe531b96931de7 is not running
Error response from daemon: Cannot kill container: 6492cbbdf9fd: Container 6492cbbdf9fda9b6acd8e33c970880dcc09995b5708ec13c02584c1ee6997900 is not running
Error response from daemon: Cannot kill container: 2fe616394de1: Container 2fe616394de12528484b31fbd11fdc8725258247a7bb5427a38b8a9d533230d3 is not running
Error response from daemon: Cannot kill container: dd5c3f9a9266: Container dd5c3f9a9266156b4f3004dc60048c53c439131f4b4341f432c85fed9ad8a0d5 is not running
Error response from daemon: Cannot kill container: 90857262c722: Container 90857262c722b5c208419dabf439afe93210f0ca49d9725407ddbd9d2d74f4d2 is not running
Error response from daemon: Cannot kill container: 29bb9d72484c: Container 29bb9d72484c1e45cae5e88d0c86b2346221c9c4305404a7d1f5785dbe0fe622 is not running
Error response from daemon: Cannot kill container: efc9ca6155be: Container efc9ca6155be6746283826ac340ffa3448e500aab62a91c141e565a4e872ae61 is not running
Error response from daemon: Cannot kill container: 96063dca1a81: Container 96063dca1a8163437bc990819a35e4b2b4e5c3f3ed65363f6f6df73a489878fd is not running
Error response from daemon: Cannot kill container: ffd62db917b7: Container ffd62db917b7058101849ed842f2a0bb324e0eed192f7658415740ac5c60f184 is not running