GUI acceptance tests using environment deployed from packages.

Build: #2250 was successful

Job: Oneprovider data tab was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
16 minutes
Revision
a286f0f6f3f012eb6568be58a9820a7399524818
Total tests
29
Successful since
#2201 ()

Tests

  • 29 tests in total
  • 15 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  50576      0 --:--:-- --:--:-- --:--:-- 50576
Error response from daemon: Cannot kill container: afb52ecded97: Container afb52ecded97b3859933a846089b166d037072ca5073d452219e7393d51efee7 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-CODTT/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODTT/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODTT/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODTT/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODTT/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODTT/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-CODTT/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-CODTT/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-CODTT/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
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]
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
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
W0802 06:57:20.595819     447 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  46069      0 --:--:-- --:--:-- --:--:-- 46069
Error from server (NotFound): pods "dev-oneprovider-krakow-0" not found
Error response from daemon: Cannot kill container: a3833d7188fc: Container a3833d7188fca4978fbe9669dfdfb1e4c4213b6be00cdbe98e2e064c44d68528 is not running
Error response from daemon: Cannot kill container: 9eaf293f8e8c: Container 9eaf293f8e8ccaf933b5ecb4f0d4e4f81673d6d83d14c6354bbd6ccee29cf9cc is not running
Error response from daemon: Cannot kill container: 5d1942b723b3: Container 5d1942b723b3f34dfa8c58df27d3ef3c8446fef749eb4134f007c21957fd159f is not running
Error response from daemon: Cannot kill container: 37bb269c4718: Container 37bb269c471874d015a13dd98f5d28b797426ac0e0f37e3dd6dde23bed50f80a is not running
Error response from daemon: Cannot kill container: 2423e3da5c93: Container 2423e3da5c93a985267c38c3cae830b63d311ef4136cbe95ba71f4b4b76fbcbd is not running
Error response from daemon: Cannot kill container: 2f89a075a53c: Container 2f89a075a53c96a5d605304bcd01cfdd5ae0be772dfdff1c38b402997cebb71b is not running
Error response from daemon: Cannot kill container: 838acad0ef1b: Container 838acad0ef1b3df46394edbf330ead6f7adf37ce9632b288573bb22d139bab7f is not running
Error response from daemon: Cannot kill container: 00781b44f7a8: Container 00781b44f7a8607181f473f71f89af302c8524d2df007f9fc7b565b6ab0e9384 is not running
Error response from daemon: Cannot kill container: e04826ecc136: Container e04826ecc1361e18fd489ddbc5d3ff07524b48e7ea01647b6966ed513af93a86 is not running
Error response from daemon: Cannot kill container: 3eb630599977: Container 3eb6305999775f64f725f240333792a75eb2d1d2a7da0c6f5541bf872e8da2c0 is not running
Error response from daemon: Cannot kill container: af7ad7e595b1: Container af7ad7e595b1fff6280a7e0dc3df82ecf4c8f0d18541ccd0fb859ef327c83c5b is not running
Error response from daemon: Cannot kill container: 2a5aac5f6029: Container 2a5aac5f6029392cf8a0ecad54bf72543aa1ac5a788f317f5c855bf8cabffb25 is not running
Error response from daemon: Cannot kill container: d3a8a68dd856: Container d3a8a68dd856379cfbb64aafe80e66a0ac902d9be9bcd349331c3a785efac571 is not running
Error response from daemon: Cannot kill container: 93c975eb0dec: Container 93c975eb0dec8b1caf796b06cd76f364ba30a62e3cb75be6f14cb4f8802e20e9 is not running
Error response from daemon: Cannot kill container: 44ef4fed1a20: Container 44ef4fed1a20884b1d179ea7b5cb613c562e43ffd3122dbf06ca0e2d392b3ba8 is not running
Error response from daemon: Cannot kill container: 5f8e7bc1c823: Container 5f8e7bc1c8236c7506aff68bb7db6b0c700679fcf23f649e36a0cd4c0bddd090 is not running