GUI acceptance tests using environment deployed from packages.

Build: #2000 was successful

Job: POSIX multiuser was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
14 minutes
Revision
3472d8727468cf978131865efabe3f31a6595f39
Total tests
8
Successful since
#1943 ()

Tests

  • 8 tests in total
  • 13 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  47969      0 --:--:-- --:--:-- --:--:-- 47969
Error response from daemon: Cannot kill container: 717c8d52d682: Container 717c8d52d682f9da730a64f2dda89c7209a79ec023be5aaabe987c8b9c6b76e6 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-CPTM/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CPTM/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CPTM/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CPTM/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CPTM/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CPTM/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-CPTM/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-CPTM/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-CPTM/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
Defaulted container "oneprovider" out of: oneprovider, onezone-registration-token (init)
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
Defaulted container "oneprovider" out of: oneprovider, onezone-registration-token (init)
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
Defaulted container "oneprovider" out of: oneprovider, onezone-registration-token (init)
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
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]
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
W0226 01:04:05.442210     432 warnings.go:70] policy/v1beta1 PodDisruptionBudget is deprecated in v1.21+, unavailable in v1.25+; use policy/v1 PodDisruptionBudget
  % 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  46069      0 --:--:-- --:--:-- --:--:-- 46069
Error response from daemon: Cannot kill container: 72aafe3f8590: Container 72aafe3f859060f1e978934c494e50ebd4827ede9a0757aa30b37dfa8a43689a is not running
Error response from daemon: Cannot kill container: 372ba72dc909: Container 372ba72dc909179e91b8efe5c172c8c5a093aa045fad597e52c4e91792ce2ff2 is not running
Error response from daemon: Cannot kill container: c710c64b38da: Container c710c64b38da794eab7bba209b0249716fc059f901a6ca6086931419229065eb is not running
Error response from daemon: Cannot kill container: bfec68e099ff: Container bfec68e099ff821c6648fd054799630762ab961b7023e93893b60aac8cc80383 is not running
Error response from daemon: Cannot kill container: e065666c7bfd: Container e065666c7bfd44847d73123de0132c551236514aee60e0f3d0075179b520e397 is not running
Error response from daemon: Cannot kill container: 15cd5136f7cd: Container 15cd5136f7cd07cda103667b4400e43d405719bf4479e390883ba64c5f09b47a is not running
Error response from daemon: Cannot kill container: b17b36eb545f: Container b17b36eb545f6fe232b5a67ef51dbcaf932768edc464f34cd7b5177ed8bc7908 is not running
Error response from daemon: Cannot kill container: 1c0a01c68895: Container 1c0a01c68895fdfcf1e09c2e38654d296e152a652333b28dc6573808a0ea0581 is not running
Error response from daemon: Cannot kill container: 1de8bb8ed895: Container 1de8bb8ed895b85476988b82449ad7c123dbf889c7d1a98b9684ce52854472ad is not running
Error response from daemon: Cannot kill container: 26404ef0b689: Container 26404ef0b68957046653122b5bbb119096db88d170030bb46dbe1ee4865fbfa9 is not running
Error response from daemon: Cannot kill container: 2d464a8a8f7a: Container 2d464a8a8f7a6b562c1b2654b7c37a31b56881df5c13c627772be5e74d385fcd is not running
Error response from daemon: Cannot kill container: 560c10e5fc68: Container 560c10e5fc687cb30218efc4836ab03550de5929fd2076678f01a3def3ebbe4d is not running
Error response from daemon: Cannot kill container: b1161d44abbd: Container b1161d44abbddeb7fdada1739b0f53446e7a6bf6a77ad5771ea3770a5b852c37 is not running
Error response from daemon: Cannot kill container: c1ce15ae8d9d: Container c1ce15ae8d9df269b9488cc1c4179b6ba72527d4874566f81a0b93e759e1b839 is not running
Error response from daemon: Cannot kill container: fd70e1d8e95a: Container fd70e1d8e95a8aea3083ece4194a80d71b5334639e57fdd66d94f35548ddd3b6 is not running
Error response from daemon: Cannot kill container: 4039b942f49f: Container 4039b942f49fb0800180442fe4e48366b802044b7113e7f55feddd1b69470e48 is not running