Skip to content

[skia] Avoid linking errors from conflicting fuzz engines #19483

[skia] Avoid linking errors from conflicting fuzz engines

[skia] Avoid linking errors from conflicting fuzz engines #19483

Triggered via pull request November 4, 2025 18:46
Status Failure
Total duration 49m 5s
Artifacts

project_tests.yml

on: pull_request
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

7 errors
build (libfuzzer, memory, x86_64)
Process completed with exit code 143.
build (honggfuzz, address, x86_64)
The hosted runner 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 (libfuzzer, coverage, x86_64)
The hosted runner 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 (afl, address, x86_64)
The hosted runner 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 (libfuzzer, undefined, x86_64)
The hosted runner 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 (libfuzzer, address, x86_64)
The hosted runner 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 (centipede, address, x86_64)
The hosted runner 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.