GUI acceptance tests using environment deployed from packages.

Build: #2104 was successful

Job: Metadata was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
18 minutes
Revision
f76640da794733cef8d505342ddfce44b6e336a7
Total tests
14
Successful since
#1943 ()

Tests

  • 14 tests in total
  • 17 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  49500      0 --:--:-- --:--:-- --:--:-- 50032
Error response from daemon: Cannot kill container: d3300939669c: Container d3300939669c3179fb047b3f64d4706a4fe16043caba16998c1f06cd41b70388 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-CPT/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CPT/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CPT/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CPT/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CPT/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CPT/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-CPT/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-CPT/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-CPT/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 09:57:39.324796     433 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
100  4653  100  4653    0     0  47000      0 --:--:-- --:--:-- --:--:-- 47000
Error response from daemon: Cannot kill container: 83b84f3119ae: Container 83b84f3119ae1afac41e3598b9bc0f67797090515713f3e0fe2b0d2d78ea9e30 is not running
Error response from daemon: Cannot kill container: 781e68a95182: Container 781e68a951826df7080a1126425a3c3ae713fa8a0ba18ee272e28c2dc57fe6bb is not running
Error response from daemon: Cannot kill container: ba631e6998cb: Container ba631e6998cb953de76c301fded22175c977f8e0092999c711d09191a611965b is not running
Error response from daemon: Cannot kill container: 0864e74f725d: Container 0864e74f725d5b979f7f88c8754a597f300fb8dbba043a564f2769948f6c94a6 is not running
Error response from daemon: Cannot kill container: 1f31cf6b6089: Container 1f31cf6b60895b90516a76770e0044440deaa3b5e83615e0cd2235f52219d8d5 is not running
Error response from daemon: Cannot kill container: 908c6e983516: Container 908c6e9835165da0d147dde120f7611dc4c88830160ec48e81d11c9035bd6912 is not running
Error response from daemon: Cannot kill container: 22516d587a57: Container 22516d587a57cd005f87f8d8e03bff8aa2baf7cf6a5d3f467700a44cc2607172 is not running
Error response from daemon: Cannot kill container: 77667b71eb23: Container 77667b71eb23a9fe6dde33affa7c6180455e9609fd03446f9bd3372e928f5772 is not running
Error response from daemon: Cannot kill container: 64642fc6e485: Container 64642fc6e485be6cc1e806e50e20966b7b3d0fb4118184d99e4fa606dd1593b9 is not running
Error response from daemon: Cannot kill container: 7e6672bcd88d: Container 7e6672bcd88d5b84decbd2a164d0edc6662bbd3963d4047bcc276f278cecc97f is not running
Error response from daemon: Cannot kill container: 51656953785f: Container 51656953785f65c0b1eb453692d06fa5f3fb1a92fb78fd6291a1a576d8125694 is not running
Error response from daemon: Cannot kill container: b63e11f15efb: Container b63e11f15efb6dc84aded20255db6eebe5ee2c1d3a31b2613fa8b290ec9bdde8 is not running
Error response from daemon: Cannot kill container: 1b941841f814: Container 1b941841f814673a484d7065e51a632632840fd8878ddfad2db22535efe5e048 is not running
Error response from daemon: Cannot kill container: d68006b3b670: Container d68006b3b670e8a0ad147a68b655609e962d0745b2e8d512eb5bb2c6dfccb2d3 is not running
Error: No such container: d68006b3b670
Error response from daemon: Cannot kill container: 2a5ae054f88c: No such container: 2a5ae054f88c
Error: No such container: 2a5ae054f88c
Error response from daemon: Cannot kill container: 5b6fa5fed79c: No such container: 5b6fa5fed79c
Error: No such container: 5b6fa5fed79c