GUI acceptance tests using environment deployed from packages.

Build: #2265 was successful

Job: Oneprovider datasets was successful

Stages & jobs

  1. Acceptance Test

Job result summary

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

Tests

  • 17 tests in total
  • 31 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  44740      0 --:--:-- --:--:-- --:--:-- 44740
Error response from daemon: Cannot kill container: 7d7a0b6c724a: Container 7d7a0b6c724a5a5f0ece8fb7e5985806c596d13ebc337800de3c22c581966d33 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
W0817 21:30:19.892143     449 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  23034      0 --:--:-- --:--:-- --:--:-- 23034
100  4653  100  4653    0     0  23034      0 --:--:-- --:--:-- --:--:-- 23034
Error response from daemon: Cannot kill container: 165cce405189: Container 165cce40518901d25a287caad2e3a8daa66eb688ebedc0a1977d630b42d11019 is not running
Error response from daemon: Cannot kill container: dd4a1d74b9de: Container dd4a1d74b9de25ba6d9bc43f6541d49bc56e5cf70eda87132a58020bed688227 is not running
Error response from daemon: Cannot kill container: 3479a9b42545: Container 3479a9b42545243412dea7a61171a11c58130e473ecdc5b38c7d60008b511030 is not running
Error response from daemon: Cannot kill container: ee3b69fcfc02: Container ee3b69fcfc0202c25cd93145ebedc4fcbec854d3df9f2fd7038926c026d25196 is not running
Error response from daemon: Cannot kill container: 1550e68c65e2: Container 1550e68c65e25b702ab2394d7c1b11ecc60de6ef8ccb83e2dce59807d75214ab is not running
Error response from daemon: Cannot kill container: 8c3e1e1337ca: Container 8c3e1e1337caff73e6015f113a3511072f09e9d668d1671ee8ba08ac446d0729 is not running
Error response from daemon: Cannot kill container: 35a696de3fd5: Container 35a696de3fd523d2224c5f527e6be137d0950432285391a7157d32dc1bd97818 is not running
Error response from daemon: Cannot kill container: 94f0663addab: Container 94f0663addab8447c1f428b1cc183825dff5416ee46561fc23f7f031e7bcb4b1 is not running
Error response from daemon: Cannot kill container: b58c1a242f7a: Container b58c1a242f7a187a99d0694a3a528f5e8896cd2e17a3b1c147b24fddd8131888 is not running
Error response from daemon: Cannot kill container: e28b3c270b94: Container e28b3c270b94671ac1ab41c13b06f9c0dfd76a4022756decc689781bcfa8dcbc is not running
Error response from daemon: Cannot kill container: 8147b77e5bf6: Container 8147b77e5bf65e4819419586c0771aabe1125a574b3457c1924d0a25ee333910 is not running
Error response from daemon: Cannot kill container: de13fbcda47e: Container de13fbcda47e79cd9a48551aabe50b85cab116a07bd956d2f348cc304cd88761 is not running
Error response from daemon: Cannot kill container: fad0abf34a2c: Container fad0abf34a2cbd5912c85235f2a7daab665e677b49ca620843a09a17ca798663 is not running
Error response from daemon: Cannot kill container: b8a2f0d3c34a: Container b8a2f0d3c34abce3700b37dbaade83dc17559907f637192e7b0b4236b2c5a594 is not running
Error response from daemon: Cannot kill container: 518228befa18: Container 518228befa18fd25310a7d11abc23625dc98827327b13a866087dfad3170fbcf is not running
Error response from daemon: Cannot kill container: d6885ec6f36d: Container d6885ec6f36d12ddd1e98e35168f09c61be7a1ef24c32d1bddbc7da7e9134fdd is not running