Run Bazel tests in parallel in CI

[wasphin]

What problem does this PR solve?

Issue Number: resolve

Problem Summary:

The Bazel unit-test jobs run independent test binaries serially or without an
explicit concurrency limit. This makes the jobs unnecessarily slow, while
unrestricted concurrency exposes tests that rely on timing, fixed ports, or
process-wide networking state to resource contention.

The Bazel disk-cache fallback can also restore an archive produced by a
different compiler or protobuf configuration. Such an archive consumes cache
transfer time and capacity without producing cache hits.

What is changed and the side effects?

Changed:

• Run the GCC, Clang, and Clang with new protobuf Bazel unit-test jobs with
  --test_output=errors and --local_test_jobs=3.
• Run timing-sensitive tests and tests that manipulate process-wide networking
  state exclusively, while keeping independent test binaries parallel.
• Use ephemeral ports in the interceptor, HTTP expect, endpoint, and oversized
  message tests to avoid conflicts with other processes.
• Set and restore the oversized-message test's maximum body size explicitly.
• Declare the protobuf JSON test as a large Bazel test so its timeout matches
  its existing runtime under CI contention.
• Restrict Bazel disk-cache fallback restoration to caches produced by the
  same CI job.

Side effects:

• Performance effects: reduces Bazel unit-test wall time while limiting local
  test concurrency to avoid overloading GitHub-hosted runners.
• Breaking backward compatibility: No. Production library behavior is
  unchanged; this updates CI scheduling and test robustness.

---

Check List:

• Please make sure your changes are compilable.
• When providing us with a new feature, it is best to add related tests.
• Please follow Contributor Covenant Code of Conduct.

[wwbmmm]

LGTM

[Copilot]

🟢 Approval recommended

The changes are targeted to CI scheduling and test robustness, and the updated test patterns (ephemeral ports, exclusive tags, FlagSaver) are consistent with existing repository practices.

Pull request overview

This PR improves Bazel CI throughput and stability by running unit tests with bounded parallelism and by hardening a set of tests against shared-runner resource conflicts (fixed ports, global flags, and networking state), while also tightening Bazel disk-cache restoration so fallbacks don’t pull incompatible artifacts.

Changes:

• Update Linux Bazel CI jobs to run tests with --test_output=errors and --local_test_jobs=3, and scope disk-cache fallback restores to the same job.
• Tag timing-/network-global-state-sensitive Bazel tests as exclusive, and mark brpc_protobuf_json_unittest as large.
• Make several tests more parallel-safe by using ephemeral ports (Start(0, ...)) and by explicitly scoping gflag mutations with GFLAGS_NAMESPACE::FlagSaver.

File summaries

File	Description
test/endpoint_unittest.cpp	Uses an ephemeral server port and validates against the actual bound address to avoid port collisions under parallel test runs.
test/BUILD.bazel	Adds exclusive tags for contention-sensitive tests and marks a protobuf JSON test as large for CI-timeout alignment.
test/brpc_server_unittest.cpp	Avoids fixed ports and scopes FLAGS_max_body_size mutation to the test via FlagSaver.
test/brpc_interceptor_unittest.cpp	Switches to ephemeral server port and connects via listen_address() to prevent conflicts.
test/brpc_http_rpc_protocol_unittest.cpp	Switches HTTP expect test to an ephemeral port using server.listen_address().
.github/workflows/ci-linux.yml	Runs Bazel unit tests with bounded local concurrency and error-only output across GCC/Clang Bazel test jobs.
.github/actions/setup-build-cache/action.yml	Restricts Bazel disk-cache restore-keys to per-job caches to avoid restoring incompatible archives.

Review details

• Files reviewed: 7/7 changed files
• Comments generated: 0
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.