GUI acceptance tests using environment deployed from packages.

Build: #2130 was successful

Job: Oneprovider datasets was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
21 minutes
Revision
39fb434fa4268b56f32dccaa52527f3591cd9ea8
Total tests
18
Successful since
#2082 ()

Tests

  • 18 tests in total
  • 20 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  42300      0 --:--:-- --:--:-- --:--:-- 42300
Error response from daemon: Cannot kill container: d233ed0b63c4: Container d233ed0b63c4dad5edc950ff9a8a7e3de0272c571ba2d81c8a5359c01b86bcde 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-CODT/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODT/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODT/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODT/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODT/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODT/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-CODT/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-CODT/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-CODT/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
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
W0504 20:39:38.193765     441 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  42300      0 --:--:-- --:--:-- --:--:-- 42300
Error response from daemon: Cannot kill container: 8beb43de4e6e: Container 8beb43de4e6e0adef03a366842b827e194c55cd84d5687adca25ff00928f9082 is not running
Error response from daemon: Cannot kill container: f1fbced56af6: Container f1fbced56af62c7b4bce01741c7d8dfeb9d98838d61036e05822a2cdf5d7111f is not running
Error response from daemon: Cannot kill container: 0e6c9c8422ca: Container 0e6c9c8422ca930c6917435a953825dda6b8cc894d2e769c976eb5fe45e02d3a is not running
Error response from daemon: Cannot kill container: b2eedb40e74a: Container b2eedb40e74aa7ddc917f2dabc3d340791f384542f917101b4ec7983cbfd3e1d is not running
Error response from daemon: Cannot kill container: 2294869d7f94: Container 2294869d7f940f3d7038d433a5ce58fbbb8a64663ae24613148e55980ff49a3a is not running
Error response from daemon: Cannot kill container: 4a0cccb6b23f: Container 4a0cccb6b23fdb6d730156138ccde8e76da0405ab6c41f50550b455247ccb4a0 is not running
Error response from daemon: Cannot kill container: 974d26415789: Container 974d26415789a37564aee919f30be52374e6aa84ac7bf69b6a91a2d77e08ce2c is not running
Error response from daemon: Cannot kill container: d610dfa8db97: Container d610dfa8db97edf78a8bc44afe33b01a2213656032f4c4367a17fce69c78bc7d is not running
Error response from daemon: Cannot kill container: 2b6ef6073f51: Container 2b6ef6073f516a408905d2088074612d92fdb921b920fb53df7baf4a3db989a1 is not running
Error response from daemon: Cannot kill container: e98fbc33ee6a: Container e98fbc33ee6ad65161b8551efd168f4e995e8e72a0a7fcf65330bfff493c99ad is not running
Error response from daemon: Cannot kill container: d40e3d856926: Container d40e3d8569264f9bf52f11f4eaf1f59e712407962999c5e734f519a4063d1880 is not running
Error response from daemon: Cannot kill container: 6a9d390edba5: Container 6a9d390edba5c561854a9a9e808a7f031ba997bfb3299efe9d6b9c536f0a3403 is not running
Error response from daemon: Cannot kill container: f8a9d1fd5b74: Container f8a9d1fd5b7462ca6aa8c117cd77cf49bd1a588f4c557c844de24a302eccb761 is not running
Error response from daemon: Cannot kill container: c1bc833a919a: Container c1bc833a919a6c4f713b6394c35161657b83f66be589929c772971592eadbedd is not running
Error response from daemon: Cannot kill container: 7d95ed0b18b7: Container 7d95ed0b18b723f1bbd84cb23cd2e13c6d839a8e9c0e15d4bcea057e1dc7ed62 is not running
Error response from daemon: Cannot kill container: f0b153353e86: Container f0b153353e866ac6ba3a8bc1d38e86a928001f30ffe38624bc03cd5c3ce09043 is not running