GUI acceptance tests using environment deployed from packages.

Build: #2069 was successful

Job: Chrome metadata test was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
19 minutes
Revision
46f0bbcd2738e0f530a00e509bab1d1d7bf6dda0
Total tests
24
Successful since
#1943 ()

Configuration changes

Job Chrome metadata test with key ODSRV-GAPT-MTC no longer exists.

Tests

  • 24 tests in total
  • 18 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  47000      0 --:--:-- --:--:-- --:--:-- 47000
Error response from daemon: Cannot kill container: c69a58fad95e: Container c69a58fad95ed326f238028004da28f3e1b09ffdb766917c8755150859b356f0 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-MTC/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-MTC/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-MTC/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-MTC/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-MTC/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-MTC/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-MTC/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-MTC/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-MTC/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
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
W0401 22:36:32.569767     440 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  41918      0 --:--:-- --:--:-- --:--:-- 41918
Error response from daemon: Cannot kill container: fee10704c994: Container fee10704c99482e9dc95d7760d9ee6494d4ff88c0212a45950c23e707c222d5b is not running
Error response from daemon: Cannot kill container: 5f92e4b169e7: Container 5f92e4b169e75b86b1d2510c2e15c415dda3005714d8ff262aa785186179bba7 is not running
Error response from daemon: Cannot kill container: 064762316f38: Container 064762316f38d0420a5469357bded3ee37de14822e383ab9cdc609cb1cc65c20 is not running
Error response from daemon: Cannot kill container: 6b2cc7d33e9c: Container 6b2cc7d33e9c4c992497a7ba0252f49dad620e56bcc9cb69dee265b69b9686a9 is not running
Error response from daemon: Cannot kill container: 8aff59fa573c: Container 8aff59fa573ce1c80ea146e1d566a728f8e1782191a74259ab687f643b5223dc is not running
Error response from daemon: Cannot kill container: c7079c140ed7: Container c7079c140ed72066d42c80556f37b2c34ba077fca3f1e50e03d4f922cc29a158 is not running
Error response from daemon: Cannot kill container: 542ce53e38f9: Container 542ce53e38f9e2d857d84f12f11a76ed5a36890846cf7ff9b5885fd5150a5096 is not running
Error response from daemon: Cannot kill container: ed0fa0d40979: Container ed0fa0d409793963c3f8aecb945ff50189ff963a4fa85066a6e7e363a5d6c9be is not running
Error response from daemon: Cannot kill container: c47f865e9b48: Container c47f865e9b48ec1f6b529572cfa029fcd150a812b44e0693c265da0ab1928482 is not running
Error response from daemon: Cannot kill container: 07920945c478: Container 07920945c4786062ccde879c1b8a4351024c07c90344e955e8f841e63f4a8323 is not running
Error response from daemon: Cannot kill container: fab2d939b938: Container fab2d939b938e9615b005d74bb4b9bbefe51cd6edff0915ded0044391cc10771 is not running
Error response from daemon: Cannot kill container: 8b1a00c85e07: Container 8b1a00c85e073ce5f35672f340fc0e1b4b759eb681fe7328cebe452155ca4008 is not running
Error response from daemon: Cannot kill container: 58221ef48801: Container 58221ef488014984fa00348c3feefd24567648cc381587fd59c05f62461765e1 is not running
Error response from daemon: Cannot kill container: 2d6151bb884d: Container 2d6151bb884d3ec2c5e76f440c5b0a93f34730c71aa791a6a5ba732793b7ebd9 is not running
Error response from daemon: Cannot kill container: 12fce3d69371: Container 12fce3d693713eeb7bcbede3cc72ca5ff191e68f66a6832816e9dc2f22311d95 is not running
Error response from daemon: Cannot kill container: c1784eee83be: Container c1784eee83be8929ab27c423b3757e966b1558d64035e2075f6e6cafb21906c2 is not running