GUI acceptance tests using environment deployed from packages.

Build: #2027 failed

Job: Oneprovider datasets was successful

Stages & jobs

  1. Acceptance Test

Job result summary

Completed
Duration
21 minutes
Revision
06b7ddbe39e2302126bded895dfde2e9f3fa8004
Total tests
16
Successful since
#1943 ()

Tests

  • 16 tests in total
  • 20 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
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  4653  100  4653    0     0  47000      0 --:--:-- --:--:-- --:--:-- 46530
Error response from daemon: Cannot kill container: bb8ccdeda1c2: Container bb8ccdeda1c2542091d72cab39e921c9017bf189902a0f0fc93a9f06999e5da2 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-CODT/onedata/bamboos'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODT/onedata/cdmi_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODT/onedata/one_env'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODT/onedata/onepanel_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODT/onedata/oneprovider_swagger'...
Cloning into '/mnt/storage/bamboo-agent-home/xml-data/build-dir/ODSRV-GAPT-CODT/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-CODT/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-CODT/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-CODT/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
W0317 08:07:24.053016     443 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  45617      0 --:--:-- --:--:-- --:--:-- 45617
Error response from daemon: Cannot kill container: 121e06776ff7: Container 121e06776ff7a88f5e7ed25b96becc7455a607eeb308f47a996fb85e7925c643 is not running
Error response from daemon: Cannot kill container: df50a1bd07d3: Container df50a1bd07d31a08678416a52cc342494cc1f507b56d9db9e1b46d8c1d0eef43 is not running
Error response from daemon: Cannot kill container: bad66c8eb294: Container bad66c8eb29411fcff6733e0d2b3f15b4e064bf1a18d8886274bb1b4bc92a239 is not running
Error response from daemon: Cannot kill container: cd0222da0bb0: Container cd0222da0bb0688810fd7ba137a0a34261bd318b3ddbe9b698af2e2ea934189f is not running
Error response from daemon: Cannot kill container: 6bb8657839aa: Container 6bb8657839aaa3cf4f79126ed1807399eda63a3d4707139cdd39ba4a622e56a8 is not running
Error response from daemon: Cannot kill container: bf352da0df9e: Container bf352da0df9e1620ebdb181343faefff5d3f1f4a03487d51c89ac685ec6dee2e is not running
Error response from daemon: Cannot kill container: 8d6b34e09563: Container 8d6b34e0956367a7551befd2cb5369208c5c5cc718e156a8e11b94a8198fd00d is not running
Error response from daemon: Cannot kill container: c7693396ff5e: Container c7693396ff5ecf921fd51832432ce46b4e94840d1c38371484a7b8753b43a09c is not running
Error: No such container: c7693396ff5e
Error response from daemon: Cannot kill container: 9ff773563659: No such container: 9ff773563659
Error: No such container: 9ff773563659
Error response from daemon: Cannot kill container: 27c040127cb6: Container 27c040127cb6ddaeaec99f0e26504ae64f859ca037ea90078ebe45b6984c68fb is not running
Error: No such container: 27c040127cb6
Error response from daemon: Cannot kill container: 9496942f97c4: No such container: 9496942f97c4
Error: No such container: 9496942f97c4
Error response from daemon: Cannot kill container: 5a164da5b4c1: No such container: 5a164da5b4c1
Error: No such container: 5a164da5b4c1
Error response from daemon: Cannot kill container: 0fd37b05da4a: No such container: 0fd37b05da4a
Error: No such container: 0fd37b05da4a
Error response from daemon: Cannot kill container: 4180b6f0afec: No such container: 4180b6f0afec
Error: No such container: 4180b6f0afec
Error response from daemon: Cannot kill container: 8d2d75d7a1dc: No such container: 8d2d75d7a1dc
Error: No such container: 8d2d75d7a1dc
Error response from daemon: Cannot kill container: b989269c9a5c: No such container: b989269c9a5c
Error: No such container: b989269c9a5c