Acceptance tests using different clients concurrently. Environment deployed from packages.

Build: #2121 was successful

Job: Chrome ACL tests was successful

Job result summary

Completed
Duration
40 minutes
Revision
81644e06108ac0893289e50d537125de59336e1e
Total tests
42
Successful since
#2117 ()

Configuration changes

Job Chrome ACL tests with key ODSRV-MAOPT-CAT no longer exists.

Tests

  • 42 tests in total
  • 37 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  47479      0 --:--:-- --:--:-- --:--:-- 47969
Error response from daemon: Cannot kill container: f1fdb1f5a998: Container f1fdb1f5a998a3fa164bf93e7945c4162461483330f36a520c79816ad139e95d 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-MAOPT-CAT/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CAT/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CAT/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CAT/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CAT/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CAT/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-MAOPT-CAT/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-MAOPT-CAT/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-MAOPT-CAT/onedata/onezone_swagger/bamboos'...
error: failed to create clusterrolebinding: clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
/bin/sh: 2: [[: not found
Error: could not find tiller
error: failed to create clusterrolebinding: clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
error: failed to create clusterrolebinding: clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
id: ‘user1’: no such user
command terminated with exit code 1
id: ‘user2’: no such user
command terminated with exit code 1
command terminated with exit code 1
command terminated with exit code 1
command terminated with exit code 1
id: ‘user1’: no such user
command terminated with exit code 1
id: ‘user2’: no such user
command terminated with exit code 1
command terminated with exit code 1
command terminated with exit code 1
command terminated with exit code 1
Defaulted container "oneclient" out of: oneclient, wait-for-onezone (init), wait-for-token-dispenser (init)
Defaulted container "oneprovider" out of: oneprovider, onezone-registration-token (init)
Defaulted container "oneprovider" out of: oneprovider, onezone-registration-token (init)
Defaulted container "oneprovider" out of: oneprovider, onezone-registration-token (init)
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  46069      0 --:--:-- --:--:-- --:--:-- 46069
Error response from daemon: Cannot kill container: d1b8c38dade8: Container d1b8c38dade84390f7fcc00fcfba46c0fd3c5d74481f06f82956a900e612da68 is not running
Error response from daemon: Cannot kill container: 95175012a2a0: Container 95175012a2a0a52af852ffefab57cde1f2a2fd9f9e5e9c59c6fd92afaa0defc1 is not running
Error response from daemon: Cannot kill container: 48cabc33f289: Container 48cabc33f28953cf8231bea13a5a234e6bbcfbe9ae19322735298a9de409ac6f is not running
Error response from daemon: Cannot kill container: 02e120676083: Container 02e1206760830fad73a45736344c8aac51808b1ecefc1f095c098164332d2331 is not running
Error response from daemon: Cannot kill container: 1791aea0de3b: Container 1791aea0de3bccb871b1bec22100144994e6315c7a7be06d5ccbadd3a7e73ae9 is not running
Error response from daemon: Cannot kill container: b05be46ccac1: Container b05be46ccac1cf86039c2977858f7142a15a1901595e98ae2650f76a1b183e8e is not running
Error response from daemon: Cannot kill container: e2b0cf751094: Container e2b0cf7510940408484f750ff0bb093c82950b3860dbcc6d8c1c50c87d1e5302 is not running
Error response from daemon: Cannot kill container: 9d256ff95d05: Container 9d256ff95d05e36c7453616e6f0dabb3519a47918635e916dc38eed4ed74e3a5 is not running
Error response from daemon: Cannot kill container: ed7b772789fb: Container ed7b772789fbaa424376e078eda4f9df66345e60effbf7a8addd801f402f3635 is not running
Error response from daemon: Cannot kill container: b6e14c7710e4: Container b6e14c7710e40ef5adb7bfe8b5338dfe12f7eed037fa1590d4d19065fdcc24eb is not running
Error response from daemon: Cannot kill container: 3f0f7663f9a4: Container 3f0f7663f9a4492f4609a700dcc9bbb17535ab93142270d78099056003f70f50 is not running
Error response from daemon: Cannot kill container: eafa7d914120: Container eafa7d9141200cbbda3b7d63b4bb87d35e618be92d470a7f29026e4dc224c2b2 is not running
Error response from daemon: Cannot kill container: 78499e1f21e5: Container 78499e1f21e55f2b512f76d0d17a9b7653b2e76e226907d7ba869ed743359019 is not running
Error response from daemon: Cannot kill container: 353e4879a122: Container 353e4879a122b854ce81d2e3bd3ec4d51e1a702a6ced20fc896ce9413e917674 is not running
Error response from daemon: Cannot kill container: 4ce1b407b520: Container 4ce1b407b52075fca6f6d25c85312d34f4f630c8a6b79a205e624415080e61f4 is not running
Error response from daemon: Cannot kill container: 503df173accb: Container 503df173accbdc2f6d3cc1a177e609064fe1b343e3428a4360dded1ab7cc5c13 is not running
Error response from daemon: Cannot kill container: 8ef0dcb7e56a: Container 8ef0dcb7e56abe35d18e6aa3aff4efa16aea4de4cac48afaadc08e1a38ff65b3 is not running