GUI acceptance tests using environment deployed from packages.

Build: #2649 failed

Job: Multiprovider multiuser failed

Stages & jobs

  1. Qnthack - copy quarantine

  2. Acceptance Test

  3. Qnthack - rerun

Job result summary

Completed
Duration
1 second
Revision
02706be832f728a75a8ea911b7a36e801b34db26
Fixed in
#2650 (Manual run by Michał Borzęcki)
No failed test found. A possible compilation error occurred.

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  4822  100  4822    0     0  50229      0 --:--:-- --:--:-- --:--:-- 50757
docker: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?.
See 'docker run --help'.
Error: Kubernetes cluster unreachable: Get "http://localhost:8080/version?timeout=32s": dial tcp 127.0.0.1:8080: connect: connection refused
The connection to the server localhost:8080 was refused - did you specify the right host or port?
The connection to the server localhost:8080 was refused - did you specify the right host or port?
The connection to the server localhost:8080 was refused - did you specify the right host or port?
The connection to the server localhost:8080 was refused - did you specify the right host or port?
The connection to the server localhost:8080 was refused - did you specify the right host or port?
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
docker: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?.
See 'docker run --help'.
error: current-context is not set
error: no context exists with the name: "minikube"
rm: cannot remove '/home/bamboo/.kube/config': No such file or directory
timeout: failed to run command ‘minikube’: No such file or directory
Job for docker.service failed.
See "systemctl status docker.service" and "journalctl -xe" for details.
Job failed. See "journalctl -xe" for details.
A dependency job for docker.service failed. See 'journalctl -xe' for details.
sudo: minikube: command not found
sudo: minikube: command not found
sudo: minikube: command not found
sudo: minikube: command not found
cp: cannot stat 'onedata-acceptance/test-reports/*.xml': No such file or directory
cp: cannot stat 'onedata-acceptance/one_env/sources_info.yaml': No such file or directory
mv: cannot stat 'onedata-acceptance/tests/gui/logs/report.*': No such file or directory
mv: cannot stat 'onedata-acceptance/tests/gui/logs/gui_report/images.yaml': No such file or directory