GUI acceptance tests using environment deployed from packages.

Build: #2193 failed

Job: POSIX multiuser was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
19 minutes
Revision
466b4a1341ba42e3ce27e138642da6627c86d0c6
Total tests
8
Successful since
#1943 ()

Tests

  • 8 tests in total
  • 17 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  45174      0 --:--:-- --:--:-- --:--:-- 44740
Error response from daemon: Cannot kill container: 2fb66e03ae87: Container 2fb66e03ae8712fad47425ef31455436cae920494420b5a7b88d50366d9041af 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-CPTM/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CPTM/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CPTM/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CPTM/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CPTM/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CPTM/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-CPTM/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-CPTM/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-CPTM/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]
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
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
W0701 01:06:31.122563     451 warnings.go:70] policy/v1beta1 PodDisruptionBudget is deprecated in v1.21+, unavailable in v1.25+; use policy/v1 PodDisruptionBudget
  % 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 --:--:-- --:--:-- --:--:-- 37829
Error response from daemon: Cannot kill container: aa8723750689: Container aa87237506894853b865d7d42dbef3343f054484d45d86e2016089e4db0c0bd7 is not running
Error response from daemon: Cannot kill container: 7b8333feb8f6: Container 7b8333feb8f63b5fd170d71d774871f8c2edf08bd77d7c802eaab9b6f5de2dbc is not running
Error response from daemon: Cannot kill container: 1ab7a5f8553a: Container 1ab7a5f8553a83f55905daac8ba619e5ca2ee2ad6eeae9604fffa2f2593d2841 is not running
Error response from daemon: Cannot kill container: 8e9ce48fb6d9: Container 8e9ce48fb6d919bbcc69c71e1cb5453ca880bb0319475e30ff4f465aa22d100b is not running
Error response from daemon: Cannot kill container: 61c4c83cce3d: Container 61c4c83cce3d6ed00a877936a5c32c2826db70f74f3e414d62d95f2b674f908c is not running
Error response from daemon: Cannot kill container: 553fd9044386: Container 553fd90443860d4190cce3716734e8059794d8c58dce947c832541f815176760 is not running
Error response from daemon: Cannot kill container: e28ea918adce: Container e28ea918adce8bc3b9e4214c19372454ec7f0df699dc5f1d5112951a5a07bb83 is not running
Error response from daemon: Cannot kill container: db922a26d8af: Container db922a26d8af684326c9d77a76000e472f895c45662095c66e52a488ad0adea5 is not running
Error response from daemon: Cannot kill container: 7a482219e8c0: Container 7a482219e8c0b986a8d310a85da7e11972676aa5207a15451b5b28fed53d79cf is not running
Error response from daemon: Cannot kill container: d94012f976f6: Container d94012f976f6807ab98e914f00b1eab1d2ea7b5e6babc8e1f619932e4b68e51a is not running
Error response from daemon: Cannot kill container: fb55a1a1653d: Container fb55a1a1653dc917b94639138460f0e8097af509a9c8a4e0c8abeb61513a1d0a is not running
Error response from daemon: Cannot kill container: 2c9cf4729d86: Container 2c9cf4729d867e638bd254d4f62ac3186aa0baf68216a1738cef50151b584007 is not running
Error response from daemon: Cannot kill container: 4d5474705aee: Container 4d5474705aee860e2fd978cfda6f80da399c77e35849d2878525c74ddaf6e011 is not running
Error response from daemon: Cannot kill container: 2bbc2a9dc864: Container 2bbc2a9dc8643cc47addc66eb713ea29323694e8fbbf845996f58a66bb1b9c28 is not running
Error response from daemon: Cannot kill container: a94587b51009: Container a94587b51009065f6f9781d83c7c117811ce1e9f766178cf6530763bc53b8873 is not running
Error response from daemon: Cannot kill container: 2bd8dfa0d7fb: Container 2bd8dfa0d7fb78f03c4f1850ffdce5a644315ffc7c532df34d8fda37d550e766 is not running