GUI acceptance tests using environment deployed from packages.

Build: #2059 was successful

Job: Chrome metadata test was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
29 minutes
Revision
193b4f47a9a0cf118cdd02f18225a0c3d5b1e2a1
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
  • 28 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  40815      0 --:--:-- --:--:-- --:--:-- 40815
Error response from daemon: Cannot kill container: e2bb4b0f18e6: Container e2bb4b0f18e6bd0ed12d7926da575cbd76bb7517c5d9f240f7800c1863a4b5ab 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
W0328 13:08:51.906702     433 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  39100      0 --:--:-- --:--:-- --:--:-- 39100
Error from server (NotFound): pods "dev-oneprovider-krakow-0" not found
Error response from daemon: Cannot kill container: 30b217b4fc8b: Container 30b217b4fc8b21391f4100e71a3ee9f9db74fe972ded6967a9bbcbe2e54186f1 is not running
Error response from daemon: Cannot kill container: ee9b3e4156e3: Container ee9b3e4156e3fb582108efb208830e50d717f3c3b09d4bca8df5929798aad3e0 is not running
Error response from daemon: Cannot kill container: fa3b4d4e2958: Container fa3b4d4e2958b8fcfc78627340291d2aec4da240c158860631bf3477486b2bbe is not running
Error response from daemon: Cannot kill container: 0df3eb4d78a3: Container 0df3eb4d78a3c2e55f2dd74256f8d0511f9bc5efc1aa18660a5534ac62000b9b is not running
Error response from daemon: Cannot kill container: 439a0a407597: Container 439a0a4075974cf329137934e2c8753d07c9844f0e0787c51fc7c73e3dd0b5e2 is not running
Error response from daemon: Cannot kill container: 1d82b05631d3: Container 1d82b05631d361f92853976899d65e0640e0d93e7329ecfb28251109e3da4e23 is not running
Error response from daemon: Cannot kill container: a317e74161e5: Container a317e74161e578f4561da9400fa33528786f6b6b5143e546f8b3d04608b020ec is not running
Error response from daemon: Cannot kill container: eb0be79c18d4: Container eb0be79c18d4691f6c090a7cf17bd1b15fccb459780db318c54ab67cfa9b7137 is not running
Error response from daemon: Cannot kill container: 7d1da5f517d0: Container 7d1da5f517d05376491ce20c99043c7f02cbce320436675776f60a5bc1931cc2 is not running
Error response from daemon: Cannot kill container: f053ed818265: Container f053ed8182657a9548bb3f428dbdb549e92c99b079c6bf77bd256ab1d73b353a is not running
Error response from daemon: Cannot kill container: 46ea94c9c0fc: Container 46ea94c9c0fc25756f97358303f107bcdfed823248c4101ae7f608e3c03e87c6 is not running
Error response from daemon: Cannot kill container: a0197315d214: Container a0197315d214ef5d7bc956d0ef1f6497c4532d53819ba4c9f6b245bbc1a0f87b is not running
Error response from daemon: Cannot kill container: 7b24411ec98f: Container 7b24411ec98f891cad231abb2af5c166b67f378687cdc759f6375d6e9b60f505 is not running
Error response from daemon: Cannot kill container: 6637f7480683: Container 6637f748068378287404e2588e44fc8c279dec06ba11c89434c6b5913c2b3724 is not running
Error response from daemon: Cannot kill container: 29a8e912872a: Container 29a8e912872a9ca3e4d9527dead6261ba36af6333810ff083e419651f1b40fcb is not running
Error response from daemon: Cannot kill container: aea520cd9f2f: Container aea520cd9f2f21e06d52ec75292273d38a79cdf164c1945f827f2e637d08c5f4 is not running