Skip to content
Build Darwin Framework

Fix the QUIC_HANDSHAKE_INFO Test to Allow for Future Versions to Grow Size (#5032) #4575

Sign in to view logs

Fix the QUIC_HANDSHAKE_INFO Test to Allow for Future Versions to Grow Size (#5032)

Fix the QUIC_HANDSHAKE_INFO Test to Allow for Future Versions to Grow Size (#5032) #4575

Triggered via pull request April 22, 2025 11:23
@nibanksnibanks
synchronize #5036
cp-fix-2.3
Status Failure
Total duration 50m 16s
Artifacts –

build-darwin-framework.yml

on: pull_request
Matrix: Build All Darwin Frameworks (Release) / Build Darwin Binaries
Build All Darwin Frameworks (Release)  /  Build Universal Binaries
0s
Build All Darwin Frameworks (Release) / Build Universal Binaries
Matrix: Build All Darwin Frameworks (Release) / Build Darwin Framework
Build All Darwin Frameworks (Release)  /  Build Darwin XCFramework
0s
Build All Darwin Frameworks (Release) / Build Darwin XCFramework
Fit to window
Zoom out
Zoom in

Annotations

4 errors
Build All Darwin Frameworks (Release) / Build Darwin Binaries (macos, arm64) / Build
The hosted runner: GitHub Actions 125 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.
Build All Darwin Frameworks (Release) / Build Darwin Binaries (ios, x64) / Build
The hosted runner: GitHub Actions 382 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.
Build All Darwin Frameworks (Release) / Build Darwin Binaries (macos, x64) / Build
The hosted runner: GitHub Actions 136 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.
Build All Darwin Frameworks (Release) / Build Darwin Binaries (ios, arm64) / Build
The hosted runner: GitHub Actions 514 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.