GUI acceptance tests using environment deployed from packages.

Build: #2096 failed

Job: Shares basic was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
16 minutes
Revision
55bf187d0d4ebfece7f274afc16ccd4ba4d3d0b1
Total tests
18
Successful since
#2059 ()

Tests

  • 18 tests in total
  • 1 test was quarantined / skipped
  • 16 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  46530      0 --:--:-- --:--:-- --:--:-- 46530
Error response from daemon: Cannot kill container: 40403959de41: Container 40403959de4157ab19cb4a63e57624ce5e54ee5745d14d98cada16421f52d645 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-CSBT/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CSBT/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CSBT/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CSBT/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CSBT/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CSBT/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-CSBT/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-CSBT/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-CSBT/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
W0412 09:31:48.192883     430 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  48978      0 --:--:-- --:--:-- --:--:-- 48978
Error response from daemon: Cannot kill container: 8d942d2c33ae: Container 8d942d2c33ae19b97ebd97e9aad195eec02a3bc113e6cd7bce268be23752e859 is not running
Error response from daemon: Cannot kill container: ebf1e71097bf: Container ebf1e71097bfc93236b03aa80481c07675a161d7584adba99621a6bd981a1206 is not running
Error response from daemon: Cannot kill container: fbe403d141fd: Container fbe403d141fd76c1903eec92dbec37d84ae148712685ac632b22ab4d091659b0 is not running
Error response from daemon: Cannot kill container: 13f9016a03fe: Container 13f9016a03fee93df7d1276aa4488d98c9da25ac5fa985622505b7578be76fdc is not running
Error response from daemon: Cannot kill container: 861787d9687c: Container 861787d9687c792e6e8cf21d3b02eeeda04a3dc0b4c6cbe40209534b8fa33dfb is not running
Error response from daemon: Cannot kill container: 38ea267adaf5: Container 38ea267adaf594fda18fec4872398fda6847b849f7d563e69377d096d82cad8a is not running
Error response from daemon: Cannot kill container: 9cd48df58af3: Container 9cd48df58af3a868590c543962b325e67b89722a8063d98308e0a064db657397 is not running
Error response from daemon: Cannot kill container: fdb208ac8f7a: Container fdb208ac8f7a2fff998d9566a805989f3e978dbdd538fac1f08663f05af3e108 is not running
Error response from daemon: Cannot kill container: 1a7518ddf848: Container 1a7518ddf8484c61cb15575591d2f166268c3647e6740191f6084b456c5de170 is not running
Error response from daemon: Cannot kill container: 3eaad14de833: Container 3eaad14de8333564fd1fe87032058477d4e8dd7fe1d0333619f2c0b142226d79 is not running
Error response from daemon: Cannot kill container: d854363b1d9d: Container d854363b1d9d25d7fec2bf49862536fc549023cf4cc4648ee700111bd456113a is not running
Error response from daemon: Cannot kill container: 446ccd8ce20d: Container 446ccd8ce20d762dfafb1bf02d9d33c3562d3ad4cc58dfe74d7e985e6842ccd0 is not running
Error response from daemon: Cannot kill container: a2bf07e88f12: Container a2bf07e88f120be14f6ba8db83306d7ae34e06148c014d03c3764fc6618a7b97 is not running
Error response from daemon: Cannot kill container: e4b8052e0ce7: Container e4b8052e0ce7cb9e5a54e369edd7757f177436628388375e41bff9bac8771fae is not running
Error response from daemon: Cannot kill container: cac99810b0db: Container cac99810b0db728ac6266a276f61119c604fe55c994dde24eaf33f3f4775255e is not running
Error response from daemon: Cannot kill container: 2a976aabdae6: Container 2a976aabdae669c0df5bc682c07261ec53142e96e1138c326a70e7a66a5889b8 is not running