GUI acceptance tests using environment deployed from packages.

Build: #2280 was successful

Job: Oneprovider datasets was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
32 minutes
Revision
c1f32fd27d328461e823cba8ffae3880e30ca404
Total tests
17
Successful since
#2262 ()

Tests

  • 17 tests in total
  • 30 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  40815      0 --:--:-- --:--:-- --:--:-- 41176
Error response from daemon: Cannot kill container: 41644dc5d66a: Container 41644dc5d66a111f67f9d7a0d729d6acad9f831a3b087dcac895352f828b2d0f 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
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
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
W0825 23:51:59.070122     448 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
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  4653  100  4653    0     0  18034      0 --:--:-- --:--:-- --:--:-- 17965
Error from server (NotFound): pods "dev-oneprovider-krakow-0" not found
Error response from daemon: Cannot kill container: 18ef2754aef1: Container 18ef2754aef158b16afd0ca9c710341d01ef5459d815b4c80766d5f9a7c55e46 is not running
Error response from daemon: Cannot kill container: 31be63aaaf40: Container 31be63aaaf40bf187cd8cdd720ccf8ace15c0fb3e88f894d16986f4cbcaec2fc is not running
Error response from daemon: Cannot kill container: ed096dd1e0f0: Container ed096dd1e0f0b24cb466803b64d13f3b47f2d8abe8193b5d74f4d94a32906d37 is not running
Error response from daemon: Cannot kill container: 40c0f192889d: Container 40c0f192889d227c22f0697deea464851133ef5a2b02f5df74deaff959338e55 is not running
Error response from daemon: Cannot kill container: fdda569cdbae: Container fdda569cdbaef1a3821e3aa86084b6051f3548feba9b815807b4e7239d8d0c18 is not running
Error response from daemon: Cannot kill container: 9da87db092a2: Container 9da87db092a203132d18132e6003afe221d38cba10455282bd446cd035f8d56c is not running
Error response from daemon: Cannot kill container: 9bc1a24613e8: Container 9bc1a24613e87b586e04c44de65d565e8b654f3add20fa997bc68ac00ac93281 is not running
Error response from daemon: Cannot kill container: cb814fb43529: Container cb814fb43529e5d41b3f8c311f884f23998b0e9e44307efc070142f4b54625f0 is not running
Error response from daemon: Cannot kill container: 5b1c213f7e64: Container 5b1c213f7e640991e7e78be31f1097d5fb38b082184069009bf8161f4141ce8a is not running
Error response from daemon: Cannot kill container: f3d7d97f765d: Container f3d7d97f765d4d4a470d26c7df47a944d7ebdc89e17192713f4d05dcb5072532 is not running
Error response from daemon: Cannot kill container: 1789c9fec48a: Container 1789c9fec48aefc53ea3f263f287329643418b6f9b72be66ff34bfdd33a5d973 is not running
Error response from daemon: Cannot kill container: ae45be74cce7: Container ae45be74cce796f297bdc371e6f6e099b57c2af9a1c2cb6a60fda1301298d16b is not running
Error response from daemon: Cannot kill container: 133e1cd87b45: Container 133e1cd87b450777a254896def27948e6cf4e78fc6e29bee1bdbafcc58628ab6 is not running
Error response from daemon: Cannot kill container: e4326cb92924: Container e4326cb9292464b216fe6ad7903550bb18d77a918d5404474d54b0c80fbf11a0 is not running
Error response from daemon: Cannot kill container: 7dd80c0a3a71: Container 7dd80c0a3a710982eab6ba53413daeb952990428b107bca3053ec1b14d9dbd0e is not running
Error response from daemon: Cannot kill container: 582949000eda: Container 582949000edaa935843b08cc692ece8ef6ef20825b872c00f50d4ab88a45311f is not running