GUI acceptance tests using environment deployed from packages.

Build: #2258 was successful

Job: Oneprovider ACL files was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
20 minutes
Revision
a2577ad5c8df19d48e961bdf05ea5f1feaec71b7
Total tests
8
Successful since
#2201 ()

Tests

  • 8 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  44740      0 --:--:-- --:--:-- --:--:-- 44740
Error response from daemon: Cannot kill container: d5e5adc0ec4e: Container d5e5adc0ec4ef9ef78b54436b947fb50ac2d11403589973eb5829c3d5ed484e4 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-COAF/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAF/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAF/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAF/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAF/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COAF/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-COAF/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-COAF/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-COAF/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
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
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
W0811 20:31:39.523659     446 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  43896      0 --:--:-- --:--:-- --:--:-- 44314
Error response from daemon: Cannot kill container: c110ba4191fb: Container c110ba4191fb921924bfa26ea976ad28b28763f35d52b96d701f2a5332cdac97 is not running
Error response from daemon: Cannot kill container: 5093b37a165f: Container 5093b37a165feed5e53e258265bc2ee753b22b0946e595d123ffb6c42130e1e1 is not running
Error response from daemon: Cannot kill container: 45aa3c63fc0b: Container 45aa3c63fc0b466d3383978411bbad5f22baa11509330cc6fe4b3e9223788d21 is not running
Error response from daemon: Cannot kill container: a7906db4242c: Container a7906db4242c0143152bb27bc5b5cc1870f6727794238b7997c147ef718b71de is not running
Error response from daemon: Cannot kill container: b8279a58b016: Container b8279a58b01687e67a0d1ea09bff8579475db35deb5fb11530d0550e161726f6 is not running
Error response from daemon: Cannot kill container: c45ce629a004: Container c45ce629a0049244a2d291e4e2edbb8204524474f5475e46b2ae111479cb7f08 is not running
Error response from daemon: Cannot kill container: ab08582c6767: Container ab08582c67674db00f444b18aa63733cbfd020b508c98ef77b291ec30a334c0d is not running
Error response from daemon: Cannot kill container: b5f9f019d0ed: Container b5f9f019d0ed1415b243c94a30f0a6b5a43d444242b676c186bcbca05ad74eb6 is not running
Error response from daemon: Cannot kill container: a58735eb39ed: Container a58735eb39edfdba0708189e414376f4fbc3d16271a755d043c6ee18c02a4255 is not running
Error response from daemon: Cannot kill container: a21f4a3e321d: Container a21f4a3e321d47c7f622da8e211370bea41f72924bb22d12d7f6442c84b459e6 is not running
Error response from daemon: Cannot kill container: cbfebbec638f: Container cbfebbec638fb65fcb4d3fa676b97eb7a319cf07ecaaf6766a5fe740718146f0 is not running
Error response from daemon: Cannot kill container: 198ed7ea8a00: Container 198ed7ea8a00c114038a1a494f5e6dd283a3119b2480e902fa504bac4d0aa680 is not running
Error response from daemon: Cannot kill container: 0c5ce40c0f9a: Container 0c5ce40c0f9aa40d8b8dea308dc6367da0ecec29bbe7c5a691b2f09285eb2d02 is not running
Error response from daemon: Cannot kill container: add7c91f9b2a: Container add7c91f9b2a326a9877b788fe5a2bad6a3fdd8e76335ea137ebb6f31e9c61b8 is not running
Error response from daemon: Cannot kill container: b79795f2fb51: Container b79795f2fb51e9cd38e3c6dd78c31ad914fbf67e8950c1c0cedf685642c6bf90 is not running
Error response from daemon: Cannot kill container: 4985aa31388b: Container 4985aa31388b2a31d5c97ce0d42f351767dca0925bc432a7d3be32284d12cca8 is not running