GUI acceptance tests using environment deployed from packages.

Build: #2048 was successful

Job: Oneprovider datasets privileges was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
19 minutes
Revision
e130ff007745a23f1e4cf9eb99795027a670472c
Total tests
11
Successful since
#2042 ()

Tests

  • 11 tests in total
  • 1 test was quarantined / skipped
  • 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  45617      0 --:--:-- --:--:-- --:--:-- 46069
Error response from daemon: Cannot kill container: b47563b48779: Container b47563b48779c243b2d0510be6f9da249274ecb6133f615efdc55008feac8cf6 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-CODP/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODP/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODP/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODP/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODP/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODP/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-CODP/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-CODP/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-CODP/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
W0324 01:11:14.344854     442 warnings.go:70] policy/v1beta1 PodDisruptionBudget is deprecated in v1.21+, unavailable in v1.25+; use policy/v1 PodDisruptionBudget
cp: cannot stat 'onedata/one_env/sources_info.yaml': No such file or directory
  % 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  48468      0 --:--:-- --:--:-- --:--:-- 48468
Error response from daemon: Cannot kill container: a55c8c90c806: Container a55c8c90c8065251b6af23598469c662743e7c7ddcc042f6c0441075be1d890d is not running
Error response from daemon: Cannot kill container: 67bd121d67da: Container 67bd121d67daa08fdc23355c8099ccfe63a7a851ea8951b1aa04ca6bf54c6d5b is not running
Error response from daemon: Cannot kill container: fdf5e90a67ff: Container fdf5e90a67ffd87b0dea0d00f34dd8a538c0729ad1ba25d8a232c93dd0866a8b is not running
Error response from daemon: Cannot kill container: 7a454b144120: Container 7a454b14412092fc903fac55f072110508e8960357dab5aeb0031b6878d3fff5 is not running
Error response from daemon: Cannot kill container: d1877ad796ea: Container d1877ad796ea9085624e3104cda97dc8dade6ed4cfcea5bc7751727d8e5d3c72 is not running
Error response from daemon: Cannot kill container: 35e969e5b3e0: Container 35e969e5b3e0bf7fa948e684b9c50f72cbc0960a5fb57209b791f06bfa03b785 is not running
Error response from daemon: Cannot kill container: 03fec7146a05: Container 03fec7146a05c8a66060b10a0f6f321fea2ec05263783d52687bb3e137527143 is not running
Error response from daemon: Cannot kill container: 163b0cb8d7e3: Container 163b0cb8d7e3615ffc39fd7dcd4e6cec0196482b483c68a7bec61d53f44e132b is not running
Error response from daemon: Cannot kill container: e8ba47c1ae39: Container e8ba47c1ae391bf0310c16477def0a9cbd2419502386dc9b554324b2eb39934c is not running
Error response from daemon: Cannot kill container: 4468c8282f67: Container 4468c8282f676316c5982754c72b408ae04d4aefe5ea1b50a80d77af96884757 is not running
Error response from daemon: Cannot kill container: 0ba66c27818e: Container 0ba66c27818e1ed81b345eda60e5607cad9b1eb814634691172ddf04690c77c8 is not running
Error response from daemon: Cannot kill container: a158ea77c8e9: Container a158ea77c8e96220bcafc1946a49eafe68bf2b9ff66f825a1259c513c354f561 is not running
Error response from daemon: Cannot kill container: 812b17c97b0c: Container 812b17c97b0c9fef2c22baeb79363054834dde8b340d6c0b859534fd9e322aa2 is not running
Error response from daemon: Cannot kill container: 2b3d4be6be0d: Container 2b3d4be6be0d73635ea587aef3777ab121920f3fd8699faf62340af1fdd53280 is not running
Error response from daemon: Cannot kill container: ae8c9f3c46b2: Container ae8c9f3c46b2767672ec30868d943477aa88d988f22196bdc3190218ec5c6dc9 is not running
Error response from daemon: Cannot kill container: 6f0f4680540d: Container 6f0f4680540d88a519499b238baeeb5d0a6633f698b056b7e3c8d52d4a864c5a is not running