GUI acceptance tests using environment deployed from packages.

Build: #2145 was successful

Job: Oneprovider archives incremental and nested was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
23 minutes
Revision
3f6eba726c9f477b80c64f61e18d18c4a18e4f06
Total tests
8
Successful since
#2108 ()

Tests

  • 8 tests in total
  • 22 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  46069      0 --:--:-- --:--:-- --:--:-- 46069
Error response from daemon: Cannot kill container: 43f37c67f67d: Container 43f37c67f67d47aaa5e049ddd45ac4366d96b03b91fefa94ccc59a11fb2128ec 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-COAIN/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAIN/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAIN/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAIN/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAIN/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAIN/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-COAIN/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-COAIN/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-COAIN/onedata/onezone_swagger/bamboos'...
error: failed to create clusterrolebinding: clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
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
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
W0523 13:05:44.541872     442 warnings.go:70] policy/v1beta1 PodDisruptionBudget is deprecated in v1.21+, unavailable in v1.25+; use policy/v1 PodDisruptionBudget
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  37829      0 --:--:-- --:--:-- --:--:-- 37829
Error response from daemon: Cannot kill container: caa5ba5b8d52: Container caa5ba5b8d52a07cd19786e58c69aaba7f493cb161ac56e7a3beb0ec69e1da61 is not running
Error response from daemon: Cannot kill container: 6445431054dd: Container 6445431054dd5572e4c90b8a7435519f2112e14265f25c13a81caee7f7ce0f5a is not running
Error response from daemon: Cannot kill container: e3b0bf6fb3c7: Container e3b0bf6fb3c7efcd04171d8bed7cf57478ec0d9b0cd90ee84ee99392c7095b8f is not running
Error response from daemon: Cannot kill container: 1b0a976eeec9: Container 1b0a976eeec9abba7761e87eeeb11e0df4206243144fa62844610bc6247d690d is not running
Error response from daemon: Cannot kill container: 83569b282bce: Container 83569b282bce95c969a54a691b2f0b618d58b027d364f780262c305ec56a578c is not running
Error response from daemon: Cannot kill container: 5a7bfcc1e7fe: Container 5a7bfcc1e7fe4d800234d4e5abc9e500b41344d9be924d266d18257035afe737 is not running
Error response from daemon: Cannot kill container: f87fa7273b27: Container f87fa7273b2779124eb4356df2863c4d03aca9887edec106f8ba1a284f5aa29e is not running
Error response from daemon: Cannot kill container: d0554bd622b6: No such container: d0554bd622b6
Error: No such container: d0554bd622b6
Error response from daemon: Cannot kill container: 7849f4101b94: No such container: 7849f4101b94
Error: No such container: 7849f4101b94
Error response from daemon: Cannot kill container: e9361b25a824: No such container: e9361b25a824
Error: No such container: e9361b25a824
Error response from daemon: Cannot kill container: 47790624400c: No such container: 47790624400c
Error: No such container: 47790624400c
Error response from daemon: Cannot kill container: 50fda6c26712: No such container: 50fda6c26712
Error: No such container: 50fda6c26712
Error response from daemon: Cannot kill container: ee0f202ca87f: No such container: ee0f202ca87f
Error: No such container: ee0f202ca87f
Error response from daemon: Cannot kill container: 2db5498641a0: No such container: 2db5498641a0
Error: No such container: 2db5498641a0
Error response from daemon: Cannot kill container: d22a177ec8b9: No such container: d22a177ec8b9
Error: No such container: d22a177ec8b9
Error response from daemon: Cannot kill container: d1e3250e757d: No such container: d1e3250e757d
Error: No such container: d1e3250e757d