Skip to content

flatpak-proxy: Tell where "Invalid message header format" comes from #38

flatpak-proxy: Tell where "Invalid message header format" comes from

flatpak-proxy: Tell where "Invalid message header format" comes from #38

Triggered via pull request July 20, 2023 11:21
Status Failure
Total duration 1d 7h 15m 35s
Artifacts

check.yml

on: pull_request
Build with Autotools and gcc, and test
0s
Build with Autotools and gcc, and test
Build with Meson and gcc, and test
36s
Build with Meson and gcc, and test
Matrix: Build with clang and analyze
Run tests in valgrind
0s
Run tests in valgrind
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 1 warning
Build with clang and analyze (cpp)
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.
Build with Autotools and gcc, and test
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.
CI checks
The ubuntu-18.04 environment is deprecated, consider switching to ubuntu-20.04(ubuntu-latest), or ubuntu-22.04 instead. For more details see https://github.com/actions/virtual-environments/issues/6002