remove geticeconfig from standard connect state machine flow #1408
Triggered via pull request
November 27, 2023 17:46
jdelapla
Status
Failure
Total duration
6h 0m 35s
Artifacts
–
ci.yml
on: pull_request
clang-format-check
19s
mac-os-build-clang
1h 4m
mac-os-build-gcc
6h 0m
static-build-mac
59m 53s
linux-gcc-code-coverage
44m 59s
address-sanitizer
44m 57s
undefined-behavior-sanitizer
44m 59s
thread-sanitizer
44m 58s
linux-gcc-4_4
44m 57s
static-build-linux
5m 48s
mbedtls-ubuntu-gcc
44m 56s
mbedtls-ubuntu-gcc-11
44m 57s
mbedtls-ubuntu-clang
44m 58s
sample-check
7m 27s
ubuntu-os-build
44m 58s
windows-msvc-openssl
15m 1s
arm64-cross-compilation
3m 47s
linux-aarch64-cross-compilation
4m 2s
arm32-cross-compilation
4m 25s
Annotations
14 errors
|
windows-msvc-openssl
Process completed with exit code 1.
|
|
address-sanitizer
The hosted runner: GitHub Actions 299 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
linux-gcc-4_4
The hosted runner: GitHub Actions 302 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
linux-gcc-code-coverage
The hosted runner: GitHub Actions 300 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
undefined-behavior-sanitizer
The hosted runner: GitHub Actions 303 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
mbedtls-ubuntu-gcc
The hosted runner: GitHub Actions 304 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
mbedtls-ubuntu-gcc-11
The hosted runner: GitHub Actions 305 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
thread-sanitizer
The hosted runner: GitHub Actions 308 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
mbedtls-ubuntu-clang
The hosted runner: GitHub Actions 307 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
ubuntu-os-build
The hosted runner: GitHub Actions 310 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
static-build-mac
The hosted runner: GitHub Actions 301 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
mac-os-build-clang
The hosted runner: GitHub Actions 297 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
mac-os-build-gcc
The job running on runner GitHub Actions 298 has exceeded the maximum execution time of 360 minutes.
|
|
mac-os-build-gcc
The operation was canceled.
|