GUI acceptance tests using environment deployed from packages.

Build: #2121 was successful

Job: Transfers files was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
20 minutes
Revision
531283e2b89b3833269b775ff1b3609165404e1a
Total tests
5
Successful since
#2028 ()

Tests

  • 5 tests in total
  • 2 tests were quarantined / skipped
  • 19 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  43896      0 --:--:-- --:--:-- --:--:-- 43896
Error response from daemon: Cannot kill container: 06a839a615c0: Container 06a839a615c05a5587ed12bbb952581cdc60a7f15d7b26dfe6f8cb9f90eb0a4f 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-CTF/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CTF/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CTF/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CTF/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CTF/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CTF/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-CTF/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-CTF/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-CTF/onedata/onezone_swagger/bamboos'...
error: failed to create clusterrolebinding: clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
Unable to find image 'onedata/acceptance_gui:v8' locally
v8: Pulling from onedata/acceptance_gui
a1298f4ce990: Already exists
04a3282d9c4b: Already exists
9b0d3db6dc03: Already exists
8269c605f3f1: Already exists
c810ae7364ef: Already exists
78d356e6ec21: Already exists
792b20546d07: Already exists
c1d3130a77b3: Already exists
0c7ad6b015da: Already exists
114ec36e4007: Already exists
2bc588dde0c7: Already exists
89641d7ca7e2: Already exists
b6cd4b44aa19: Already exists
e1c77802a505: Already exists
f373aa611054: Already exists
Digest: sha256:97e4de524ef380ad8c07bf6c71280c378a5e0179834942ff0e6c0007d32b148c
Status: Downloaded newer image for onedata/acceptance_gui:v8
Error: could not find tiller
error: failed to create clusterrolebinding: clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
Defaulted container "oneprovider" out of: oneprovider, onezone-registration-token (init)
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
Defaulted container "oneprovider" out of: oneprovider, onezone-registration-token (init)
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
Defaulted container "oneprovider" out of: oneprovider, onezone-registration-token (init)
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
Defaulted container "oneprovider" out of: oneprovider, onezone-registration-token (init)
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
Defaulted container "oneprovider" out of: oneprovider, onezone-registration-token (init)
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
Defaulted container "oneprovider" out of: oneprovider, onezone-registration-token (init)
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
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  19800      0 --:--:-- --:--:-- --:--:-- 19800
Error from server (NotFound): pods "dev-oneprovider-paris-0" not found
Error response from daemon: Cannot kill container: b1313c31ce9f: Container b1313c31ce9f608ce31482ce881dfecd615d5fd12261a37c3c71e411d107e0a7 is not running
Error response from daemon: Cannot kill container: 1f3dc63a0492: Container 1f3dc63a0492348084de6b0c9863ec917f6d5e047aca93a5efb9c6017e374e7d is not running
Error response from daemon: Cannot kill container: 9754ddf974ee: Container 9754ddf974ee490bbf314d5189e08d494a0d2aa88224dff9216677084e148229 is not running
Error response from daemon: Cannot kill container: 0ef3c00c5ea0: Container 0ef3c00c5ea05aae6178be005cddf94038e7d5d9dd20dd359f1fcfcd2fad8b1d is not running
Error response from daemon: Cannot kill container: 2520eacb4184: Container 2520eacb41841857517862e2b3149160f426a17ceb708d91d0d42383212d8193 is not running
Error response from daemon: Cannot kill container: a0142355d75b: Container a0142355d75b24787abd2ca57998e553a94c9ba6d2feeff49d1b469ff7fc4000 is not running
Error response from daemon: Cannot kill container: 1b66b8b56cd0: Container 1b66b8b56cd02a405960bb54fcd1d56f755258d1448f7934ffd5cd25ea704a9d is not running
Error response from daemon: Cannot kill container: 3664d1f91977: Container 3664d1f91977c06297deb54fff3033da7b5f2e04c58c0f6077443e81e66ac1ce is not running
Error response from daemon: Cannot kill container: f50e814f8a2b: Container f50e814f8a2bcb0120d588076f8081950b5edc3ab3121dda43217e9e3c209a45 is not running
Error response from daemon: Cannot kill container: be384a195f1c: Container be384a195f1cbb564e680e85a9146600de29e5aef115a9144e4ba76086c14c47 is not running
Error response from daemon: Cannot kill container: 85a16eb8e175: Container 85a16eb8e17541ba97b93d8f72850f16464514a684e61d360064db652412156a is not running
Error response from daemon: Cannot kill container: 97d7806e2cd4: Container 97d7806e2cd4433f232a6850c8404f38530bc68ada62d83eddfe6ed9fec50463 is not running
Error response from daemon: Cannot kill container: 6685df9f6550: Container 6685df9f65508a34ed90ad62a9f712a0ea8043aeaf37a7f0810173afcaf28b51 is not running
Error response from daemon: Cannot kill container: 7f5fd46dadf4: Container 7f5fd46dadf452bb4f487a1adb207d93512b60e9117260a913cf476d2a1cf594 is not running
Error response from daemon: Cannot kill container: e9ca85a84374: Container e9ca85a84374a956fc037ff0fd1aa0c84bedd7af02a1547715d8f59ce9f5da1f is not running
Error response from daemon: Cannot kill container: 6a28b5c1b372: Container 6a28b5c1b3726bacaf5105a548a2da87ee49043fcaedad63999a0110a97bfd52 is not running
Error response from daemon: Cannot kill container: 79ee6766fba8: Container 79ee6766fba804086deb00e2352952fe2595e7a96b21cf8d8755bd7da9074338 is not running
Error response from daemon: Cannot kill container: 68a8179a344f: Container 68a8179a344f4bfacb81f00d946215c78ad07328557a7a6f1da3c6a42c4c936e is not running
Error response from daemon: Cannot kill container: b9101e21f3a7: Container b9101e21f3a731c0c3429211a8d85bbd626bad3cea6d026d1f5c5ddbbaac1fd4 is not running