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

Build: #2399 was successful

Job: Directories times was successful

Job result summary

Completed
Duration
17 minutes
Revision
442fbc00c3ff98eb304229ca0f7f38a6c9aec746
Total tests
10
First to pass since
#2397 (Child of ODSRV-OZP-1760)

Tests

  • 10 tests in total
  • 15 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  43896      0 --:--:-- --:--:-- --:--:-- 43896
Error response from daemon: Cannot kill container: 02c0f2f357c9: Container 02c0f2f357c90a21d6285e6601bb6fe6bf0b62e5e0863ce9da3407894223bb9a 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-CDTT/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CDTT/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CDTT/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CDTT/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CDTT/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-MAOPT-CDTT/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-CDTT/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-CDTT/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-CDTT/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
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)
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
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  25151      0 --:--:-- --:--:-- --:--:-- 25016
100  4653  100  4653    0     0  25151      0 --:--:-- --:--:-- --:--:-- 25016
Error from server (NotFound): pods "dev-oneprovider-krakow-0" not found
Error response from daemon: Cannot kill container: 8e83255e6e8f: Container 8e83255e6e8f4a76021b3eed73ccaed0769b9967e21548580d34b415a25ababb is not running
Error response from daemon: Cannot kill container: f30e9e5cfd40: Container f30e9e5cfd40cc79907e16af899286596d02d76c00a10c3430320a240278b55c is not running
Error response from daemon: Cannot kill container: a650f6e01eae: Container a650f6e01eae910306d4f16f44c4c6140bc9d09880e3ff07d41aae4f61781551 is not running
Error response from daemon: Cannot kill container: aadb7a8cbec4: Container aadb7a8cbec44c2bab1542721912b1c7906708c46f85e9be888dd09b506e2762 is not running
Error response from daemon: Cannot kill container: b0ca3480e55d: Container b0ca3480e55dcb4236c5fa9e69b236b9762d482d16ad2c654e2ad7b6a3e9e9b0 is not running
Error response from daemon: Cannot kill container: e63c62976231: Container e63c629762319d5e12d965369f6140a8e6884383cb0c451f54fba06b45abee6c is not running
Error response from daemon: Cannot kill container: 1c4b889e8970: Container 1c4b889e89708e6fa62ea09b081909c0c84cd4e286fe301f3e35caa43064ad87 is not running
Error response from daemon: Cannot kill container: 17d41a43fd4a: Container 17d41a43fd4ada57f587f02a46c187188c4ea1909f2fcda958d8ab7cdbfa4fc7 is not running
Error response from daemon: Cannot kill container: 9c13725deced: Container 9c13725deced3b9f5552e20133a8af937899bb7740a2e5febebf2c784aed583d is not running
Error response from daemon: Cannot kill container: 0e576921a328: Container 0e576921a3287ab13c217e56712ba080bc6599dd3abaef3dc9412408d6732221 is not running
Error response from daemon: Cannot kill container: 61c4468d3276: Container 61c4468d3276eeb9a287ba22c38f8cfa7963b8c93aa349aa0f5ef59f3d97c7bc is not running
Error response from daemon: Cannot kill container: 9b77dd893ce1: Container 9b77dd893ce170d115e1004b77166b5254782b5799fdc6b1eeceac642ab0afa4 is not running
Error response from daemon: Cannot kill container: beb4912d1220: Container beb4912d1220c35f989aa7ea656618a7ffa50799f30c42052018b6f278354a76 is not running
Error response from daemon: Cannot kill container: d4081b40e6a5: Container d4081b40e6a50563fa2bd4d562a34d90f72c948b2ae42c0644e78e70bba64602 is not running
Error response from daemon: Cannot kill container: 9a8107fdc526: Container 9a8107fdc526cb1374b4fc51e83a22f271cb828995543f3dc178410fb5d8af38 is not running
Error response from daemon: Cannot kill container: 5794233e857c: Container 5794233e857c75ae8c62c0247a95931e4e4c691add0e4c41575b3e4b81e407bc is not running
Error response from daemon: Cannot kill container: 04a5085db122: Container 04a5085db122e976bed4a8511466dc4a0d2edffbad59a100600f01909783b129 is not running