GUI acceptance tests using environment deployed from packages.

Build: #2102 failed

Job: Oneprovider datasets was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
22 minutes
Revision
bd958fd39bf31d2a3f76d4e4471d41f2b042959f
Total tests
18
Successful since
#2082 ()

Tests

  • 18 tests in total
  • 21 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  36351      0 --:--:-- --:--:-- --:--:-- 36351
Error response from daemon: Cannot kill container: 88475f3ad152: Container 88475f3ad152e44586fa511a12b2fcba515bf3d1513bbb4cf4726b7351e49edd 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
W0414 12:58:27.605338     432 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  45174      0 --:--:-- --:--:-- --:--:-- 45174
Error response from daemon: Cannot kill container: 154225dcdd70: Container 154225dcdd709bbed754d760f2477fa7d61a07ab319c0990022956fec4eb6760 is not running
Error response from daemon: Cannot kill container: 63ecdd0fa4e5: Container 63ecdd0fa4e5ff18f53735fe820e25b123357cd7aa202bbe2551c5b389a620dd is not running
Error response from daemon: Cannot kill container: 97e6eba4cdf8: Container 97e6eba4cdf8b78ac3af0ee2fa61bc178212911e75e124165f5a626afe691711 is not running
Error response from daemon: Cannot kill container: ee71fed7548d: Container ee71fed7548d0c1bf8bda191da2e4b4a92ac414957b187db771ba79fe08a6a9c is not running
Error response from daemon: Cannot kill container: 179ba6c4489a: Container 179ba6c4489a5db18978eae21eeecd83bc9219982f603b6dc1f9488012b862d8 is not running
Error response from daemon: Cannot kill container: fe2a289c8d37: Container fe2a289c8d374f82f1b8ba6d4d41eeec01c972929191575d1f23ef4858e43d3f is not running
Error response from daemon: Cannot kill container: 97d3b7103cc3: Container 97d3b7103cc3dc9580b48a31e366d17f8b896d4913d73a4e2c05cb0a74bf4bc8 is not running
Error response from daemon: Cannot kill container: f05aeba3478d: Container f05aeba3478d372178ac7c45ecf85c9a830f9bc8bc9e035d123b9eeba536b8dd is not running
Error response from daemon: Cannot kill container: c8faf2231b1c: Container c8faf2231b1c4c2a72893785ae9fc43b144c3814c2bb1280ad29cf6949707424 is not running
Error response from daemon: Cannot kill container: f846e348b889: Container f846e348b8893034ce154fd3d2cb32facd5f7a42cad5395ae09d58cb08d9771f is not running
Error response from daemon: Cannot kill container: 8cc158e760a7: Container 8cc158e760a70d55b639ac5a76795d36a21e519662e64afb177dae8b994780cb is not running
Error response from daemon: Cannot kill container: 19647c9bdded: Container 19647c9bddedb65742d826f2cdf8a5d8756b49545936e21081ed3d777427b9a3 is not running
Error response from daemon: Cannot kill container: 33363bca81f6: Container 33363bca81f6a865220ae71da5cf466b4ca0c650cb0c4b3e5f435ac54802a6d5 is not running
Error response from daemon: Cannot kill container: 881a79d41017: Container 881a79d41017f549b33a99b6b76f09b2dd19d2f9d769b1c62fb1478c9cfbe966 is not running
Error response from daemon: Cannot kill container: a24269457454: Container a242694574543fbdd7292eacba25b61b743cbc4933cd85eb22dab67aa7f88cf6 is not running
Error response from daemon: Cannot kill container: 2139d8324f23: Container 2139d8324f23b268ad5a1a19cfe2f652000581388086e0be79ca116c4ba0a114 is not running