GUI acceptance tests using environment deployed from packages.

Build: #2008 failed

Job: Transfers directories was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
13 minutes
Revision
0ab5f662c3ea6d31c3ccedd9a5babeeb1a2cc8bc
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  44740      0 --:--:-- --:--:-- --:--:-- 44740
Error response from daemon: Cannot kill container: 28bcc9fab43a: Container 28bcc9fab43afe38f66a209675581fc00fd4b4c754c4b75f4692e044c1dc2e81 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  40815      0 --:--:-- --:--:-- --:--:-- 40815
Error from server (NotFound): pods "dev-oneprovider-paris-0" not found
Error response from daemon: Cannot kill container: 1144d701e7a6: Container 1144d701e7a6a89944f5d497bf628057c386d009803f06c960d2375480f04b13 is not running
Error response from daemon: Cannot kill container: 6d47f9a4a43c: Container 6d47f9a4a43cda95ebe7b9e95dbf7c217382fb203b5c926286be02d90e6ab4ee is not running
Error response from daemon: Cannot kill container: 425ac2d98f9e: Container 425ac2d98f9e3cb2678eb22047e5aab4466d7a4add46933551e319ec66e243d3 is not running
Error response from daemon: Cannot kill container: 08de8bca6996: Container 08de8bca69967256644b71785e4b9bd775530aff3c22b603b9feadfbede6e572 is not running
Error response from daemon: Cannot kill container: 854981c950a5: Container 854981c950a5b089286d8575a85dba07f582aee76442bc445d72b1283414c8f9 is not running
Error response from daemon: Cannot kill container: 9c037ad0bdc4: Container 9c037ad0bdc449553745707d7e9f550797e132ef0b2e0df51666b3c88bc10360 is not running
Error response from daemon: Cannot kill container: fe6dd48ee59b: Container fe6dd48ee59b7f9d5058cc783c13c392c9d88afc243b9905300cb1468f9e3c59 is not running
Error response from daemon: Cannot kill container: 32ab621416f4: Container 32ab621416f420dc6feee69ab01d48042d22ddedfe8cc0739686f89a56a15ccc is not running
Error response from daemon: Cannot kill container: 1a1f184b2384: Container 1a1f184b238486c023c04f0d22ac48fd16fc633b3a42490e38e7de07eb6d556b is not running
Error response from daemon: Cannot kill container: 1fafac494c6f: Container 1fafac494c6f3e0708dc01c2b6469a3cdfaade0f12782d186a10cee33fea33ba is not running
Error response from daemon: Cannot kill container: 8fe26de9a757: Container 8fe26de9a7573df7485d20828a6444e86bcfd9a9ec47f5b1c919c518c335b5f0 is not running
Error response from daemon: Cannot kill container: dd8d5aafe467: Container dd8d5aafe467b9f98de47d8fab000104060c81ee0d8bae5a37a7e5a13f0961ec is not running
Error response from daemon: Cannot kill container: 188aeb67c0b9: Container 188aeb67c0b9ed07134e58c3350e99fc53e209891d2c536eb9862aea4050bd82 is not running
Error response from daemon: Cannot kill container: 8664a73fcd5e: Container 8664a73fcd5ef2953ae3b43de5aa63c69a878d0ab7296545efb05b0c2ef13e74 is not running
Error response from daemon: Cannot kill container: c6682b2cfd9f: Container c6682b2cfd9fbb1120775849dc384f7927bcc257f0306c6280dae7b65d3b1b82 is not running
Error response from daemon: Cannot kill container: 80ecf13b46b7: Container 80ecf13b46b75f21f1be7db5dec7f37c5409241a8f63049e41f7bf10c34eac55 is not running
Error response from daemon: Cannot kill container: cc8374c7170d: Container cc8374c7170d9426852734d2c254193eca88ecd44edd08dd42e625ce232cabf8 is not running
Error response from daemon: Cannot kill container: 8655fa646766: Container 8655fa64676663c864601e17adba58bc5648637b86d1de0b3287b1645b4f544b is not running
Error response from daemon: Cannot kill container: 4dc22eaa4534: Container 4dc22eaa4534b89373b1c0236884ce1e0a10f3d81cc14f886925f10783cfc941 is not running