GUI acceptance tests using environment deployed from packages.

Build: #2075 was successful

Job: Oneprovider datasets was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
21 minutes
Revision
d5330e48531ab5bfbefefb1e446da4fe7cede649
Total tests
18
Successful since
#1943 ()

Tests

  • 18 tests in total
  • 20 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
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  4653  100  4653    0     0  41176      0 --:--:-- --:--:-- --:--:-- 40815
Error response from daemon: Cannot kill container: fcda0593a556: Container fcda0593a5566b159dc8d8f06d5bf035dd6c43a68b08a00a10899943da6d10a8 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-CODT/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODT/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODT/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODT/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODT/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODT/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-CODT/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-CODT/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-CODT/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
W0404 21:12:53.550659     443 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  38775      0 --:--:-- --:--:-- --:--:-- 38775
Error from server (NotFound): pods "dev-oneprovider-krakow-0" not found
Error response from daemon: Cannot kill container: 1d4c8e76234b: Container 1d4c8e76234ba4e08a3596a74da13572e15b9b13b7d9e66ade2f3f665d8bed3f is not running
Error response from daemon: Cannot kill container: 8585cdfc5493: Container 8585cdfc5493f87264f990403cc96fb9cd6796cf0c2c9dcbe2a1dcf07e3c5c54 is not running
Error response from daemon: Cannot kill container: 2bbbeb896d34: Container 2bbbeb896d347684e9687186997798636ec06bc98c0eedeaa0bc859c0c3bf6b8 is not running
Error response from daemon: Cannot kill container: 0f03c6363c88: Container 0f03c6363c886128bc57b434bcb4c725ff161653e9d5cc91b19492b1acf552b0 is not running
Error response from daemon: Cannot kill container: 241bef8117c8: Container 241bef8117c83b2907f1526fee0753611fee5f6567970c2ee63ee1092142d8c0 is not running
Error response from daemon: Cannot kill container: a3ee5a8e0196: Container a3ee5a8e01967fef14fd58eaed1cfb16df995af40b29af90ffbd829954a7f873 is not running
Error response from daemon: Cannot kill container: 6f278b4719ff: Container 6f278b4719ff0308bf7bd7cb03247289171d9dfb2f66b7b389e758e724acc8f3 is not running
Error response from daemon: Cannot kill container: 36e9ac1d5d43: Container 36e9ac1d5d43fe4e84860f7bd148cef217bcafdcc1047ba20da5f27064d7f09e is not running
Error response from daemon: Cannot kill container: ab834e64cb9c: Container ab834e64cb9ccd33fa8e76be531cfdfefb97845ebcd3282a3940821da58679a0 is not running
Error response from daemon: Cannot kill container: 07e7c0ba5c8a: Container 07e7c0ba5c8a574899a8404e474d1824f1c41191ec8fd0ede0920e2c90619349 is not running
Error response from daemon: Cannot kill container: b84e6ed29a6b: Container b84e6ed29a6b1d447f4cdcb8973ec8dee46c9c5bb557696c1d01371fb43d92cd is not running
Error response from daemon: Cannot kill container: da07475717c3: Container da07475717c32f61d95be49d0b1f810c6b4864642f60edb3070e766a61ce7c92 is not running
Error response from daemon: Cannot kill container: fde717a74c2e: Container fde717a74c2e81150a05d8cd7f6aff15dd8c42c181a71378a0c71598bf9bb50c is not running
Error response from daemon: Cannot kill container: 61f1ce3ca60f: Container 61f1ce3ca60f68ad97eb67baa6db5c9a0cff54d50a03949e4d567a70f5f70160 is not running
Error response from daemon: Cannot kill container: 5939f6a41a36: Container 5939f6a41a361a9234b59515fd9e810129327a7bdc9b418096c2ecca558171a9 is not running
Error response from daemon: Cannot kill container: bd0182cb13cd: Container bd0182cb13cd450c52e67acf2e5c62fef7d783bdf35a300e20930bf0d29798d0 is not running