Skip to content

Make sure we don't write additional DATA frames when flushing once request is finished #20

Make sure we don't write additional DATA frames when flushing once request is finished

Make sure we don't write additional DATA frames when flushing once request is finished #20

Triggered via pull request November 11, 2024 18:09
Status Failure
Total duration 7m 16s
Artifacts

pull_request.yml

on: pull_request
Soundness  /  API breakage check
3m 30s
Soundness / API breakage check
Soundness  /  Documentation check
2m 49s
Soundness / Documentation check
Soundness  /  Unacceptable language check
5s
Soundness / Unacceptable language check
Soundness  /  License headers check
4s
Soundness / License headers check
Soundness  /  Broken symlinks check
10s
Soundness / Broken symlinks check
Soundness  /  Format check
36s
Soundness / Format check
Soundness  /  Shell check
34s
Soundness / Shell check
Soundness  /  YAML lint check
3s
Soundness / YAML lint check
Soundness  /  Python lint check
5s
Soundness / Python lint check
Soundness  /  Swift license headers check
6s
Soundness / Swift license headers check
Matrix: Cxx Interop / Cxx interop / linux
Matrix: Cxx Interop / Cxx interop / windows-nightly
Matrix: Cxx Interop / Cxx interop / windows
Matrix: Integration Tests / linux
Matrix: Integration Tests / windows-nightly
Matrix: Integration Tests / windows
Matrix: Unit Tests / Unit tests / linux
Matrix: Unit Tests / Unit tests / windows-nightly
Matrix: Unit Tests / Unit tests / windows
Fit to window
Zoom out
Zoom in

Annotations

5 errors
Cxx Interop / Cxx interop / Linux (nightly-main)
Process completed with exit code 1.
Unit Tests / Unit tests / Linux (6.0)
Process completed with exit code 1.
Integration Tests / Linux (nightly-main)
Process completed with exit code 1.
Unit Tests / Unit tests / Linux (nightly-main)
Process completed with exit code 1.
Unit Tests / Unit tests / Linux (nightly-6.0)
Process completed with exit code 1.