GUI acceptance tests using environment deployed from packages.

Build: #2212 was successful

Job: Oneprovider datasets was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
23 minutes
Revision
883320bbc7aaf9e91c88105b4957434d82738494
Total tests
18
Successful since
#2201 ()

Tests

  • 18 tests in total
  • 21 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  47479      0 --:--:-- --:--:-- --:--:-- 47479
Error response from daemon: Cannot kill container: f7a7037e8a0a: Container f7a7037e8a0aa6e41f6b1078dd09108b2b71822d795d2cb4978d7e66c3a524ca 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
W0708 20:33:07.304389     455 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  48978      0 --:--:-- --:--:-- --:--:-- 48978
Error response from daemon: Cannot kill container: 10a1787e0c00: Container 10a1787e0c00d6566059a961cb845c9a6941675b323acf3b21f98b647a760ddd is not running
Error response from daemon: Cannot kill container: 7321e6f64839: Container 7321e6f64839fcab91a253335ffee802b11332df798a42eb1f629d84eda01da4 is not running
Error response from daemon: Cannot kill container: 9d4555834fc6: Container 9d4555834fc63341ee71b93e4657e60b54e6248719a55df6cc4ff680bcabb510 is not running
Error response from daemon: Cannot kill container: c0abd1d25725: Container c0abd1d25725afbf9cf8f102b7288f09cac66efde70494efc87677b9062567d4 is not running
Error response from daemon: Cannot kill container: a4c364447eaa: Container a4c364447eaa5936959808500d3efaee390b02feeced468db369528595bac67b is not running
Error response from daemon: Cannot kill container: 2787761c4dfb: Container 2787761c4dfb97c3a921e16727ad63f659b32dd115f37c060ddb973e0db71ce3 is not running
Error response from daemon: Cannot kill container: 316d958376db: Container 316d958376db3be060d994b4a89da2ae6de797daa37ca4e537ad3361af856f83 is not running
Error response from daemon: Cannot kill container: 656b06b6f1ff: Container 656b06b6f1ffa741f3a0bd8b015053587ac96a43af23a63afe8d811c2a2dd4db is not running
Error response from daemon: Cannot kill container: 91f1485b85ff: Container 91f1485b85ffb759c7a72827b792548640cdf2374b4d6ce1cf7fd6d904e8c62d is not running
Error response from daemon: Cannot kill container: 8d02b9031a0d: Container 8d02b9031a0d8d5c8ff7b7fecb4178a54299382b4c0b0048f7de7f99b5232ca3 is not running
Error response from daemon: Cannot kill container: c99f9fd73803: Container c99f9fd73803a6b67791194dbb8bb894385a07b27268551a74c408ff01c8a78d is not running
Error response from daemon: Cannot kill container: f6572cb5d016: Container f6572cb5d016967067a03be428b4e76e33188067e79f2d396509c629efa36307 is not running
Error response from daemon: Cannot kill container: cff7832ade9e: Container cff7832ade9e56a60d9c5c16929b5d99b4ce8fbc66dcee1b075be9a71f7d0cf4 is not running
Error response from daemon: Cannot kill container: a8174747875b: Container a8174747875bc771a782e044b0a524d23080beb153fe6ec4ed3b073ddf818382 is not running
Error response from daemon: Cannot kill container: 5c66a014caf5: Container 5c66a014caf550cb344796f1c37d0e3d4f19398b83574b74fe1c861675e9a6c6 is not running
Error response from daemon: Cannot kill container: b7636b205ee9: Container b7636b205ee923c7e487e16711c995f20149aaa05e506e6b29eece924df6c8cc is not running