GUI acceptance tests using environment deployed from packages.

Build: #2042 was successful

Job: Oneprovider hardlinks was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
21 minutes
Revision
d4a37ebda8d9cad234b655aae75d29294552ebb5
Total tests
11
Successful since
#1968 ()

Tests

  • 11 tests in total
  • 19 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: 6748d2b5a5a6: Container 6748d2b5a5a60f6bae1096c62427136a403ce32b65ff1532a11b7e2f7633ceb3 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-COH/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COH/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COH/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COH/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COH/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COH/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-COH/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-COH/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-COH/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
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
W0322 12:52:35.733863     440 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  33717      0 --:--:-- --:--:-- --:--:-- 33717
Error response from daemon: Cannot kill container: 3d5509b9e87c: Container 3d5509b9e87c279cc16e0a91157f3b10b66d68295bd51134aeb8ab32ec8ac4a6 is not running
Error response from daemon: Cannot kill container: d4f50ddb08d7: Container d4f50ddb08d76cb55111959bafab6859fae1c7dcf9fc7b9a89dc739da8e9ce3a is not running
Error response from daemon: Cannot kill container: 2132da75d1d4: Container 2132da75d1d494eebbd5b84911e4b2112c1b5281ebda505a341966d700a27005 is not running
Error response from daemon: Cannot kill container: f8e0f58e8afe: Container f8e0f58e8afefa35bda3d3419ca563434a233194b2617b1c91125168a3ac7cd5 is not running
Error response from daemon: Cannot kill container: 20443cf42819: Container 20443cf42819315ba1aa17e79a34398de945350408a7541c7b859008232123d4 is not running
Error response from daemon: Cannot kill container: 9a3a2a3946f2: Container 9a3a2a3946f2af44c2a0760777ebdf60b15c0e64f6822d543fbd14fb25b9d503 is not running
Error response from daemon: Cannot kill container: c113d908e413: Container c113d908e413aaeaf9d5b7d54e1cfe56d14c1bb1a063305dda1e766e55b12873 is not running
Error response from daemon: Cannot kill container: b58f59d2121c: Container b58f59d2121c511a91c2ae94c28095478b8277ac9d342c049cd907986625e234 is not running
Error response from daemon: Cannot kill container: 4037a8f5c0c4: Container 4037a8f5c0c4435a0aea5119ce60b470a0f2043e3e397f4544bacb1f67edf82d is not running
Error response from daemon: Cannot kill container: 00166159905d: Container 00166159905d9727f1a3c12fba2567034243c6a1cfb73cf09b59e5366c215f20 is not running
Error response from daemon: Cannot kill container: 0770e0bf31e7: Container 0770e0bf31e7563d0a0308b551337f05c43ccde74d075c7ffac554f9819d71f3 is not running
Error response from daemon: Cannot kill container: aa1be45e718c: Container aa1be45e718c2f882b2e958e47ca11b5b9b084cccfb60db695ff0887eb8a4c8a is not running
Error response from daemon: Cannot kill container: 6c9d849b5471: Container 6c9d849b5471f2614cd2aafb446e1a2fd0ff6eb8a2a3cfad798804d228e0f64e is not running
Error response from daemon: Cannot kill container: 8717fc06ee7a: Container 8717fc06ee7a8a01f7eb23ac0ff874244e820862018710fd5b4e4b793cfcc378 is not running
Error response from daemon: Cannot kill container: 62e435cdb1dc: Container 62e435cdb1dc57798b5cd8cdcb90ddb2d063961efa47f116aea9123e9b9abfcb is not running
Error response from daemon: Cannot kill container: 0322a181d97f: Container 0322a181d97f39244e4edc5773095e395f867e1f121b9451804cb18812ef658b is not running