GUI acceptance tests using environment deployed from packages.

Build: #2027 failed

Job: Chrome metadata test was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
28 minutes
Revision
06b7ddbe39e2302126bded895dfde2e9f3fa8004
Total tests
24
Successful since
#1943 ()

Configuration changes

Job Chrome metadata test with key ODSRV-GAPT-MTC no longer exists.

Tests

  • 24 tests in total
  • 27 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  18914      0 --:--:-- --:--:-- --:--:-- 18991
Error response from daemon: Cannot kill container: 6b5db5bb8a79: Container 6b5db5bb8a79bd73821dabbf8340086f4cb411f7172c78cef64e7c2a73a8dbce 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-MTC/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-MTC/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-MTC/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-MTC/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-MTC/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-MTC/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-MTC/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-MTC/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-MTC/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
W0317 07:35:19.826487     431 warnings.go:70] policy/v1beta1 PodDisruptionBudget is deprecated in v1.21+, unavailable in v1.25+; use policy/v1 PodDisruptionBudget
  % 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  30814      0 --:--:-- --:--:-- --:--:-- 30611
Error from server (NotFound): pods "dev-oneprovider-krakow-0" not found
Error response from daemon: Cannot kill container: 5def19458a0e: Container 5def19458a0ee5e2854c60ac79908e7f1c96cf4dda6051d7b73abdafc25e8b5d is not running
Error response from daemon: Cannot kill container: 07aae0acd13a: Container 07aae0acd13a14cdcb541930dd7092127a27be4d3810bfea267805c753318316 is not running
Error response from daemon: Cannot kill container: f3e33e55df5b: Container f3e33e55df5b32e985322874b048aa5965bfc0e2282337bf19eb3eb2342e44b5 is not running
Error response from daemon: Cannot kill container: 5531950160c6: Container 5531950160c6cfc1f1c06fbad78b8c1a5d093e9b6cfcee636923c7ff015fc385 is not running
Error response from daemon: Cannot kill container: acb1ce3bbef6: Container acb1ce3bbef66f75b76f2e2eb501712b53986048d509c785b57ddf5f2cfd0ec3 is not running
Error response from daemon: Cannot kill container: 4d85a4b3541c: Container 4d85a4b3541cecce5c7302d2cefe774d9fee4feed8c68816e075217e2e1434bc is not running
Error response from daemon: Cannot kill container: a17eab2e7739: Container a17eab2e7739fcf2f3de947272ddc0f1f4e000812173f86e12a36b24912b40ca is not running
Error response from daemon: Cannot kill container: 0d8a82ae7ad2: Container 0d8a82ae7ad23ba1f0df3fa61b404b24e141ff504fb1b3fe6a03d792e0a6f4e1 is not running
Error response from daemon: Cannot kill container: e9080fd86290: Container e9080fd86290f7acbccb06128f5ca859b61d0c5a94670eafa95aedac956ac9c1 is not running
Error response from daemon: Cannot kill container: 25dd2ae30bc5: Container 25dd2ae30bc5aaab296dd4277a3ecc07a34a84733388bdd330f67feaf9776fe3 is not running
Error response from daemon: Cannot kill container: 15ec235917f7: Container 15ec235917f72723910ed84f39ca33bc7e652ff127c427e6af97c86836af2388 is not running
Error response from daemon: Cannot kill container: d66d65fc6cee: Container d66d65fc6ceefd343baf0c2df4352909760bcec91e7ae8ea547109e41c425f3d is not running
Error response from daemon: Cannot kill container: 1791d877d0b7: Container 1791d877d0b72608ef5f30bbaf803e5f6cb92f885ceea5d56edd2155600f2168 is not running
Error response from daemon: Cannot kill container: 51c5aa436b0c: Container 51c5aa436b0c995cfb1f0f0e864bfda23e3f552b41746a07657c847d88dc3951 is not running
Error response from daemon: Cannot kill container: c70e2af45b81: Container c70e2af45b818fca8f049fe4c3b3064d96ee09d07d4d5a4c81c0934b7538aace is not running
Error response from daemon: Cannot kill container: f91f301feb70: Container f91f301feb700281a6772dbf415742aeae32307963be7ff6e5e07c0ec376f29e is not running