Fix three causes of spurious shell integration test failures (#32056)

### Description

This fixes three causes of spurious failures of `//src/test/shell/bazel:external_integration_test`:

* `test_deferred_download_smoke` and `test_deferred_download_two_parallel_downloads` serve fixed payloads with a known checksum. Once a run has stored them in a repository cache that outlives it, later runs get them from the cache without contacting the test server, so the test blocks forever writing to the fifo that the server would have read and times out. The payloads now contain a random suffix.
* `test_http_timeout` depends on what the kernel does with connections beyond the listen backlog of the single-threaded test server, whose only handler never returns. Linux and macOS 15 drop them silently, so Bazel reports a connect timeout. On macOS 27, which has SYN cookies enabled by default, the handshake completes and the connection is then reset, so every download attempt fails with "Connection reset by peer" and "timed out" never appears in the log. In `timeout` mode, the server now handles every connection in its own thread so that each attempt times out reading the response.
* Bash builds that use libintl, such as Homebrew's bash 5.3, can crash with SIGSEGV in a forked subshell when they restore their own locale after a temporary assignment such as `LC_ALL=C cmd`, since libintl then looks up the preferred languages through CoreFoundation, which isn't fork-safe. This happens in the `timestamp` function of `unittest.bash`, which then fails the test without any output before `set_up` runs, and in the same way in `generate-xml.sh`. Both now set `LC_ALL` via `env`, which leaves the locale of bash itself untouched.

### Motivation

All three fail locally on macOS 27 with `--test_env=REPOSITORY_CACHE=$(bazel info repository_cache)`: the first two tests every time, the bash crash intermittently. In a stress test, 4 of 48 Homebrew bash processes crashed in every subshell that ran `LC_ALL=C python3 -c pass` in a function, and none did with `env LC_ALL=C`. CI wipes the repository cache before every job, so there the deferred download tests can only hang when a flaky attempt is retried within the same job.

### Build API Changes

No

### Release Notes

RELNOTES: None

Closes #32056

COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/bazel/pull/32056 from fmeum:fix-local-external-test-failures 70c6cdbd450bf2ab16101922009ba5ab2ea950d9
PiperOrigin-RevId: 1007393679
Change-Id: Ib62aabbc5ad716a4650af643af7c4136c9cff56f
4 files changed
tree: e3999ce07f0b47271c83e267caa974316696abe2
  1. .bazelci/
  2. .devcontainer/
  3. .gemini/
  4. .github/
  5. docs/
  6. examples/
  7. scripts/
  8. src/
  9. third_party/
  10. tools/
  11. .bazelrc
  12. .bazelversion
  13. .gitattributes
  14. .gitignore
  15. AGENTS.md
  16. AUTHORS
  17. bazel_downloader.cfg
  18. BUILD
  19. CHANGELOG.md
  20. CODE_OF_CONDUCT.md
  21. CODEOWNERS
  22. combine_distfiles.py
  23. combine_distfiles_to_tar.sh
  24. compile.sh
  25. CONTRIBUTING.md
  26. CONTRIBUTORS
  27. distdir.bzl
  28. extensions.bzl
  29. LICENSE
  30. maven_install.json
  31. MODULE.bazel
  32. MODULE.bazel.lock
  33. oneversion_allowlist.csv
  34. oneversion_allowlist_for_tests.csv
  35. pyproject.toml
  36. README.md
  37. repositories.bzl
  38. requirements.txt
  39. SECURITY.md
  40. verify_module_bazel_lock.sh
README.md

Bazel

{Fast, Correct} - Choose two

Build and test software of any size, quickly and reliably.

  • Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.

  • One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.

  • Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.

  • Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.

Getting Started

Documentation

Reporting a Vulnerability

To report a security issue, please email security@bazel.build with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. Our vulnerability management team will respond within 3 working days of your email. If the issue is confirmed as a vulnerability, we will open a Security Advisory. This project follows a 90 day disclosure timeline.

Contributing to Bazel

See CONTRIBUTING.md

Build status