Skip to content

Nightly

Nightly #50

Triggered via schedule July 1, 2024 01:29
Status Failure
Total duration 36m 51s
Artifacts 17

nightly.yml

on: schedule
Matrix: build-test / docker-test / Test Docker Selenium
Matrix: build-test / helm-chart-test / Test K8s
Nightly build
0s
Nightly build
Fit to window
Zoom out
Zoom in

Annotations

24 errors and 18 warnings
build-test / docker-test / Test Docker Selenium (test, false, false, true)
Final attempt failed. Child_process exited with error code 2
build-test / docker-test / Test Docker Selenium (test, true, false, true)
Final attempt failed. Child_process exited with error code 2
build-test / docker-test / Test Docker Selenium (test_node_docker, false, true, false)
Final attempt failed. Child_process exited with error code 2
build-test / docker-test / Test Docker Selenium (test_video, false, true, false)
Final attempt failed. Child_process exited with error code 2
build-test / docker-test / Test Docker Selenium (test_node_relay, false, false, false)
Exception: Message: Could not start a new session. Could not start a new session. Error while creating session with the service http://emulator:4723. Could not start a new session. Response code 500. Message: An unknown server-side error occurred while processing the command. Original error: Could not find a connected Android device in 20000ms
build-test / docker-test / Test Docker Selenium (test_node_relay, false, false, false)
Exception: Message: Could not start a new session. Could not start a new session. Error while creating session with the service http://emulator:4723. Could not start a new session. Response code 500. Message: An unknown server-side error occurred while processing the command. Original error: Could not find a connected Android device in 20000ms
build-test / docker-test / Test Docker Selenium (test_node_relay, false, false, false)
Exception: Message: Could not start a new session. Could not start a new session. Error while creating session with the service http://emulator:4723. Could not start a new session. Response code 500. Message: An unknown server-side error occurred while processing the command. Original error: Could not find a connected Android device in 20000ms
build-test / docker-test / Test Docker Selenium (test_node_relay, false, false, false)
Exception: Message: Could not start a new session. Could not start a new session. Error while creating session with the service http://emulator:4723. Could not start a new session. Response code 500. Message: An unknown server-side error occurred while processing the command. Original error: Could not find a connected Android device in 20000ms
build-test / docker-test / Test Docker Selenium (test_node_relay, false, false, false)
Exception: Message: Could not start a new session. Could not start a new session. Error while creating session with the service http://emulator:4723. Could not start a new session. Response code 500. Message: An unknown server-side error occurred while processing the command. Original error: Could not find a connected Android device in 20000ms
build-test / docker-test / Test Docker Selenium (test_node_relay, false, false, false)
Exception: Message: Could not start a new session. Could not start a new session. Error while creating session with the service http://emulator:4723. Could not start a new session. Response code 500. Message: An unknown server-side error occurred while processing the command. Original error: Could not find a connected Android device in 20000ms
build-test / docker-test / Test Docker Selenium (test_node_relay, false, false, false)
Final attempt failed. Child_process exited with error code 2
build-test / helm-chart-test / Test K8s (v1.25.16, disabled, minikube, v3.10.3, false, true)
Final attempt failed. Child_process exited with error code 2
build-test / docker-test / Test Docker Selenium (test_parallel, false, false, false)
Final attempt failed. Child_process exited with error code 2
build-test / docker-test / Test Docker Selenium (test_video_dynamic_name, false, true, false)
Final attempt failed. Child_process exited with error code 2
build-test / helm-chart-test / Test K8s (v1.28.11, job_https, minikube, v3.13.3, true, true)
Exception: Message: Could not start a new session. Unable to create new session
build-test / helm-chart-test / Test K8s (v1.28.11, job_https, minikube, v3.13.3, true, true)
Exception: Message: Could not start a new session. Unable to create new session
build-test / helm-chart-test / Test K8s (v1.28.11, job_https, minikube, v3.13.3, true, true)
Exception: Message: Could not start a new session. Unable to create new session
build-test / helm-chart-test / Test K8s (v1.26.15, job, minikube, v3.11.3, true, true)
Exception: Message: Could not start a new session. Could not start a new session. Unable to create new session
build-test / helm-chart-test / Test K8s (v1.30.2, deployment_https, minikube, v3.15.2, false, true)
Exception: Message: Could not start a new session. Could not start a new session. java.util.concurrent.TimeoutException
build-test / helm-chart-test / Test K8s (v1.30.2, deployment_https, minikube, v3.15.2, false, true)
Exception: Message: Could not start a new session. Could not start a new session. java.util.concurrent.TimeoutException
build-test / helm-chart-test / Test K8s (v1.30.2, deployment_https, minikube, v3.15.2, false, true)
Final attempt failed. Child_process exited with error code 2
build-test / docker-test / Test Docker Selenium (test, false, false, true)
Attempt 1 failed. Reason: Child_process exited with error code 2
build-test / docker-test / Test Docker Selenium (test, true, false, true)
Attempt 1 failed. Reason: Child_process exited with error code 2
build-test / docker-test / Test Docker Selenium (test_node_docker, false, true, false)
Attempt 1 failed. Reason: Child_process exited with error code 2
build-test / docker-test / Test Docker Selenium (test_video, false, true, false)
Attempt 1 failed. Reason: Child_process exited with error code 2
build-test / docker-test / Test Docker Selenium (test_node_relay, false, false, false)
Attempt 1 failed. Reason: Child_process exited with error code 2
build-test / helm-chart-test / Test K8s (v1.29.6, job_hostname, minikube, v3.14.4, false, true)
Number of failed tests: 3. All tests passed in rerun!
build-test / helm-chart-test / Test K8s (v1.25.16, disabled, minikube, v3.10.3, false, true)
Attempt 1 failed. Reason: Child_process exited with error code 2
build-test / helm-chart-test / Test K8s (v1.25.16, disabled, minikube, v3.10.3, false, true)
Attempt 2 failed. Reason: Child_process exited with error code 2
build-test / helm-chart-test / Test K8s (v1.25.16, disabled, minikube, v3.10.3, false, true)
No files were found with the provided path: ./tests/videos/. No artifacts will be uploaded.
build-test / docker-test / Test Docker Selenium (test_parallel, false, false, false)
Attempt 1 failed. Reason: Child_process exited with error code 2
build-test / docker-test / Test Docker Selenium (test_video_dynamic_name, false, true, false)
Attempt 1 failed. Reason: Child_process exited with error code 2
build-test / helm-chart-test / Test K8s (v1.28.11, job_https, minikube, v3.13.3, true, true)
Attempt 1 failed. Reason: Child_process exited with error code 2
build-test / helm-chart-test / Test K8s (v1.28.11, job_https, minikube, v3.13.3, true, true)
Number of failed tests: 3. All tests passed in rerun!
build-test / helm-chart-test / Test K8s (v1.27.15, deployment, minikube, v3.12.3, true, true)
Attempt 1 failed. Reason: Child_process exited with error code 2
build-test / helm-chart-test / Test K8s (v1.27.15, deployment, minikube, v3.12.3, true, true)
Number of failed tests: 3. All tests passed in rerun!
build-test / helm-chart-test / Test K8s (v1.26.15, job, minikube, v3.11.3, true, true)
Number of failed tests: 4. All tests passed in rerun!
build-test / helm-chart-test / Test K8s (v1.30.2, deployment_https, minikube, v3.15.2, false, true)
Attempt 1 failed. Reason: Child_process exited with error code 2
build-test / helm-chart-test / Test K8s (v1.30.2, deployment_https, minikube, v3.15.2, false, true)
Attempt 2 failed. Reason: Child_process exited with error code 2

Artifacts

Produced during runtime
Name Size
v1.25.16-disabled-artifacts
78.5 KB
v1.25.16-disabled_selenium-grid-4.22.0-20240701.tgz
1010 KB
v1.26.15-job-artifacts
37.9 MB
v1.26.15-job-videos
12.2 MB
v1.26.15-job_selenium-grid-4.22.0-20240701.tgz
1010 KB
v1.27.15-deployment-artifacts
6.25 MB
v1.27.15-deployment-videos
2.68 MB
v1.27.15-deployment_selenium-grid-4.22.0-20240701.tgz
1010 KB
v1.28.11-job_https-artifacts
63.5 KB
v1.28.11-job_https-videos
12.1 MB
v1.28.11-job_https_selenium-grid-4.22.0-20240701.tgz
1000 KB
v1.29.6-job_hostname-artifacts
125 KB
v1.29.6-job_hostname-videos
10.4 MB
v1.29.6-job_hostname_selenium-grid-4.22.0-20240701.tgz
1000 KB
v1.30.2-deployment_https-artifacts
233 KB
v1.30.2-deployment_https-videos
4.28 MB
v1.30.2-deployment_https_selenium-grid-4.22.0-20240701.tgz
1010 KB