GUI acceptance tests using environment deployed from packages.

Build: #2236 failed

Job: Chrome metadata test was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
29 minutes
Revision
0211ba80f01c42f60a611d61795cbf5a0fa9dc0c
Total tests
24
Successful since
#2201 ()

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  39769      0 --:--:-- --:--:-- --:--:-- 40112
Error response from daemon: Cannot kill container: cca943312354: Container cca943312354253496a351f8db28186e60c0194e3c7712cee1b114b79b3fd551 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
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
W0720 20:18:16.549845     455 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  40460      0 --:--:-- --:--:-- --:--:-- 40460
Error response from daemon: Cannot kill container: 36c4c5123ea4: Container 36c4c5123ea4bfc1ccfd2cb49be810696556ae20222323fbd6b5693473e5aa62 is not running
Error response from daemon: Cannot kill container: 9b19772b3b22: Container 9b19772b3b22291a16ea2e8438b5629de327b3e8e2af9c8327ca35c8e7c8baf1 is not running
Error response from daemon: Cannot kill container: 1dfa69ac79db: Container 1dfa69ac79db1339358e0e2e7200d4f457a546a77b3a6520671ecc0654940b0f is not running
Error response from daemon: Cannot kill container: 5d4e4b23c1b4: Container 5d4e4b23c1b4021e6b360b2e7a03b2cb868b6670f3eda7f48da93d0af7557905 is not running
Error response from daemon: Cannot kill container: f688aa26302d: Container f688aa26302dc7d6191fda9f8cca04608a979613f6482fe4d49b41bce1481e98 is not running
Error response from daemon: Cannot kill container: def3fa338da3: Container def3fa338da3ae9f59400a43171541631203f92cd61f32fe5d08ad04bc6505b9 is not running
Error response from daemon: Cannot kill container: 426b026e6e2f: Container 426b026e6e2f8d9ee3d8e85a298aab187a7d4ea3608f795d8314c44a47de0653 is not running
Error response from daemon: Cannot kill container: 3f3d566f5bde: Container 3f3d566f5bdef7e2388c724fc282edf2731522fdf1b0ea9d75f2fa8f04292564 is not running
Error response from daemon: Cannot kill container: 667a60b06ebf: Container 667a60b06ebf10fe6ec6bcce482429baa2f0ada6cd8cd8a55d6ae9740d5dbf53 is not running
Error response from daemon: Cannot kill container: 80338b89c6e2: Container 80338b89c6e2fb8130d22719d24db946fb39d452198a249a7d0afabde08d0789 is not running
Error response from daemon: Cannot kill container: 6d6220ba8dfb: Container 6d6220ba8dfb968e618f77c99463e9624b54d0f1b2b1c4fd31df3fbaebb3b6d7 is not running
Error response from daemon: Cannot kill container: af135de1f3e8: Container af135de1f3e8654cda01cdb8083a560fc756ac3f3c2f747c44ada92f8cbdcdeb is not running
Error response from daemon: Cannot kill container: 1bb64b2c9069: Container 1bb64b2c906910b21c314ed1a71dfef0b61fb08a4e467d53b82b17c670151a50 is not running
Error response from daemon: Cannot kill container: 8a27889695d4: Container 8a27889695d49921d460ff64a31ac2cf31a8d7f8ea5e39b2dbfcadd71ec06c17 is not running
Error response from daemon: Cannot kill container: 6b35babf50ba: Container 6b35babf50ba5b0efb2abc791553d53c45486abd76b91f6fd55aac56a9e5a842 is not running
Error response from daemon: Cannot kill container: 9c47fc186f0f: Container 9c47fc186f0fa8005d0a2157c2378185309fed96843e36fefe042b3028f12123 is not running