GUI acceptance tests using environment deployed from packages.

Build: #2096 failed

Job: Oneprovider datasets was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
22 minutes
Revision
55bf187d0d4ebfece7f274afc16ccd4ba4d3d0b1
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
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  4653  100  4653    0     0  48978      0 --:--:-- --:--:-- --:--:-- 48468
Error response from daemon: Cannot kill container: 1fca697091ca: Container 1fca697091cabf7eb09d5dad8c333b53b7fe547b20bf2c3751f7198bc5fbc6a1 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
W0412 10:07:07.920691     445 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  49500      0 --:--:-- --:--:-- --:--:-- 49500
Error response from daemon: Cannot kill container: 44b86085fc7a: Container 44b86085fc7a7945af5c0ccb4afbed01c2f0e05460c27158e3dc51d595af187b is not running
Error response from daemon: Cannot kill container: bb8c9eac26dc: Container bb8c9eac26dc42afc877ce4e781007d6427859b4db379f479ebec5b2f02b00d2 is not running
Error response from daemon: Cannot kill container: b2d276462acc: Container b2d276462accecefe735919a85c209fb9d2de90c7c232fbb5ad0ffaa425818e3 is not running
Error response from daemon: Cannot kill container: b39f1d4d8a6c: Container b39f1d4d8a6c762208431e88306a4e23c4b33335c13e8647e9026cc6409f7365 is not running
Error response from daemon: Cannot kill container: 59d301afa60c: Container 59d301afa60c49901176ff306fc7189cc1da6bc8fbd947731f8f8e1b52d549e7 is not running
Error response from daemon: Cannot kill container: c5c205e0e331: Container c5c205e0e3318806876ce0c22565b7924889e0cbcb758fc5c3707fdc758cb3dd is not running
Error response from daemon: Cannot kill container: 0bdaef63265b: Container 0bdaef63265bec8f8a5327d1d06fec94caa721e3bfa731de7b92a7dd4e925d45 is not running
Error response from daemon: Cannot kill container: 2ee3a899b2f2: Container 2ee3a899b2f2e17cc2b34bf1cc64b523fb92f8315febe743da8ba4c3bf692d91 is not running
Error response from daemon: Cannot kill container: d0dc6517dcf2: Container d0dc6517dcf285d0c35b556da5ccf15c993a514bc41573504892f21ea33cc935 is not running
Error response from daemon: Cannot kill container: 9888d65a5881: Container 9888d65a588123b5cdfbbe29c50f274e0ddbc7e37cb7b6963776c98733d16748 is not running
Error response from daemon: Cannot kill container: 53bc4090b24e: Container 53bc4090b24e8d486b49ef7980f7bf170c4e9fb3c3fbe93249628110a28a72e9 is not running
Error response from daemon: Cannot kill container: d46c0f367e12: Container d46c0f367e12164bcb82802c4a45c37a211f43d5b6946bdee7505a6b7ab02054 is not running
Error response from daemon: Cannot kill container: 7c170e159298: Container 7c170e1592983139e38579899b9748c7b6b48df23bc559c9abb863802146517e is not running
Error response from daemon: Cannot kill container: 4caeb0f21de0: Container 4caeb0f21de08a35f565aafdc84069d53416c454e06d0834c09d9349adb4cc67 is not running
Error response from daemon: Cannot kill container: 9d21e19574b1: Container 9d21e19574b1c1a007d5c883f182a0dd5eb959387c01f297e28d414810e31f1b is not running
Error response from daemon: Cannot kill container: 4e2235efdbff: Container 4e2235efdbff7c9a90fb46a8c11205d7e7b3de5683157c81adb6af14e039e6d9 is not running