GUI acceptance tests using environment deployed from packages.

Build: #2010 was successful

Job: Transfers directories was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
14 minutes
Revision
ed4f134a7d934cf4803abda141850366f8511cb2
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  49500      0 --:--:-- --:--:-- --:--:-- 49500
Error response from daemon: Cannot kill container: 9d6e24151e57: Container 9d6e24151e570a342e79ebd90112f9bb177de5cf44794e51ec157014129b1457 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  44740      0 --:--:-- --:--:-- --:--:-- 45174
Error from server (NotFound): pods "dev-oneprovider-paris-0" not found
Error response from daemon: Cannot kill container: b3de40dee629: Container b3de40dee62907c2b45c8a23185121481db24ffc4946c66b894664aebe1ec079 is not running
Error response from daemon: Cannot kill container: 6112e5c9e6f1: Container 6112e5c9e6f15dcce018e5984daae2214fced1eab7efd44349fd2ee46400b745 is not running
Error response from daemon: Cannot kill container: ac8c7b6f65bb: Container ac8c7b6f65bbb7f4fc1a203f01c78c2b73d49d0fcc884084cf41fd1b09ff849d is not running
Error response from daemon: Cannot kill container: 74c50b62225e: Container 74c50b62225ea09e33166648f9252f85f0463be6739f92d33132faeeef91de5f is not running
Error response from daemon: Cannot kill container: 51b0fff0cc34: Container 51b0fff0cc34afa1612cca227538c326d3ae94dd1a3ed32028a194ec2b8df423 is not running
Error response from daemon: Cannot kill container: d73c28aee295: Container d73c28aee295b8abd4445e2067b9b0fb261fd52d9e7e61d95fdd5610e16dd9ba is not running
Error response from daemon: Cannot kill container: e0a8be9fddb9: Container e0a8be9fddb967abe49907a72fa2f246a8bd05ec127b5389b84c1bfd729c18cf is not running
Error response from daemon: Cannot kill container: 674d7805de71: Container 674d7805de71e92f621aab6fe7453d176f6b2873e0d91ca50f7269ca5b09c4b8 is not running
Error response from daemon: Cannot kill container: d2e246c0717b: Container d2e246c0717b3e5d9a17e99959a1603a7b143c035bb51680392567519d3a0363 is not running
Error response from daemon: Cannot kill container: be6237761427: Container be6237761427d11c49f12d40f99fd3b6b251d33c9054437f85af942285d44db2 is not running
Error response from daemon: Cannot kill container: f5478cf888dd: Container f5478cf888dd5e85d40a058a3d6d56cc6d3e2fd3e80cf869740104ebbed9eec6 is not running
Error response from daemon: Cannot kill container: f4573ad5a6d8: Container f4573ad5a6d8e0fa793a3494aeec2b867bff8c958f9f56946f926fc9c6735082 is not running
Error response from daemon: Cannot kill container: 5ccea751e6e9: Container 5ccea751e6e9548c3476245d8aeed601bbf124bcf9ac4ec97be6f107f352c769 is not running
Error response from daemon: Cannot kill container: 971b226d0713: Container 971b226d071382f91ad7e1bdf391513f415e408263ae0182c6ea24f57fef482a is not running
Error response from daemon: Cannot kill container: adc055131246: Container adc0551312467361b50727fe51ebde07f27ef359d0db8c9b8141d38c7034d3ed is not running
Error response from daemon: Cannot kill container: ea28ea0a2b9b: Container ea28ea0a2b9b14e2b6c1b29bca8edb4a9791352ce3bb3da157cb45294c2b6605 is not running
Error response from daemon: Cannot kill container: c9aed8517756: Container c9aed85177567efaf9bba4163ae38cf1ad4da9fb5980044bad932262556d9849 is not running
Error response from daemon: Cannot kill container: 2a90cf37603f: Container 2a90cf37603f99720f31b6007298c37218eb0133e1e5f2ccc05969e100938ff9 is not running
Error response from daemon: Cannot kill container: 610e25e6cfd4: Container 610e25e6cfd4a49f0d3e4200b7ed36f81d6eb5a2bafe56cf80ddb14c3daef880 is not running