Baseline: 8b453331

Cherry picks:

   + 223113c9:
     Automated rollback of commit
     ae2a6a2d.

Important changes:

  - Adds --experimental_reuse_sandbox_directories flag to reuse
    already-created non-worker sandboxes with cleanup.
  - --experimental_force_gc_after_build is deprecated and will be
    removed soon. Use --bep_publish_used_heap_size_post_build instead
  - Forward coverage-instrumented files from non-tool dependencies by
    default.

This release contains contributions from many people at Google, as well as David Ostrovsky, Johannes Abt, Masoud Koleini, Pras Velagapudi.

*** Reason for rollback ***

Semantics of flags are different, need to unify or keep both flags.

PiperOrigin-RevId: 381873366

Add logging when package loading encounters an exception related to globbing. It's clear from existing logging that globs are the source of the trouble.

This logging pulls its own weight, I think (we should log if we don't immediately throw).

Also cleaned up some interfaces.

PiperOrigin-RevId: 380845241

The Android dexer and command line `Converters` should contain the only remaining
Guava cache references.

PiperOrigin-RevId: 380839417

Targets that should run on Windows but currently broken are listed in yml files and should be looked into, targets that don't run on Windows are marked as "no_windows".

In total, 52 more tests are enabled on Windows.

Related https://github.com/bazelbuild/bazel/issues/4292

RELNOTES: None
PiperOrigin-RevId: 380839138

Eagerly initialize JNI copies of Java classes: doing lazy initialization on a per-method basis doesn't save anything and adds a tiny bit of overhead to every one of these calls.

PiperOrigin-RevId: 380833502

PiperOrigin-RevId: 380816890

PiperOrigin-RevId: 380802339

NDK r19 crosstools incorrectly reported that it supports API level 29.
NDK r21 crosstools was missing API level 30.

Fixes #13421.

PiperOrigin-RevId: 380800055

RELNOTES: None
PiperOrigin-RevId: 380795228

RepoSpec holds information of a repository rule definition, including where the rule class is defined and the attributes of a repository rule. It's the output of Bzlmod resolution and will be used to create a repository rule instance.

Related: https://github.com/bazelbuild/bazel/issues/13316

RELNOTES: None
PiperOrigin-RevId: 380784644

Remote: Fix a bug that the XML generation is executed even if test.xml is generated when build with --remote_download_minimal.

Change test.xml from BasicActionInput to Artifact before executing the spawn so its metadata can be injected.

Use a custom MetadataHandler to allow metadata injections of undeclared outputs.

Fixes #12554.

Closes #12590.

PiperOrigin-RevId: 380741230

PiperOrigin-RevId: 380657997

PiperOrigin-RevId: 380648314

PiperOrigin-RevId: 380637706

PiperOrigin-RevId: 380634599

PiperOrigin-RevId: 380632901

PiperOrigin-RevId: 380579905

PiperOrigin-RevId: 380573067

PiperOrigin-RevId: 380570737

(https://github.com/bazelbuild/bazel/issues/13316)

This SkyFunction performs module discovery by starting out from the root module and iteratively adding direct dependencies into the graph.

PiperOrigin-RevId: 380563418

These got missed in a previous change.

RELNOTES: None
PiperOrigin-RevId: 380559980

These seem to have been slowly migrated away from, finishing that up. This isn't
comprehensive, just cleaning up low hanging fruit.

PiperOrigin-RevId: 380557643

See #13236.

RELNOTES: None.
PiperOrigin-RevId: 380503265

After migrating these packages to shared BUILD files some of the dependencies are
unnecessary and may be removed.

PiperOrigin-RevId: 380384826

PiperOrigin-RevId: 380384598

PiperOrigin-RevId: 380384381

PiperOrigin-RevId: 380384104

Centralize action cache behavior on IOExceptions inside CompactPersistentActionCache. Don't log I/O errors here to remote logging: they are expected from time to time, and these I/O errors are preserved in the failure detail, so we can detect increases in them if there is an issue.

PiperOrigin-RevId: 380257953

Make --bep_publish_used_heap_size_post_build work for query and other non-build commands. Since we want BEP to support query anyway, enabling this flag on query allows it to be a drop-in replacement for --experimental_force_gc_after_build.

PiperOrigin-RevId: 380256260

The concurrency level setting is replaced with an initial capacity setting. This mimics what `ConcurrentHashMap` does.

PiperOrigin-RevId: 380251312

The flakiness was introduced by https://github.com/bazelbuild/bazel/commit/90c395c62742bb038a686d34da57323db665f113. Caffeine has an [undefined eviction policy](https://www.javadoc.io/doc/com.github.ben-manes.caffeine/caffeine/2.8.5/com/github/benmanes/caffeine/cache/Caffeine.html#maximumSize-long-):

> Note that the cache **may evict an entry before this limit is exceeded or temporarily exceed the threshold while evicting**.

Remove assertions on the cache stats and instead just test that subsequent calls are cached.

PiperOrigin-RevId: 380250597

Include the Starlark stack trace as part of the crash's stack trace for all unhandled throwables originating in Starlark evaluation.

In keeping with tradition of not wrapping `Error` in `AbstractParallelEvaluator`, different exception types are used for `RuntimeException` and `Error`.

Additionally embed a context supplier in `StarlarkThread`. This is specifically targeted for the case of a crash during rule analysis, where the call stack itself doesn't include enough information to identify the rule (since the `BUILD` file is evaluated during loading).

PiperOrigin-RevId: 380246681

PiperOrigin-RevId: 380229840

This changes the default behavior for coverage from "forward nothing" to "forward InstrumentedFilesInfo from non-tool dependencies". This is still not quite ideal behavior, since typically attributes which provide source files (like srcs) are non-tool dependencies. But it's an improvement because it avoids the need for explicit coverage configuration for the entire chain of dependencies from test to source file.

In cases where an aspect returned InstrumentedFilesInfo previously, the InstrumentedFilesInfo provider for the base rule is ignored, so the behavior will be unchanged.

The bit about coverage_common.instrumented_files_info is merged into the related section under "Advanced Topics" in the rules documentation, since it's no longer required for the whole dependency chain to configure coverage explicitly in order for that to work at all.

RELNOTES: Forward coverage-instrumented files from non-tool dependencies by default.
PiperOrigin-RevId: 380224680

(https://github.com/bazelbuild/bazel/issues/13316)

We're "denormalizing" the override API: whereas you'd write "override_dep(name='X', Y_override(...))" before, you'd now write "Y_override(module_name='X', ...)".

PiperOrigin-RevId: 380173439

(https://github.com/bazelbuild/bazel/issues/13316)

This CL implements ModuleFileFunction, a SkyFunction that takes the name and version of a module, finds and evaluates its MODULE.bazel file and returns the evaluated result.

This is not hooked into the main SkyFrame route yet (RepositoryDelegatorFunction has yet to call this).

PiperOrigin-RevId: 380141062

PiperOrigin-RevId: 380118631

PiperOrigin-RevId: 380094180

PiperOrigin-RevId: 380093830