GUI acceptance tests using environment deployed from packages.

Build: #2104 was successful

Job: Oneprovider hardlinks was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
14 minutes
Revision
f76640da794733cef8d505342ddfce44b6e336a7
Total tests
11
Successful since
#2082 ()

Tests

  • 11 tests in total
  • 14 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  48978      0 --:--:-- --:--:-- --:--:-- 49500
Error response from daemon: Cannot kill container: d2d9b17b848b: Container d2d9b17b848b94cd9c0824e2537b31e7d8ccd0b8e8cd1cf37328a6b5186d193f 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-COH/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COH/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COH/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COH/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COH/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COH/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-COH/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-COH/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-COH/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
W0415 10:22:00.320756     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  43485      0 --:--:-- --:--:-- --:--:-- 43485
Error response from daemon: Cannot kill container: a756db809377: Container a756db809377ce128d9fbcda8497c6bb433576756cd95d4b5a3cb498312b06f1 is not running
Error response from daemon: Cannot kill container: f64d130cf57b: Container f64d130cf57b78af10d335f8569c7fc1ce735a0719cdc3977464dafd4910623b is not running
Error response from daemon: Cannot kill container: 99d690879572: Container 99d69087957236a26dba0d87115a1666a43e64edd531fa53dae0ae8eb7c34f80 is not running
Error response from daemon: Cannot kill container: d01856cb8f03: Container d01856cb8f033c0a8989dd2d932a3e7f7f036bf051054665d45be822c6ea1926 is not running
Error response from daemon: Cannot kill container: 5c15a688d013: Container 5c15a688d013239cbbe37f04a491c66c3405998ebb6184d19671b8997d366a43 is not running
Error response from daemon: Cannot kill container: 5b822c7cab3e: Container 5b822c7cab3ebc5ad2da7187afcaf1efa431cc2bef6d70ee3ddc8e3cd200a4f2 is not running
Error response from daemon: Cannot kill container: adfb6542aa7a: Container adfb6542aa7af42d31d84906babaad643d030e67703b6da5f2dbe74c57a8c5c7 is not running
Error response from daemon: Cannot kill container: 9168881ebdcb: Container 9168881ebdcb3f8d229573f10c7b9fa7775098f748753a75d4643a7df051c9c6 is not running
Error response from daemon: Cannot kill container: d1ca8f1121db: Container d1ca8f1121db7a2a8a58bad6026ba898552d7abe89afe6817fa09e9fadd27d4a is not running
Error response from daemon: Cannot kill container: ed87d624ae91: Container ed87d624ae91bb69153c8558e1e8d4fbb9be3b75eca5ec4bda5027e526b4fd7f is not running
Error response from daemon: Cannot kill container: 13079625d58d: Container 13079625d58d10240cd0ed18c5e2f823705298559f2ab648c5525e6119941eca is not running
Error response from daemon: Cannot kill container: 52e706d9f240: Container 52e706d9f2409ff160432fdb6cc3b7b876f7517c0487581e91e3f29e8a127a4b is not running
Error response from daemon: Cannot kill container: 1d1a31e505a9: Container 1d1a31e505a9db05a66576b3572fa57f5893f43c7fa023d7c7549d275498fa94 is not running
Error response from daemon: Cannot kill container: af7b4e1b7d84: Container af7b4e1b7d842de28007c982b15d58bf116c8322155f1b421ea39cd13e459c14 is not running
Error response from daemon: Cannot kill container: bef5fb826dc7: Container bef5fb826dc722e4d473d2f445b3b72f00205df66728ad81368bcbb90ffb58b0 is not running
Error response from daemon: Cannot kill container: 67cf3f195146: Container 67cf3f195146e5151c81afa524b235a3e1a13e8af4794a319c0d86464b66246c is not running