add: secure connection for docker compose #1925
VietND96build-test.yml
on: pull_request
Matrix: Test Seleium Grid on Docker / Test Docker Selenium
Matrix: Test Selenium Grid on Kubernetes / Test K8s
Rerun workflow when failure
10s
Annotations
13 errors and 8 warnings
|
Test Seleium Grid on Docker / 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
|
|
Test Seleium Grid on Docker / 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
|
|
Test Seleium Grid on Docker / 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
|
|
Test Seleium Grid on Docker / 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
|
|
Test Seleium Grid on Docker / 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
|
|
Test Seleium Grid on Docker / 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
|
|
Test Seleium Grid on Docker / 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
|
|
Test Seleium Grid on Docker / 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
|
|
Test Seleium Grid on Docker / 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
|
|
Test Seleium Grid on Docker / 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
|
|
Test Selenium Grid on Kubernetes / Test K8s (v1.26.15, job, minikube, v3.11.3, true, true)
Exception: Message: java.util.concurrent.TimeoutException
|
|
Test Seleium Grid on Docker / Test Docker Selenium (test_node_docker, false, true, false)
System.IO.IOException: No space left on device : '/home/runner/runners/2.317.0/_diag/Worker_20240809-174537-utc.log'
at System.IO.RandomAccess.WriteAtOffset(SafeFileHandle handle, ReadOnlySpan`1 buffer, Int64 fileOffset)
at System.IO.Strategies.BufferedFileStreamStrategy.FlushWrite()
at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder)
at System.Diagnostics.TextWriterTraceListener.Flush()
at GitHub.Runner.Common.HostTraceListener.WriteHeader(String source, TraceEventType eventType, Int32 id)
at GitHub.Runner.Common.HostTraceListener.TraceEvent(TraceEventCache eventCache, String source, TraceEventType eventType, Int32 id, String message)
at System.Diagnostics.TraceSource.TraceEvent(TraceEventType eventType, Int32 id, String message)
at GitHub.Runner.Worker.Worker.RunAsync(String pipeIn, String pipeOut)
at GitHub.Runner.Worker.Program.MainAsync(IHostContext context, String[] args)
System.IO.IOException: No space left on device : '/home/runner/runners/2.317.0/_diag/Worker_20240809-174537-utc.log'
at System.IO.RandomAccess.WriteAtOffset(SafeFileHandle handle, ReadOnlySpan`1 buffer, Int64 fileOffset)
at System.IO.Strategies.BufferedFileStreamStrategy.FlushWrite()
at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder)
at System.Diagnostics.TextWriterTraceListener.Flush()
at GitHub.Runner.Common.HostTraceListener.WriteHeader(String source, TraceEventType eventType, Int32 id)
at GitHub.Runner.Common.HostTraceListener.TraceEvent(TraceEventCache eventCache, String source, TraceEventType eventType, Int32 id, String message)
at System.Diagnostics.TraceSource.TraceEvent(TraceEventType eventType, Int32 id, String message)
at GitHub.Runner.Common.Tracing.Error(Exception exception)
at GitHub.Runner.Worker.Program.MainAsync(IHostContext context, String[] args)
Unhandled exception. System.IO.IOException: No space left on device : '/home/runner/runners/2.317.0/_diag/Worker_20240809-174537-utc.log'
at System.IO.RandomAccess.WriteAtOffset(SafeFileHandle handle, ReadOnlySpan`1 buffer, Int64 fileOffset)
at System.IO.Strategies.BufferedFileStreamStrategy.FlushWrite()
at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder)
at System.Diagnostics.TextWriterTraceListener.Flush()
at System.Diagnostics.TraceSource.Flush()
at GitHub.Runner.Common.TraceManager.Dispose(Boolean disposing)
at GitHub.Runner.Common.TraceManager.Dispose()
at GitHub.Runner.Common.HostContext.Dispose(Boolean disposing)
at GitHub.Runner.Common.HostContext.Dispose()
at GitHub.Runner.Worker.Program.Main(String[] args)
|
|
Rerun workflow when failure
Process completed with exit code 1.
|
|
Test Selenium Grid on Kubernetes / Test K8s (v1.27.16, deployment, minikube, v3.12.3, true, true)
Attempt 1 failed. Reason: Child_process exited with error code 2
|
|
Test Selenium Grid on Kubernetes / Test K8s (v1.27.16, deployment, minikube, v3.12.3, true, true)
Attempt 2 failed. Reason: Child_process exited with error code 2
|
|
Test Seleium Grid on Docker / Test Docker Selenium (test_node_relay, false, false, false)
Attempt 1 failed. Reason: Child_process exited with error code 2
|
|
Test Seleium Grid on Docker / Test Docker Selenium (test_parallel, false, false, false)
Number of failed tests: 5. All tests passed in rerun!
|
|
Test Seleium Grid on Docker / Test Docker Selenium (test_parallel, false, false, false)
Number of failed tests: 5. All tests passed in rerun!
|
|
Test Selenium Grid on Kubernetes / Test K8s (v1.26.15, job, minikube, v3.11.3, true, true)
Number of failed tests: 1. All tests passed in rerun!
|
|
Test Seleium Grid on Docker / Test Docker Selenium (test_node_docker, false, true, false)
You are running out of disk space. The runner will stop working when the machine runs out of disk space. Free space left: 39 MB
|
|
Test Seleium Grid on Docker / Test Docker Selenium (test_node_docker, false, true, false)
Attempt 1 failed. Reason: Timeout of 1200000ms hit
|
Artifacts
Produced during runtime
| Name | Size | |
|---|---|---|
|
test_video_artifacts
Expired
|
3.17 MB |
|
|
test_video_dynamic_name_artifacts
Expired
|
2.77 MB |
|
|
v1.25.16-disabled-artifacts
Expired
|
66.9 KB |
|
|
v1.25.16-disabled-videos
Expired
|
3.73 MB |
|
|
v1.25.16-disabled_selenium-grid-4.24.0-SNAPSHOT-20240809.tgz
Expired
|
1.09 MB |
|
|
v1.26.15-job-artifacts
Expired
|
101 KB |
|
|
v1.26.15-job-videos
Expired
|
3.58 MB |
|
|
v1.26.15-job_selenium-grid-4.24.0-SNAPSHOT-20240809.tgz
Expired
|
1.09 MB |
|
|
v1.27.16-deployment-artifacts
Expired
|
90.2 KB |
|
|
v1.27.16-deployment-videos
Expired
|
3.64 MB |
|
|
v1.27.16-deployment_selenium-grid-4.24.0-SNAPSHOT-20240809.tgz
Expired
|
1.09 MB |
|
|
v1.28.12-job_https-artifacts
Expired
|
42.5 KB |
|
|
v1.28.12-job_https-videos
Expired
|
4.12 MB |
|
|
v1.28.12-job_https_selenium-grid-4.24.0-SNAPSHOT-20240809.tgz
Expired
|
1.09 MB |
|
|
v1.29.7-job_hostname-artifacts
Expired
|
127 KB |
|
|
v1.29.7-job_hostname-videos
Expired
|
4.01 MB |
|
|
v1.29.7-job_hostname_selenium-grid-4.24.0-SNAPSHOT-20240809.tgz
Expired
|
1.09 MB |
|
|
v1.30.3-deployment_https-artifacts
Expired
|
167 KB |
|
|
v1.30.3-deployment_https-videos
Expired
|
3.78 MB |
|
|
v1.30.3-deployment_https_selenium-grid-4.24.0-SNAPSHOT-20240809.tgz
Expired
|
1.09 MB |
|