GUI acceptance tests using environment deployed from packages.

Build: #39 failed

Job: Onepanel deployment basic was successful

Job result summary

Completed
Duration
4 minutes
Revision
0f535bb389921828ff179eaf158e9fc644beba92
Total tests
1
Successful since
#38 ()

Tests

  • 1 test in total
  • 3 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  4419  100  4419    0     0  17620      0 --:--:-- --:--:-- --:--:-- 17676
Error response from daemon: Cannot kill container: 35f734581e89: Container 35f734581e89db1c3e27e8bf16b1aa4d229afe8897cc5bb192b2e20685a6de3e is not running
tput: unknown terminal "unknown"
Cloning into 'bamboos'...
Cloning into 'cdmi_swagger'...
Cloning into 'one_env'...
Cloning into 'onepanel_swagger'...
Cloning into 'bamboos'...
Cloning into 'oneprovider_swagger'...
Cloning into 'bamboos'...
Cloning into 'onezone_swagger'...
Cloning into 'bamboos'...
Error from server (AlreadyExists): clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
Error: Could not create /home/bamboo/.helm: mkdir /home/bamboo/.helm: permission denied
Error from server (AlreadyExists): clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
Error from server (AlreadyExists): clusterrolebindings.rbac.authorization.k8s.io "serviceaccounts-cluster-admin" already exists
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  4419  100  4419    0     0  16909      0 --:--:-- --:--:-- --:--:-- 16931
Error response from daemon: Cannot kill container: 01c07e174e99: Container 01c07e174e999f182367c301fb97f4ed52650f42bae5026332b07f05373a953b is not running
Error response from daemon: Cannot kill container: ed0be0d76367: Container ed0be0d7636776ce9a27336a924890c5492e2d9360fdd4e355fc4f916518a9a3 is not running
Error response from daemon: Cannot kill container: 07aacab8b4e1: Container 07aacab8b4e150ebc971fea6a5ada24835637039b6d9ca1819face7a02c9da52 is not running
Error response from daemon: Cannot kill container: d6fa8073fbd7: Container d6fa8073fbd7ddeba2cbe72def393fec827e1d27f49aedb9b67a964d57693144 is not running
Error response from daemon: Cannot kill container: 6acec17d6891: Container 6acec17d6891c46e775f57469d46e98faa2327d33614081e542be9cb7a6eeebb is not running
Error response from daemon: Cannot kill container: b61cf0201311: Container b61cf0201311719c37cd1320c1cd6c7038c96f0f28ac3e0dca3e31f0c32c706f is not running
Error response from daemon: Cannot kill container: 7a5133fc1fba: Container 7a5133fc1fbab12c59d29c5f651e09c49f8c9e45862875976d1a682a2e010b62 is not running
Error response from daemon: Cannot kill container: 4d485ba8e8fc: Container 4d485ba8e8fc73da075429b6bd6d1d3edd742b9c621e6cde29b72202a3500122 is not running
Error response from daemon: Cannot kill container: 02c449c3788f: Container 02c449c3788f33bc3f2951767c89daa4719da82811cc4c1e98b9c7e58d75b576 is not running