GUI acceptance tests using environment deployed from packages.

Build: #2258 was successful

Job: Chrome metadata test was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
2 minutes
Revision
a2577ad5c8df19d48e961bdf05ea5f1feaec71b7
Total tests
1
Successful since
#2201 ()

Configuration changes

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

Tests

  • 1 test in total
  • 1 minute 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  48978      0 --:--:-- --:--:-- --:--:-- 48978
Error response from daemon: Cannot kill container: b1a60cf95319: Container b1a60cf9531959a9295ba7a7c5d32ddb23d21edc0108b69cece524d06fa78118 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
W0811 19:49:27.697631     453 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  40815      0 --:--:-- --:--:-- --:--:-- 41544
Error from server (NotFound): pods "dev-oneprovider-krakow-0" not found
Error response from daemon: Cannot kill container: ae2219fc1d19: Container ae2219fc1d1993b4583938d111c7b57f97c47002d48c255a1eab9cec5f370d54 is not running
Error response from daemon: Cannot kill container: 2e41e3cc31f4: Container 2e41e3cc31f49ed428c3e8d9997d33cc3c4b1b776fc44563f739ce1eebb3fd33 is not running
Error response from daemon: Cannot kill container: bcdc4a34361c: Container bcdc4a34361c070e9ad006ed4aff04d8f75eef26e97a587b0dd4e73c975377c1 is not running
Error response from daemon: Cannot kill container: 7532ec022ce0: Container 7532ec022ce09a75ce2afe80dc538562459ae6f99dfa8ab5cf3f34d9934bd73b is not running
Error response from daemon: Cannot kill container: ccc0aa5efe54: Container ccc0aa5efe5470a88381647b0d21321e607b7560cf37fbda0697a5d7dfed69f5 is not running
Error response from daemon: Cannot kill container: b04d5a02404e: Container b04d5a02404e7dba37a355e3d33d3be27aa18c4ba02cf30c3b51b53724a3fc1d is not running
Error response from daemon: Cannot kill container: 783555f669ab: Container 783555f669ab324ebd808841a92869926ff929388d1b5fab9877aff35ae397c4 is not running
Error response from daemon: Cannot kill container: b862f30953fd: Container b862f30953fda68f7e6b23e99cb5e866313002d1babcb0e613d95fbaad395653 is not running
Error response from daemon: Cannot kill container: 21a50e1f2e3b: Container 21a50e1f2e3b75d423be09db87e9c9c59d0f9f918640d1134b4b10a91e804b6f is not running
Error response from daemon: Cannot kill container: 84ac1649a65e: Container 84ac1649a65e80618ed4e39add88c13bc7bd3b67e345d1159e4024c7c900a3ec is not running
Error response from daemon: Cannot kill container: 7fb6dc02d58d: Container 7fb6dc02d58d8b3f7a3a1e0919e4b449b2a1ab6c1669ffda9bc736dd04dd61c2 is not running
Error response from daemon: Cannot kill container: d74c81aea2b6: Container d74c81aea2b6cd2298a737422454e15245f9c192966bcd003caf16ef9360ecc3 is not running
Error response from daemon: Cannot kill container: a8b486a4abc9: Container a8b486a4abc9a08937ac2c8f914c86835eb8f8ce84b530ef016a2f1b94bbdf74 is not running
Error response from daemon: Cannot kill container: 03f4ecb406eb: Container 03f4ecb406eba4c6420a9d03c48abca84b266bed69bb919fa13144808c68747c is not running
Error response from daemon: Cannot kill container: dd2d7afbe8cc: Container dd2d7afbe8cc204684aecbe68a384fbd272e64a059e6b0a7567925e02844b551 is not running
Error response from daemon: Cannot kill container: ddc15899f444: Container ddc15899f4441fce497c4cb82a04a5b81c02c81d6233b11f8f98e3bde5a6a091 is not running