Baseline: b00576de

Cherry picks:

   + a8e2c586:
     Throw toolchain resolution error (as EvalError) instead of
     IllegalStateException if create_compile_action() is called for
     an action that isn't configured for the toolchain.

This release contains contributions from many people at Google, as well as .

Throw toolchain resolution error (as EvalError) instead of IllegalStateException if create_compile_action() is called for an action that isn't configured for the toolchain.

PiperOrigin-RevId: 705135234
Change-Id: Iffaf819e9b59cc4925aa7bd14ce5c3f529664b1b

This fixes a few issues introduced in 282ac623:
* Only the executable path in the first argument of a `CommandLines` instance should be subject to path mapping.
* String arguments that are not normalized as path strings and thus can't possibly be the optimized memory representation used for the executable arg by `StarlarkAction` should not be modified.

Also removes an class that became unused in that commit.

Closes #24576.

PiperOrigin-RevId: 703536848
Change-Id: I358696bc268ab1f400798ef55ea4db8d556f07dd

Nothing is using this anymore.

PiperOrigin-RevId: 703536745
Change-Id: I97f6e6e2ca439027839bd41c1599524795d7b146

- Ensure that rewriter.py also processes generated docs in order to set metadata required by the version selector
- Enable version selector for the command line reference

PiperOrigin-RevId: 703532562
Change-Id: I77664bd6e14b59d2ef0b749f85a52a09c291f6e8

*** Reason for rollback ***

Rollforward with fixes

Preserve analysis cache through `--run_under` command changes

Work towards https://github.com/bazelbuild/bazel/issues/3325
Fixes https://github.com/bazelbuild/bazel/issues/10782

RELNOTES: Changing any part of --run_under that isn't the label (such as the shell command) no longer invalidates the analysis cache.

Closes #24411.

PiperOrigin-RevId: 703516108
Change-Id: Ief9bd2547fe87b4c09b132ada87aed369753e550

Fixes #24578.

PiperOrigin-RevId: 703513880
Change-Id: I3f95a92ead3e64007974e45362185738b5927cee

Fix the "Error Prone: Specify a Locale when calling String#to{Lower,Upper}Case" warning in Resolver.

PiperOrigin-RevId: 703499448
Change-Id: I683e74db4602666ba93aba4433d31d0399056fd4

If this is used from a WORKSPACE, or used in bzlmod with the repo name
overridden to the old name, rules_apple isn't correct for this
allowlist.

Closes #24582.

PiperOrigin-RevId: 703493907
Change-Id: Ie4f88de60775c50874169e4fb5712b7b5fe8b8bd

These are implementation details of the unix package, and shouldn't be depended upon by anything else.

PiperOrigin-RevId: 703486528
Change-Id: I08b50b847eaed0b08b171b158af3862216929fd8

This is a thread-safe pattern since C++11.

PiperOrigin-RevId: 703478162
Change-Id: I595bfaf61bf29d0fcf799ada1335e57d31ca9045

PiperOrigin-RevId: 703468738
Change-Id: I9f98fd4a584d1c2a1d927ad0edf7c43b1fad641a

By making UnixFileStatus an implementation of FileStatus. Also remove unused fields and methods from the former.

PiperOrigin-RevId: 703463721
Change-Id: Icf31c8e834eccab38df13d0cfdb833a7313ea8a7

Instead, pass the stat/lstat error handling mode to JNI and do the right thing there. This simplifies both the JNI and Java sides.

PiperOrigin-RevId: 703436541
Change-Id: Iadca939712c861cf5902e79bd1d4bd6a975a1c40

Included module file segments already had to have a `.MODULE.bazel` suffix, but this wasn't documented. Also prohibit a filename starting with a `.`, which would hide the file on Unix.

Closes #24575.

PiperOrigin-RevId: 703417032
Change-Id: Idc87e0012f42d5ba9b0e6c5a5a7be9294f99f636

This guards against an ineffective `null` check in the JDK.

Also use `getCpuLoad()` instead of `getSystemCpuLoad()` as the latter has been deprecated.

Fixes #24519

Closes #24569.

PiperOrigin-RevId: 703413335
Change-Id: I66189d7e44962363be8a0c36496ce89fd388b9c9

This requires patching rules_graalvm with https://github.com/sgammon/rules_graalvm/pull/514 to ensure the native image runs with `sun.jnu.encoding` set to `UTF-8` on Linux.

Also enable unrelated tests after the recent java_tools update.

Work towards #24444
Unblocks #24457

Closes #24565.

PiperOrigin-RevId: 703409662
Change-Id: I44de4387de4a6da404436f5a35a2b27274122bbb

Log the actual evaluating version on top of the byte-array representation of the FrontierNodeVersion components.

PiperOrigin-RevId: 703330045
Change-Id: I7b2746ac068669c07641fb2f659e090c9e467190

Use sharing for its BuildConfigurationKey. Inlining it is expensive.

PiperOrigin-RevId: 703309002
Change-Id: Ie12a33f1e131612b068dbbdfd66997ab450f01af

Introduce a `recursiveCreateParentDirectory` flag to `LocalInstrumentationOutput` so that it can optionally create non-existing parent directory of an output.

PiperOrigin-RevId: 703258799
Change-Id: I712098788b82f97a109063c4c52bdc6a451b0bf9

Follow-up fix to https://github.com/bazelbuild/bazel/commit/59e99b67533ebc5375cca98bc95ec0b74c4d4a69

PiperOrigin-RevId: 703255080
Change-Id: I1055c4c8b7e2e627199bdca9e2daab5654102831

PiperOrigin-RevId: 703230851
Change-Id: I406086a9f4e03c4f0f8ba413c18587f2ae0997eb

RELNOTES: None
PiperOrigin-RevId: 703221309
Change-Id: Ie7a4607b530a01e49f671bc6804a307740c81175

We can no longer prevent code being tested from exiting when `System.exit` is called, but we can at least show where it happened. We do this by the examining the stack traces of all threads in a shutdown hook, looking for `Runtime.exit`. (`System.exit` calls `Runtime.exit`, and users can also call it directly.)

We cannot detect `Runtime.halt` this way, unfortunately.

Recent JDK versions can be configured to log where `System.exit` is called, but that logging is fiddly and its configuration may interfere with that of the code under test. Also, we may later add to the shutdown hook so that it also detects which test method is currently executing, in case that isn't in the thread that called `System.exit`.

PiperOrigin-RevId: 703190140
Change-Id: Ie4ba4728c41adb868f7fc75b630851b900e7e27d

Avoids contention when the metadata is already available, which is the common case.

PiperOrigin-RevId: 703126528
Change-Id: Ia15e918ed6ca5b78851b099efb1eddd35c02de76

RemoteConfiguredTargetValue includes an implementation of TargetData so it
doesn't need to be looked up from the Package.

PiperOrigin-RevId: 703085029
Change-Id: I1f976a8c7b5e8c05f421281d8da9f810f0ece85c

This adds the capability and debugging output, but doesn't actually check anything, that will be in the next change.

Work towards selectively enabling execution platforms: #22567.

PiperOrigin-RevId: 703081888
Change-Id: Ibc92de582a4791af3f389645603cd66e38b710cf

PiperOrigin-RevId: 703081614
Change-Id: I16791ec75960fa884c0de3d0a29dd25beaab03ee

Use it in the many suitable places where Starlark.call() is used so far.
Next steps will be to introduce something corresponding in StarlarkCallable and implement a more efficient implementation thereof in StarlarkFunction and possibly BuiltinFunction.
Further steps could be to allow optimized access paths from Eval.evalCall() to StarlarkFunction and, again possibly, to BuiltinFunction, that directly populate the locals array or the argument vector for the native call.

PiperOrigin-RevId: 703075286
Change-Id: I8fbda39645884a32831958b1fa6b9a1603b9567f

The coverage report produced with `--combined_report` now contains file-level baseline coverage information.

Line-level as well as branch information requires language specific actions and is subject to a proposal for a Starlark API for baseline coverage.

Work towards #5716

Closes #24563.

PiperOrigin-RevId: 703017111
Change-Id: I40db58bc08949b84abc37db237fca0853430795c

The flag has been a no-op for a long while.

Fixes https://github.com/bazelbuild/bazel/issues/13221

PiperOrigin-RevId: 703008100
Change-Id: I75f69edb1339e1c276eafb36539f0c14d7f290b2

PiperOrigin-RevId: 703005422
Change-Id: Ia14657f73bdfe473af80741566253f4a91884b2d

This is a _coarse grained and conservative_ approach to disallow clients from using remote analysis caching when there are changed files outside of the active directories. This is because such files __may__ invalidate a deserialized frontier, but is unable to due to the pruned Skyframe graph, and ultimately cause [stable inconsistent builds](https://bazel.build/run/build#build-consistency)

This is implemented with the `--experimental_frontier_violation_check` flag and only triggers with `--experimental_remote_analysis_cache_mode=download`.

The flag has 3 strictness levels:

1) `strict`: **preferable if reverting the local changes is manageable**. Stop the build immediately and report which filesystem changes are affecting the build. Progress can only be made when the violating change is reverted, or with the `warn` option.
2) `warn`: **preferable if reverting the local changes is undesirable**. Gracefully fallback to fully local evaluation by disabling analysis cache downloads, while warning the user which files are affecting the build. If there exists at least one remotely fetched analysis value in the Skyframe graph already, first invalidate all existing analysis and execution phase values, then continue the build without remote analysis caching.
3) `disabled_for_testing`: do nothing. This is a test specific escape hatch.

PiperOrigin-RevId: 702986396
Change-Id: Ia031e57810bac8fae817d88640c44a4d1c47f307

Baseline: 7b20da28

Cherry picks:

   + e27ab916:
     Automated rollback of commit
     3fdec931.
   + d699813b:
     Release 9.0.0-pre.20241125.3 (2024-12-04)
   + 0ee3d20d:
     Release 9.0.0-pre.20241125.3 (2024-12-04)
   + 08b47315:
     Release 9.0.0-pre.20241125.3 (2024-12-04)
   + 6c25f899:
     Release 9.0.0-pre.20241125.3 (2024-12-04)

This release contains contributions from many people at Google, as well as .

Baseline: 7b20da28

Cherry picks:

   + e27ab916:
     Automated rollback of commit
     3fdec931.
   + d699813b:
     Release 9.0.0-pre.20241125.3 (2024-12-04)
   + 0ee3d20d:
     Release 9.0.0-pre.20241125.3 (2024-12-04)

This release contains contributions from many people at Google, as well as .

Baseline: 7b20da28

Cherry picks:

   + e27ab916:
     Automated rollback of commit
     3fdec931.

Important changes:

  - `archive_override` now accepts all attributes usable with
    `http_archive`; similar for `git_override` and `git_repository`.
  - Fixed an issue where `genquery` in external repos would evaluate
    labels as if they were in the main repo.
  - Re-enable symbolic macro attribute inheritance.

This release contains contributions from many people at Google, as well as Fabian Meumertzheim, Jordan Mele, Simon Thornington, Ulrik Falklof, Xdng Yng, Xudong Yang.

Example:
```
foo project:
 - foo/...
 - tests/foo/...
 - third_party/foo/...
```

A `PROJECT.scl` can *either* define canonical project data *OR*.exclusively declare:

```
project = {
  "actual": "//foo:PROJECT.scl",
}
```

`$ bazel build //foo //bar` works if both `//foo` and `//bar` resolve to `PROJECT.scl`s that reference the same canonical `PROJECT.scl`.

That means we can still only request targets from the same project in a single build.

## Also:

Moved `getProjectFile` from `BuildTool` to `Project`. The original idea was that `Project` found matching `PROJECT.scl` files and `BuildTool` determined if the results could be properly built (i.e. all targets match to the same file).

In practice I don't think those need to be separate logical concerns, so I just merged it all into `Project`.

PiperOrigin-RevId: 702817985
Change-Id: If0bf8865e9813b44db2d22e5ac77e539ad674458

Tarjan's algorithm uses the traversal index, not the stack depth.

PiperOrigin-RevId: 702737429
Change-Id: I394897aa07512202ddbcf3f222bfe25abda87070

Adds a README.md file to the final .zip file providing the commit hash, timestamp, and build command to produce the file.

Fixes #15459

Closes #24566.

PiperOrigin-RevId: 702721238
Change-Id: Id25829d3d77cf82be6c95022e2e5e8e09e30e312

PiperOrigin-RevId: 702711324
Change-Id: I233f6ad5b6fb332848bda99e0d7be307ed8f40d4