GUI acceptance tests using environment deployed from packages.

Build: #2274 was successful

Job: Transfers cancel was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
10 minutes
Revision
624ddd1dfa241fb01c10e610d5a920a26351648e
Total tests
1
Successful since
#2250 ()

Tests

  • 1 test in total
  • 1 test was quarantined / skipped
  • 7 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  37524      0 --:--:-- --:--:-- --:--:-- 37524
Error response from daemon: Cannot kill container: 33f76620f118: Container 33f76620f118eb61c52a854d49cb22ba3efc5392283698e27f4b8becc94e1d8f 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-CTC/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CTC/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CTC/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CTC/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CTC/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CTC/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-CTC/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-CTC/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-CTC/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: could not find tiller
error: failed to create clusterrolebinding: clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
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
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
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
error: failed to create clusterrolebinding: clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
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
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]
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
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  4653  100  4653    0     0  24750      0 --:--:-- --:--:-- --:--:-- 24619
Error response from daemon: Cannot kill container: 19f7ce44df63: Container 19f7ce44df631b0a8f032026dddb9adfa90fc5a3a2337588d9dd3c460757e18d is not running
Error response from daemon: Cannot kill container: a23dfd420030: Container a23dfd420030aacb0d7bd1e6305553d17fd9e9443b0ace6bdf272b6f2e601943 is not running
Error response from daemon: Cannot kill container: 5478ea4e80c1: Container 5478ea4e80c1156d7db810e35593c3a9a70f9135d608c1634aedaa71cbdd4d50 is not running
Error response from daemon: Cannot kill container: c7ca597f6391: Container c7ca597f6391e22aea715cebcbd52a16d13bc27588e993ed84c86695f91c2100 is not running
Error response from daemon: Cannot kill container: 72e015a77911: Container 72e015a77911f5c8444374984ec2f9c4160185507d0e44c2a19e76e6d3730a26 is not running
Error response from daemon: Cannot kill container: 3947a7a99a88: Container 3947a7a99a88c3bd4ddb9d608049bda875bc964bda1d35d338be77ee1dbdddb2 is not running
Error response from daemon: Cannot kill container: 6dd3f5d73caa: Container 6dd3f5d73caaa213354944be49c5cbf4ccef2db101216f3f18fcee740f182808 is not running
Error response from daemon: Cannot kill container: 7959dbdddf01: Container 7959dbdddf0184a0e8457db2106aaf76a3462be70ddcc740da68fdfe01fb3a88 is not running
Error response from daemon: Cannot kill container: c636a9355afd: Container c636a9355afd65c40e19680b4758cfd2c5d37bcc2de13315f35be2bf45bb3069 is not running
Error response from daemon: Cannot kill container: d1051fda3b95: Container d1051fda3b955982da67ba492948d5d27a353bf144675e2cbcaa4c7e393ac591 is not running
Error response from daemon: Cannot kill container: cfdcaf95c620: Container cfdcaf95c620e1ed348267a45aa2c27c2d03f93c88e5ded109623903d3f60a5e is not running
Error response from daemon: Cannot kill container: a8f25513f106: Container a8f25513f106151acb8123e6ddb915801828f438f8344c21ffe80127082430fb is not running
Error response from daemon: Cannot kill container: 40277f37cadc: Container 40277f37cadc2efb60ad49313662345522d546b2fc2fe45e5f644c7af790f0e7 is not running
Error response from daemon: Cannot kill container: 939f84e45b16: Container 939f84e45b160da7a26f730aa9d59a8338ab6e8bb928b2ffc3edc5868a6ad30e is not running
Error response from daemon: Cannot kill container: de5888fc0c2d: Container de5888fc0c2d8a161b8371c38af56705d1cf8387c47200d9706f9003762941e8 is not running
Error response from daemon: Cannot kill container: 52c77cea4144: Container 52c77cea4144d8db7386b1d468c92e7b59864f0a7b426bb710636061d0d4a635 is not running
Error response from daemon: Cannot kill container: e6417e66db26: Container e6417e66db26f5e3c41f097683d3d184bf67361094f78cd80e99b10294ff258c is not running
Error response from daemon: Cannot kill container: 835a6d46f6de: Container 835a6d46f6def28e6e7ce3ee300236c11ffa25a3b1db60b50fc1e5624682075e is not running
Error response from daemon: Cannot kill container: 1eb9a1452438: Container 1eb9a14524388e7b579f9af3985995505a315b8487dea15d2917b323db1a3fb8 is not running