GUI acceptance tests using environment deployed from packages.

Build: #2182 was successful

Job: Oneprovider hardlinks was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
21 minutes
Revision
d2cc10268e04cf220fb1974e046f2e402e0b82c5
Total tests
11
Successful since
#2129 ()

Tests

  • 11 tests in total
  • 19 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  42300      0 --:--:-- --:--:-- --:--:-- 42688
Error response from daemon: Cannot kill container: dab82ec93375: Container dab82ec933753bb574ad4c8840432a007458ef6fc5e9db440c947fdc24e1d77b 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
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
W0627 15:03:26.252595     461 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  36637      0 --:--:-- --:--:-- --:--:-- 36637
Error response from daemon: Cannot kill container: 92e62c426f93: Container 92e62c426f939a326eec27c123ea696a80948b171c9e60bd96fec38346dda154 is not running
Error response from daemon: Cannot kill container: 427245dd50a6: Container 427245dd50a62760b33423539be6390d8aaaacf43a6a22e1c772b3102b5928ad is not running
Error response from daemon: Cannot kill container: 5ca4161fb3f3: Container 5ca4161fb3f31d7f96c9c4964e2ac7498350a1ec57efa40dd241843d97e012f7 is not running
Error response from daemon: Cannot kill container: 1be67ef07a00: Container 1be67ef07a00d3326541afcbc654d2ff735ddc85df5f0cac5b0bb034ebfca48c is not running
Error response from daemon: Cannot kill container: 8468db787e8d: Container 8468db787e8d4e92994691af48f3123d4b0c36dbaae67600a6f834fcbbfd5386 is not running
Error response from daemon: Cannot kill container: ede7d8ed703a: Container ede7d8ed703ac89f9c79aeca6ec827d2779b3816d16d59cdaec21a4f29cf3258 is not running
Error response from daemon: Cannot kill container: 0b951a011602: Container 0b951a0116023cb8431a97183ef22ccc501b1b38ac07038d0757cd0133217219 is not running
Error response from daemon: Cannot kill container: dc2edabd5b84: Container dc2edabd5b849877747daadf369ffb55a67c8a44ec1aa61c3b7aac3ab4572aa8 is not running
Error response from daemon: Cannot kill container: 2cd8a0d3ea9d: Container 2cd8a0d3ea9daf5483395f12fd3d6321fe5b31497b4d3f1c8e4e43bc317a729a is not running
Error response from daemon: Cannot kill container: b2b212cb6ebb: Container b2b212cb6ebb7d2ebc2d4255aa9a94b39c8838dc0c4b7107d0ec749713d3c4d0 is not running
Error response from daemon: Cannot kill container: ade457f1e928: Container ade457f1e9288a92379c2a84e9d267c18c62f0e708aeca3b7bb5c5287d99f2b7 is not running
Error response from daemon: Cannot kill container: 8f6214d3b5ce: Container 8f6214d3b5ce9718489a83efec629e5b0e615622d9c8573cd206dbdeaaba8abb is not running
Error response from daemon: Cannot kill container: aa7ea0116c36: Container aa7ea0116c363da941815774b09ea2cb48f47e77b4861969745ff223e544e2d5 is not running
Error response from daemon: Cannot kill container: 3eb8c764dfd6: Container 3eb8c764dfd60d31511abcf04886c1c829019ac0bc6c3046447a4c56ee9ee421 is not running
Error response from daemon: Cannot kill container: 4a172742b832: Container 4a172742b83240da3f169b190845e8fb9ccf67d6620e46860be339658f0ada2c is not running
Error response from daemon: Cannot kill container: b3b40c7c6f5c: Container b3b40c7c6f5cb1b5bb647fccb8f5b80e510e82d43d3e770f86bdcce38b6296eb is not running