GUI acceptance tests using environment deployed from packages.

Build: #2274 was successful

Job: Onezone groups multiuser was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
40 minutes
Revision
624ddd1dfa241fb01c10e610d5a920a26351648e
Total tests
23
Successful since
#2201 ()

Tests

  • 23 tests in total
  • 39 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: 841e1e03661e: Container 841e1e03661ecc6c2800aa7554ba944c042fa6e4ad3f4bb1cb2c7e57897a2efb 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-COGMUT/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COGMUT/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COGMUT/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COGMUT/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COGMUT/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-COGMUT/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-COGMUT/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-COGMUT/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-COGMUT/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 00:51:26.044006     437 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  41918      0 --:--:-- --:--:-- --:--:-- 41544
Error response from daemon: Cannot kill container: 8d33e8b9ba00: Container 8d33e8b9ba00d335b275f80b0464d274b77f41f67c81b6204dcf1de7963ebcc6 is not running
Error response from daemon: Cannot kill container: 188b11fde436: Container 188b11fde4361f5dbb9ab31515d7668284e4c5a6133f5db62ed3b8d228cf9ddd is not running
Error response from daemon: Cannot kill container: be9bb8631a15: Container be9bb8631a152a7ca2b5c320f3f92c8cc0d9fef0589ca59de65f65a188d14094 is not running
Error response from daemon: Cannot kill container: 4d19eec664d7: Container 4d19eec664d7307fb7659218c40af499fd7d06345bd9c6b598aa5ec39a15447c is not running
Error response from daemon: Cannot kill container: fd2eb9b45ed6: Container fd2eb9b45ed6ee293ed530d25db71d34bc3f504e627afefe67dbcd220db0624a is not running
Error response from daemon: Cannot kill container: 1c60877ffcb7: Container 1c60877ffcb777534f896198cde99192a478e9341a114752acbd95722d971219 is not running
Error response from daemon: Cannot kill container: 76c711181689: Container 76c711181689586522e800b7655e2c98519a790a54daba12e203365aa87277e0 is not running
Error response from daemon: Cannot kill container: d398473bbbe4: Container d398473bbbe4bef78a82b8afc948dbaf292b77bd87a8547a1570ed3845b7cdf7 is not running
Error response from daemon: Cannot kill container: 39bbe72fab8c: Container 39bbe72fab8c9040b888ce3cccb49c8144743f4b15fbf4d88e51e8450a30e08a is not running
Error response from daemon: Cannot kill container: 402a09f4d933: Container 402a09f4d9334a6dd75d08caf20a7fa09d35b1a1adfe68d63262ce6cbd7b19d4 is not running
Error response from daemon: Cannot kill container: ba474772e553: Container ba474772e5533dc52b1a8a1cb73bb09e2f1cfa9f5c9ee79b2257b0959e911094 is not running
Error response from daemon: Cannot kill container: 4d5ff9289ab5: Container 4d5ff9289ab589181cce092521228a0b70f8cea466e0cf6f9baddd75b85bdb1f is not running
Error response from daemon: Cannot kill container: c09f6dcb1150: Container c09f6dcb115025cfdbb421656746342a5460773ce18256275e9d1699fedb8612 is not running
Error response from daemon: Cannot kill container: 2558bd5ef427: Container 2558bd5ef42785fbfdf91db28a3e297101d26090a459b8ca63165398ba2c3366 is not running
Error response from daemon: Cannot kill container: 4c2bcbdbc6f9: Container 4c2bcbdbc6f9f8c9d4221da8dddc7babe28c4a21e626f18c7753f790a629c782 is not running
Error response from daemon: Cannot kill container: fa9967c07955: Container fa9967c07955c03ff1209324fe372ed136605bfdc1ce52655c964d5934333d87 is not running