GUI acceptance tests using environment deployed from packages.

Build: #2142 failed

Job: Transfers directories was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
13 minutes
Revision
3f6eba726c9f477b80c64f61e18d18c4a18e4f06
Total tests
5
Successful since
#1990 ()

Tests

  • 5 tests in total
  • 12 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  48978      0 --:--:-- --:--:-- --:--:-- 48978
Error response from daemon: Cannot kill container: 51c1e6193d10: Container 51c1e6193d1050eb970fbe7209da620f957d6d00b37a1f74ebb74631a39e8a9e 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  46069      0 --:--:-- --:--:-- --:--:-- 46069
Error from server (NotFound): pods "dev-oneprovider-paris-0" not found
Error response from daemon: Cannot kill container: 1f46b428fc2d: Container 1f46b428fc2d5cfce61c86dc68a057c228f4c8248e6a1d7de123d4c8c3f60041 is not running
Error response from daemon: Cannot kill container: b71338a18716: Container b71338a187162b4b623f8e11f65bde017ee267225aa59844dda49d73b742ecea is not running
Error response from daemon: Cannot kill container: 0cb4d07821ec: Container 0cb4d07821ec670610bd4e91c7840c93d8c2f742fc474c3d88ae092d66b5fc64 is not running
Error response from daemon: Cannot kill container: 75ed65120589: Container 75ed6512058946267ecf67c53c2ded08687094b0a4756f09ccd2ca6c19a5525b is not running
Error response from daemon: Cannot kill container: 693b73bf9e49: Container 693b73bf9e496fdba58e70ce787942fadff5e1cefaef2cbedd13aabbfadeccf3 is not running
Error response from daemon: Cannot kill container: 8876480a895e: Container 8876480a895e257594a554083986eb4de7de6fccbae6c7d880a6a91da807df37 is not running
Error response from daemon: Cannot kill container: e6c4fabe8235: Container e6c4fabe8235a4406e9c676e6bde2b5e2610dec989ea6189adf36e22bd171bf0 is not running
Error response from daemon: Cannot kill container: 936d84a73ee5: Container 936d84a73ee593138e982dd33aab079da0c653e2d8a13ff3bd8964809cf7542d is not running
Error response from daemon: Cannot kill container: e1bc2c70ed9f: Container e1bc2c70ed9f70aed4a7e64ec4bd2bce93946920515a03866d3f4245f19b71ae is not running
Error response from daemon: Cannot kill container: 677ff9dda447: Container 677ff9dda447aed765995721d285b0d3746152c3e4358de29a1c432357426672 is not running
Error response from daemon: Cannot kill container: 878a2e7af9e2: Container 878a2e7af9e2de5006f94a915b4c408eb4adb0220bce2c7805d66f53dc4d14e0 is not running
Error response from daemon: Cannot kill container: 8c99bb70de8a: Container 8c99bb70de8a108ff468c63772ed2962ec904f0a9890e9411c8343c9f5a2a8ec is not running
Error response from daemon: Cannot kill container: bb8753f547de: Container bb8753f547de2b500a648cce925b03f0afcf5ba95627a5d67bde95967b17f814 is not running
Error response from daemon: Cannot kill container: 5c5891bfd08c: Container 5c5891bfd08cbd0b79820fff2c73cecd12c7b46bc2b3f0dd90e7ba74f895aec5 is not running
Error response from daemon: Cannot kill container: aa9c23555e95: Container aa9c23555e95aac28a71cb182c029c8d1810042f13304f16d2b25bb8c4db687a is not running
Error response from daemon: Cannot kill container: df6130736e52: Container df6130736e52356b34351e600d7db04c47f379917d91162ce22f4a2ce11e0910 is not running
Error response from daemon: Cannot kill container: 346ff5c48cb5: Container 346ff5c48cb541869958dd8648840e627d2bd6e804a6c76fb61a57b92dbccaec is not running
Error response from daemon: Cannot kill container: b2022c7d725b: Container b2022c7d725bb4990bbf7815015c1e083d2896dc2a4afcda00a4d39232bd4ee8 is not running
Error response from daemon: Cannot kill container: 587e789a30e2: Container 587e789a30e2c67cd7d3024d0360dffd08af004b056468187397e5c9b43030d0 is not running