Skip to content
Bazel (experimental)

Recover browser MCP calls after broken-pipe transport failures #10891

Sign in to view logs

Recover browser MCP calls after broken-pipe transport failures

Recover browser MCP calls after broken-pipe transport failures #10891

Triggered via pull request February 28, 2026 03:37
@swordfish444swordfish444
opened #13100
swordfish444:codex/mcp-transport-recovery
Status Failure
Total duration 38m 14s
Artifacts –

bazel.yml

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

Annotations

4 errors and 4 warnings
Local Bazel build on macos-15-xlarge for x86_64-apple-darwin
Process completed with exit code 1.
Local Bazel build on macos-15-xlarge for aarch64-apple-darwin
Process completed with exit code 1.
Local Bazel build on ubuntu-24.04 for x86_64-unknown-linux-gnu
Process completed with exit code 1.
Local Bazel build on ubuntu-24.04 for x86_64-unknown-linux-musl
Process completed with exit code 1.
Local Bazel build on macos-15-xlarge for x86_64-apple-darwin
Failed to restore: Cache service responded with 400
Local Bazel build on macos-15-xlarge for aarch64-apple-darwin
Failed to restore: Cache service responded with 400
Local Bazel build on ubuntu-24.04 for x86_64-unknown-linux-gnu
Failed to restore: Cache service responded with 400
Local Bazel build on ubuntu-24.04 for x86_64-unknown-linux-musl
Failed to restore: Cache service responded with 400