GUI acceptance tests using environment deployed from packages.

Build: #2022 failed

Job: Transfers directories was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
14 minutes
Revision
10ddb4213486b44781d6de3e618016ef93cedab5
Total tests
5
Successful since
#1990 ()

Tests

  • 5 tests in total
  • 13 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  43083      0 --:--:-- --:--:-- --:--:-- 43083
Error response from daemon: Cannot kill container: 400ae42746dd: Container 400ae42746ddd875f1a48a11c44affba5578d6e4453caaf565fc72307c11ecf0 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-CTD/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CTD/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CTD/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CTD/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CTD/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CTD/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-CTD/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-CTD/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-CTD/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  49500      0 --:--:-- --:--:-- --:--:-- 49500
Error from server (NotFound): pods "dev-oneprovider-paris-0" not found
Error response from daemon: Cannot kill container: 3207667d23fd: Container 3207667d23fdaedf67751b154ea2482dfd6fdee3a77c1dda22a4685a5a13df66 is not running
Error response from daemon: Cannot kill container: bb8e68c529c7: Container bb8e68c529c7adec545cadc7e2663e72ae4ec182946708992396ec7fbd13a796 is not running
Error response from daemon: Cannot kill container: 4c3e4c7cf93f: Container 4c3e4c7cf93f4aa2f751e45396b932dddbf0368bd515c32208f549d7478ed679 is not running
Error response from daemon: Cannot kill container: fb780070339a: Container fb780070339a1bcadbcaa6e705ee223879960bf408a6ac3e5d28315d2e1f42c1 is not running
Error response from daemon: Cannot kill container: 510490667b77: Container 510490667b77557f2830f90b3bc457339eb8455dd0e99bec5fff202fed892e32 is not running
Error response from daemon: Cannot kill container: 8f5487ab34f4: Container 8f5487ab34f4ec663b56569acf0395fa7aeb09d7939666e99389cfa5941d2fcc is not running
Error response from daemon: Cannot kill container: 2184a706a2ac: Container 2184a706a2ac7b006eecdedec8b7e2987671236cd64edc20f2d7b3037b18285c is not running
Error response from daemon: Cannot kill container: 8fe2c980b943: Container 8fe2c980b94388056fa297ff7f2e52360b03425a47af9cac93fe530d32ebac83 is not running
Error response from daemon: Cannot kill container: 5a3b9bc63e46: Container 5a3b9bc63e46adff29aa85cf62f74cab1f0f84544719278435a0f8556f813918 is not running
Error response from daemon: Cannot kill container: 94291d6f4384: Container 94291d6f438489bd6243cf0fe9ebdcbc330dc7720b1a0c298354ff4eeed62bb6 is not running
Error response from daemon: Cannot kill container: bd020cadea67: Container bd020cadea6774f876b409eaed2b48de4523ee2ca3db29030f84f0174d6e1d0a is not running
Error response from daemon: Cannot kill container: 1215412ef36b: Container 1215412ef36b33b982f472830b4815913d399d418d7f358e4d212e2b4f6cf650 is not running
Error response from daemon: Cannot kill container: c705811dd43c: Container c705811dd43c054790487b643ea55251234f1a1be758e9d6086db9f160a40dfa is not running
Error response from daemon: Cannot kill container: 28d1a4a42d34: Container 28d1a4a42d34c2a77dad00b0c6ef5bb1bd0e68b78dcf05d5ccc60b59a5a38f54 is not running
Error response from daemon: Cannot kill container: be5b15effeee: Container be5b15effeeecb56983c31aaedc4930246080ee42050f348d835a70670e3d82e is not running
Error response from daemon: Cannot kill container: 259fabd49ea8: Container 259fabd49ea878dfbeb8a084502c05bb33c8038d0c91830d756c43c8e8e32d3d is not running
Error response from daemon: Cannot kill container: 52b359430284: Container 52b3594302848c89a850e23286dc7d71e02c1ed3cded25f7d71b947438217bcf is not running
Error response from daemon: Cannot kill container: 61f52f2d76dc: Container 61f52f2d76dcbac19f097463cf5ae9840d1edcc840f030d36198a630c14f394f is not running
Error response from daemon: Cannot kill container: 77618680f269: Container 77618680f269ef109ea5c4bfe6674a35308e4ecc12aa8c4e4dc23a46ceed432f is not running