GUI acceptance tests using environment deployed from packages.

Build: #2146 was successful

Job: Oneprovider ACL subdirectories was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
21 minutes
Revision
55cdb7fe92fff892fdb8cf16f00c4ce6627a4c4a
Total tests
12
Successful since
#1943 ()

Tests

  • 12 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  19550      0 --:--:-- --:--:-- --:--:-- 19550
Error response from daemon: Cannot kill container: 4bfc5920d0cb: Container 4bfc5920d0cb60fc5ab8bf99f0ced58e3a7925a18b798c1065d213510da7cce4 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-COAS/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAS/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAS/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAS/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAS/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAS/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-COAS/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-COAS/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-COAS/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
W0524 08:48:02.465289     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  44740      0 --:--:-- --:--:-- --:--:-- 44740
Error response from daemon: Cannot kill container: b018a0b1f59f: Container b018a0b1f59f1934fd2e030612915b8c340d852c5c22c36f7a112b9bbac7fe75 is not running
Error response from daemon: Cannot kill container: 1c5afebd18df: Container 1c5afebd18df20a0dcd53471613563b0dc43f93460157312d343678bcc446457 is not running
Error response from daemon: Cannot kill container: 1d1526c8c17d: Container 1d1526c8c17de90d81f32d168ff9e3e82e4948b70b354d1c5878b58ccb2457bb is not running
Error response from daemon: Cannot kill container: 63ea2fd5586a: Container 63ea2fd5586ad3e5cb4b26d6a249373f2a4817de57b8897a39c46018098fb099 is not running
Error response from daemon: Cannot kill container: 1d1f983eb0a1: Container 1d1f983eb0a122a0c1c8e5bbd58fc6ee2d383b8db6bd3b555ed7f197f13daf4e is not running
Error response from daemon: Cannot kill container: abb7b8397d6f: Container abb7b8397d6f62b1580e35d0bf1c68413af5182f1838e7737f288ac4a5d188f0 is not running
Error response from daemon: Cannot kill container: 31a6b4a5549e: Container 31a6b4a5549e2181b56002396a308cafab44f4edf258ba69778528d4a5143a8d is not running
Error response from daemon: Cannot kill container: 3ce040796183: Container 3ce0407961831cbb376e87bccaf1b6efaa2e9fcedfdee39fe5aeb9a4b833304e is not running
Error response from daemon: Cannot kill container: de3b740ebaf5: Container de3b740ebaf5e0f382ea2b917c71f014b3ff996044baba9d637dee39ab034e6d is not running
Error response from daemon: Cannot kill container: 6e57e79922a3: Container 6e57e79922a3fbf8bbc1357c984e3f8bf1178a6565c23b27dd22c21a691f0c58 is not running
Error response from daemon: Cannot kill container: ad64f7616791: Container ad64f76167916b011831c56ab8eaf377bf59fe7ae1cc16d754bd31338cd986d1 is not running
Error response from daemon: Cannot kill container: fd215d074d50: Container fd215d074d50ec780eea94ff9dc763376eb97addd8eae722ba0008b56ffdf1cf is not running
Error response from daemon: Cannot kill container: 76e6b1bc8a44: Container 76e6b1bc8a4446ff9770d9da42f56698d8cd42daebfc5300b504f19e0c2017d0 is not running
Error response from daemon: Cannot kill container: 300c5979fe74: Container 300c5979fe74c2bbbe3239ab05e46b3d7be2cdd8957b4a285b94fc1bce906414 is not running
Error response from daemon: Cannot kill container: 375005fec651: Container 375005fec6513f5091b32f1d3a5dccf73ddd013988c70e088579182a2773aec9 is not running
Error response from daemon: Cannot kill container: d7b76a6e1875: Container d7b76a6e1875aa56bdb095d5a13a5cbc747490ba8aeac13debc1f4495a0fe769 is not running