This project is mirrored from https://github.com/bazelbuild/bazel.git.
Pull mirroring updated .
- Jan 12, 2024
-
-
oquenchil authored
The toolchain was passing -l:name. This mechanism doesn' t exist on macOS, instead the full path to the shared library should be passed. Mainline commit: https://github.com/bazelbuild/bazel/commit/f0ade80ce920be0719b1a43a40258397f68a944d As it says on that mainline commit, it cannot be checked in with a test unlike this PR, because the macOS toolchain was moved outside of Bazel. Therefore, the change must go in, the macOS toolchain needs to be updated, then the test can be added. This change does go in with a test because the toolchain is still embedded in Bazel for 6.5. Fixes https://github.com/bazelbuild/bazel/issues/20487
-
keertk authored
to allow users temporarily disable remote action building throttle. Workaround for #20478. Closes #20558. Commit https://github.com/bazelbuild/bazel/commit/294c904c30fe305f60e548a438940d5ab60a15b4 PiperOrigin-RevId: 597445193 Change-Id: Ib2c7133adf86139b35156d94e39cbf9e17906439 Co-authored-by:
Chi Wang <chiwang@google.com>
-
- Jan 09, 2024
-
-
Yun Peng authored
For the bootstrap VanillaJavaBuilder, it is important that the AutoValue plugin classes do not end up in the deploy jar. If they do, the processor class is loaded from the app classloader (instead of the processor path classloader). When this happens, AutoValueProcessor uses the app classloader to load extensions (such as auto-value-gson needed by bzlmod), instead of the processor path classloader. Unless all extensions are also correctly present in the app classloder (i.e. in the VanillaJavaBuilder deploy jar), they won't be loaded. Unfortunately, simply adding the jars to the deploy jar is insufficient, we need to also correctly merge the `META-INF/service/...` files as well, which does not happen in our bootstrap java_binary/java_library rules. So, to fix, we remove the auto value plugins from the deploy jar, and use them only to compile our sources that require them. Added a regression test for the crash. We should probably improve it so that we can actually build with the bootstapped Bazel in tests without network access. But I don't think we need block this patch release on that. Fixes https://github.com/bazelbuild/bazel/issues/20501 PiperOrigin-RevId: 592266992 Change-Id: I08ac91ee74140df0c4f22ad2553a8c017b497181 Co-authored-by:
Googler <hvd@google.com>
-
bazel.build machine account authored
When a repository rule is fetch attributes are iterated over in `enforceLabelAttributes` to prepopulate the environment, restarting the fetch each time a new dependency is discovered. This is faster than calling `repository_ctx.path(...)` early in the repository rule implementation function but still has considerable overhead. This PR defers throwing `NeedsSkyframeRestartException` till after every attribute has been processed, greatly reducing the number of restarts and iterations. In an internal project these optimisations are particularly noticeable. Before: 2min 8s, 2min 7s After: 1min 35s, 1min 27s Closes #20434. Commit https://github.com/bazelbuild/bazel/commit/e8ac96adb860b9831a62681167295f103a51470a PiperOrigin-RevId: 588090528 Change-Id: I7917b137d6e60b6d6a73189cf396418a85b3ec28 Co-authored-by:
Jordan Mele <mele@canva.com> Co-authored-by:
Xùdōng Yáng <wyverald@gmail.com>
-
bazel.build machine account authored
Currently if the `--install_base` path passed is not writable by the user invoking Bazel, the Bazel client crashes: ```console ❯ bazel --install_base=/some/read/only/path version FATAL: failed to set timestamp on '/some/read/only/path': (error: 30): Read-only file system ``` This happens because the Bazel client (unconditionally) attempts to update the `mtime` of this path: https://github.com/bazelbuild/bazel/blob/a3c677dfea2de636a719d50345a5a97af96fae60/src/main/cpp/blaze.cc#L1010-L1021 This commit updates the client to ignore such errors. See #20373 for context. Closes #20442. Commit https://github.com/bazelbuild/bazel/commit/7f782e3c1a1c4a21beea19c2cedb614be8316e67 PiperOrigin-RevId: 591266054 Change-Id: If53e7cad48cb62406f7883f72b413e4b5a0bb8e2 Co-authored-by:
Rahul Butani <rrbutani@users.noreply.github.com> Co-authored-by:
Ian (Hee) Cha <heec@google.com>
-
Yun Peng authored
This should fix https://buildkite.com/bazel-trusted/publish-bazel-binaries/builds/19494, which was caused by recent OS update.
-
- Jan 08, 2024
-
-
bazel.build machine account authored
Due to https://github.com/bazelbuild/bazel/issues/20660 RELNOTES: None Commit https://github.com/bazelbuild/bazel/commit/d9dc4fde4c8d06498f39b54a81d4e7fa1e5b5b30 PiperOrigin-RevId: 593115090 Change-Id: Ifc2a282dbd6dd8a3abfec987398388e5844af91c --------- Co-authored-by:
Googler <pcloudy@google.com> Co-authored-by:
Ian (Hee) Cha <heec@google.com>
-
- Jan 06, 2024
-
-
- Dec 19, 2023
-
-
Xùdōng Yáng authored
-
- Dec 15, 2023
-
-
bazel.build machine account authored
Without this there can be large gaps in the profile when using remote execution that are hard to reason about. Closes #20474. Commit https://github.com/bazelbuild/bazel/commit/75fffbf1bc55bf58f358d98802c2eeb9001553cd PiperOrigin-RevId: 590475989 Change-Id: Ic6e042c36f85e8098a468c73c62bd45cc367423e Co-authored-by:
Brentley Jones <github@brentleyjones.com>
-
Ian (Hee) Cha authored
After an action was executed remotely, RemoteSpawnRunner would use the timestamps in the execution metadata to record appropriate timing phases into the JSON profile. However, there are durations in-between the existing phases that are unaccounted for. Depending on the RBE server implemenation, these phases could mean different things: - Sandbox preparation - Cleaning up sandbox environments post-execution - Others Missing these durations inside the timing profile would cause confusion to end users as it would be interpreted as nothing happened in between the existing phases. Add these durations into the profile as "pre-X" phases so that user is aware of activities could still be happening during that time. RBE server implementation should be able to alter these label programmatically if necessary. Closes #20387. Commit https://github.com/bazelbuild/bazel/commit/fe9e9e04cbc7174fc33fa18810ff6647766100c4 PiperOrigin-RevId: 590816782 Change-Id: I2bee36be928db24a14fab18bc519c3893723b7d6 Co-authored-by:
Son Luong Ngoc <sluongng@gmail.com>
-
- Dec 14, 2023
-
-
Xùdōng Yáng authored
By upgrading the Apache Commons Compress library to 1.20. I'm deliberately not upgrading to the most recent one (1.24.0) because it would require an additional JDK module (java.desktop) and significantly regress the binary size. Fixes #20090. Closes #20110. PiperOrigin-RevId: 580935354 Change-Id: I6c9728ac3fd925432f44a55efaef8f5b52d428c0 Co-authored-by:
Tiago Quelhas <tjgq@google.com>
-
Mai Hussien authored
Cherry-picks: https://github.com/bazelbuild/bazel/commit/7a537ca644ac17d565585cd4b3e21bf6243dc001, https://github.com/bazelbuild/bazel/commit/0656103c9bc23b627e1a49fe4544f068469f8f1b, https://github.com/bazelbuild/bazel/commit/bc1df918074883660b74c40e0ee43db9aa0ced87, https://github.com/bazelbuild/bazel/commit/7b97147263700067e4397fa6c9a25318fa2e98f7 Fixes https://github.com/bazelbuild/bazel/issues/20480 --------- Co-authored-by:
Fabian Meumertzheim <fabian@meumertzhe.im>
-
- Dec 12, 2023
- Dec 08, 2023
-
-
Tiago Quelhas authored
[6.5.0] Fix tree file materialized as symlink to another file when building without the bytes. (#20409) This is the same bug as #19143, except that the fix in 3a48457d missed the case where the symlink occurs inside an output directory. Fixes #20408.
-
- Oct 20, 2023
-
-
Bazel Release System authored
Baseline: 0f231ac8 Release Notes: + Support multiple remote execution digest functions (#19042) + Release 6.4.0 remote (#18959) + Move BazelFileSystemModule into bazel package (#19043) + Fix a bug where frozen targets list was mutated while expanding env attribute (#19053) + Mark isolated extension usages as experimental (#19065) + Add the remote_require_cached flag (#19075) + Advertise CcInfo from cc_import (#19086) (#19088) + Update java_tools version to 12.6 (#19092) + Set the digest_function field as part of all relevant gRPC requests (#19049) + Merge `use_repo` buildifier fixups into a single command (#19134) + Ensure that extension unique names followed by `~` are prefix-free (#19164) + Lockfile updates & fixes (#19153) + Switch xcode_autoconf to use 'configure = True' (#19174) + Cherry pick Add a Starlark flag that allows disabling proguard. This will be useful for testing later. (#19179) + Update CODEOWNERS for 6.4.0 (#19194) + Friendlier error message for `bazel_dep`s without `version` (#19196) + Always check `$config_dependencies` visibility at use (#19197) + Add support for the BLAKE3 digest function (#19191) + Enable cc toolchain resolution when cross compiling to windows arm64. (#19198) + Ensure disk cache root exists (#19225) + Fix valid json when using jsonproto output in queries with new `--ouput=streamed_jsonproto` implementation. (#19226) + Add toolchain type for Java bootstrap runtime (#19220) + Add Starlark implementation for several CcCommon methods. (#19076) + Rename `cc_test_wrapper` to `cc_test` (#19231) + Cherry-pick commits to fix a Windows issue (#19232) + Add support for more workspace boundary files to bash completion (#19281) + Use `debugPrint` instead of `str` for `fail` arguments (#19283) + Include name in `repr` of exported `rule`s (#19229) + Download `BazelRegistryJson` only once per registry (#19300) + Make module extension tag's `debugPrint` useful for error messages (#19285) + Intern repository mapping entries (#19293) + Add `additional_linker_inputs` option to `cc_library` rule (#19264) + Do not rerun module extensions when only imports or locations change (#19284) + Add profiling for Bzlmod operations (#19313) + Retry on javax.net.ssl.SSLException ... BAD_DECRYPT (#19346) + Fetch `RepoSpecs` in parallel (#19354) + Make `MODULE.bazel.lock` deterministic (#19370) + Ensure lockfile is updated after reset to pre-build state (#19371) + build-runfiles: remove temporary file prior to creating it (#19386) + Always fail on unknown attributes (#19404) + Ignore Starlark options on commands with `allowResidue = False` (#19417) + Separate PackageSpecificationProvider from its target (PackageGroupConfiguredTarget) (#19420) + Expose PackageSpecificationInfo provider as a top level symbol (#19422) + Revert "Report remote execution messages as events" (#19415) + [6.4] Add --incompatible_disable_objc_library_transition (#19393) + Create .bazelversion to address postsubmit timeout issues (#19435) + Add `contains` method inside `PackageSpecificationProvider` (#19425) + Wrong include path to Clang 16 on Windows (#19430) + Simplify release notes by just printing the first line of the commit … (#19448) + Remove PackageGroupConfiguredTarget.isAvailableFor function (#19444) + Remove default -s flag from macOS libtool invocation (#19454) + Turn off lockfile feature by default (#19462) + Take the no-remote-exec tag into account when computing the action salt (#19457) + Add `--incompatible_merge_fixed_and_default_shell_env` (#19319) + Improve error when a label is provided in `config_setting`'s `values` (#19484) + Mark tool inputs in the execution log. (#19483) + Add visionOS support (#19436) + Intern empty `Depset`s (#19443) + Do not allow applicable_licenses on platform. (#19426) + Cherry pick Bzlmod fixes (#19494) + Optimize classpath pre-processing in java_stub_template.txt (#19491) + Add output name to CacheNotFoundException (#19452) + feat: add option to exit early if analysis cache is discarded (#19503) + Cherry pick platform dependent lockfile (#19498) + Print Passed and Failed methods in detailed test summary (#19505) + Add formatted timestamp entries to volatile workspace status file. (#19499) + Write an explicit line ending to the lockfile (#19519) + Only use `/showIncludes` if supported (#19521) + Also apply `NestedSet` optimizations to `Depset` (#19492) + Add diff_against_dynamic_baseline option to experimental_output_direc… (#19514) + Update java_tools to v12.7 (#19522) + Advertise CcInfo from cc_proto_library (#19534) + Update unknown Xcode version error message and provide an environment variable to force re-evaluation (#19540) + Print dep chain leading to a module that is in error (#19543) + Show fetch progress for the `mod` command (#19542) + Revert "Switch xcode_autoconf to use 'configure = True' (#19174)" (#19550) + Explain the use of `str(Label(...))` in the docs (#19554) + Add `--consistent_labels` flag to all query commands (#19567) + Inject builtin modules at the end of the MODULE.bazel file (#19573) + Disable bzlmod_query_test for RBE build (#19585) + Clear runfiles environment variables for `bazel run` (#19606) + cc_library: propagate data dependencies via implementation_deps. (#19590) + Error on potential unsupported `/showIncludes` lines (#19611) + Use case-insensitive comparison for Windows paths in `runfiles.bash` (#19626) + Show test labels in summaries in display form (#19625) + Remove stale extension entries from lockfile (#19683) + Keep leading zero in formatted date (#19694) + Bzlmod lockfile: fix pretty printing for attributes (#19691) + MODULE.bazel.lock file contains user specific paths (#19698) + Consider RCs equivalent to release for `bazel_compatibility` (#19689) + Use `Label` in `@bazel_tools//tools/jdk` macros (#19675) + Remove stale extension entries from lockfile if module order changes (#19730) + Update rules_java 5.5.1 (#19701) + Fix Java compilation for jdk21 (#19735) + Fix output materialized as symlink when building without the bytes. (#19739) + Make lockfile's `RepoSpec` attributes more readable (#19748) + Merge rule and aspect validation output groups (#19745) + Fix handling of non-ASCII characters in archive entry file names (#19765) + Raise an early error on invalid labels in transitions inputs/outputs (#19764) + Handle synthetic method parameters entries that don't have names (#19758) + Bazel release process: Fix push justification. (#19768) + Flip --experimental_cc_implementation_deps (#19751) + Add blake3 NEON instructions on linux arm64 (#19804) + Fix crash when `environ` contains duplicate entries (#19827) + Bump c++ standard to c++14 per default (#19794) + Collect debug info context from implementation deps (#19836) + Fix unconditional Skyframe invalidation with --lockfile_mode=… (#19848) Acknowledgements: This release contains contributions from many people at Google, as well as Andreas Herrmann, bazel.build machine account, Brentley Jones, buildbreaker2021, Chirag Ramani, David Ostrovsky, Ed Schouten, Fabian Meumertzheim, George Gensure, Greg, John Laxson, Julio Merino, Keith Smiley, Matt Mackay, Mauricio G, NelsonLi0701, nglevin, Nicholas Junge, oquenchil, Orion Hodson, Roman Salvador, Ted Kaplan, Thi Doan, Thi Don, Tyler Williams, Xùdōng Yáng.
-
- Oct 18, 2023
-
-
Fabian Meumertzheim authored
…update Ensure that `BazelLockFileModule` only updates `MODULE.bazel.lock` if the content of the file needs to change. Every such update changes the file's metadata, which results in Skyframe invalidation of, in particular, all configurations. This broke `bazel config`, which uses `MemoizingEvaluator#getDoneValues()` to directly observe Skyframe state. Compared to the original commit https://github.com/bazelbuild/bazel/commit/78db9ae9a545a9586dbb02d7831f5302594e01cb, this cherry-pick does not include the change to `bazel config` as it may not be backwards compatible (changes the exit code in certain situations). Fixes #19823 Closes #19842. PiperOrigin-RevId: 574133346 Change-Id: I5886c91fc6b7b938a7dee59ea75aa7b8afb5b161 Fixes #19843
-
- Oct 17, 2023
-
-
Ian (Hee) Cha authored
Fixes https://github.com/bazelbuild/bazel/issues/19146 Closes #19725. Commit https://github.com/bazelbuild/bazel/commit/e55fee2938b38605cd3da7fc9c790da71961dd1a PiperOrigin-RevId: 573751305 Change-Id: I9b5df85dc5e52822b3a0b44fc42d90b727a5abf0 Co-authored-by:
Thi Don <t@thi.im>
-
- Oct 16, 2023
-
-
Thi Doan authored
Fixes: https://github.com/bazelbuild/bazel/issues/18181. Closes: #18280. Closes #18280. PiperOrigin-RevId: 530246609 Change-Id: I6b49d1bd827e98ca65db87c34c1bb13106ffc232 (cherry picked from commit 978cd23e ) Co-authored-by:
David Ostrovsky <david@ostrovsky.org>
-
bazel.build machine account authored
The values of the internal `$environ` attribute of repository rules is now deduplicated. `ActionEnvironmentFunction#getEnvironmentView`'s signature is updated to receive a `Set` to ensure deduplication for all callers. Previously, a repository rule with duplicate values in `environ` could crash with: ``` FATAL: bazel crashed due to an internal error. Printing stack trace: java.lang.RuntimeException: Unrecoverable error while evaluating node 'REPOSITORY_DIRECTORY:@foo' (requested by nodes 'IGNORED_PACKAGE_PREFIXES:@foo') at com.google.devtools.build.skyframe.AbstractParallelEvaluator$Evaluate.run(AbstractParallelEvaluator.java:633) at com.google.devtools.build.lib.concurrent.AbstractQueueVisitor$WrappedRunnable.run(AbstractQueueVisitor.java:365) at java.base/java.util.concurrent.ForkJoinTask$RunnableExecuteAction.exec(Unknown Source) at java.base/java.util.concurrent.ForkJoinTask.doExec(Unknown Source) at java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(Unknown Source) at java.base/java.util.concurrent.ForkJoinPool.scan(Unknown Source) at java.base/java.util.concurrent.ForkJoinPool.runWorker(Unknown Source) at java.base/java.util.concurrent.ForkJoinWorkerThread.run(Unknown Source) Caused by: java.lang.IllegalArgumentException: Multiple entries with same key: FOO=bar and FOO=bar at com.google.common.collect.ImmutableMap.conflictException(ImmutableMap.java:377) at com.google.common.collect.ImmutableMap.checkNoConflict(ImmutableMap.java:371) at com.google.common.collect.RegularImmutableMap.checkNoConflictInKeyBucket(RegularImmutableMap.java:241) at com.google.common.collect.RegularImmutableMap.fromEntryArrayCheckingBucketOverflow(RegularImmutableMap.java:132) at com.google.common.collect.RegularImmutableMap.fromEntryArray(RegularImmutableMap.java:94) at com.google.common.collect.ImmutableMap$Builder.build(ImmutableMap.java:573) at com.google.common.collect.ImmutableMap$Builder.buildOrThrow(ImmutableMap.java:601) at com.google.devtools.build.lib.skyframe.ActionEnvironmentFunction.getEnvironmentView(ActionEnvironmentFunction.java:105) at com.google.devtools.build.lib.rules.repository.RepositoryFunction.getEnvVarValues(RepositoryFunction.java:305) ... ``` Fixes #19244 Closes #19245. Commit https://github.com/bazelbuild/bazel/commit/49af3d32073aecb4d04ea85e58d7fd964774aff9 PiperOrigin-RevId: 557156429 Change-Id: I454e88b1358cac9a9d787f295fdc9829c57860e4 Co-authored-by:
Fabian Meumertzheim <fabian@meumertzhe.im>
-
- Oct 12, 2023
-
-
bazel.build machine account authored
otherwise getting libunix_jni.so: undefined symbol: blake3_hash_many_neon see https://github.com/bazelbuild/bazel/commit/d0de5e044c65fe7c5e414f860887be20087732da Closes #19384. Commit https://github.com/bazelbuild/bazel/commit/31812fe7689fc317afed4e80c383d01cfcbc7087 PiperOrigin-RevId: 562479599 Change-Id: I8f0ca6b68486f5ea8db698f3f99526eb1c0de8a8 Co-authored-by:
Mauricio G <up.mauricio.g@gmail.com>
-
- Oct 10, 2023
-
-
Ian (Hee) Cha authored
This allows distributing libraries as source that use `implementation_deps`. Closes #19724. Commit https://github.com/bazelbuild/bazel/commit/05787f3f8bc3f3866ccb4d7650b331373a053640 PiperOrigin-RevId: 571105562 Change-Id: I268c5aa0fd83b220aa85dbeb6eef6a07f6b7d3f7 Co-authored-by:
Thi Don <t@thi.im>
-
bazel.build machine account authored
Commit: https://github.com/bazelbuild/bazel/commit/46404353f8295fb6306e34b7138b622b083c8ec0 PiperOrigin-RevId: 571350496 Change-Id: I95f5a1ef32ba1df4dad7ebb9c25bf87333bc25ff --------- Co-authored-by:
Googler <fwe@google.com>
-
Liam Miller-Cushon authored
> If the value of the name_index item is zero, then this parameters element indicates a formal parameter with no name. https://docs.oracle.com/javase/specs/jvms/se20/html/jvms-4.html#jvms-4.7.24 Cherry-pick of https://github.com/bazelbuild/bazel/commit/3954a18fa6b0e3d1a1005cc3409ebc95f6adf3af PiperOrigin-RevId: 530621691 Change-Id: I7ff5bea7a5203f10c62fde42ff10818f8c94cd9e Co-authored-by:
Yun Peng <pcloudy@google.com>
-
- Oct 09, 2023
-
-
Fabian Meumertzheim authored
When a label pointing to an unavailable repository is specified as a transition's input or output, an early error is raised instead of crashing during transition evaluation. Fixes #19632 Closes #19634. PiperOrigin-RevId: 570634319 Change-Id: Icda2946313898db2372484b4f845aafcf5a8b272 Fixes #19641
-
Fabian Meumertzheim authored
When creating a `PathFragment` from a ZIP or TAR entry file name, the raw bytes of the name are now wrapped into a Latin-1 encoded String, which is how Bazel internally represents file paths. Previously, ZIP entries as well as TAR entries with PAX headers would result in ordinary decoded Java strings, resulting in corrupted file names when passed to Bazel's file system operations. Fixes #12986 Fixes https://github.com/bazelbuild/rules_go/issues/2771 Closes #18448. PiperOrigin-RevId: 571857847 Change-Id: Ie578724e75ddbefbe05255601b0afab706835f89 Fixes #19671
-
- Oct 07, 2023
-
-
Fabian Meumertzheim authored
By merging the special `_validation` output groups across a rule and its attached aspects, aspects and rules can simultaneously use validation actions. Fixes #19624 Closes #19630. PiperOrigin-RevId: 571084964 Change-Id: I3135ce1f9e61124e96a3b7d8e0ea0c3a3cdf526d Fixes #19742
-
Yun Peng authored
String-valued tag and repo rule attributes in the `MODULE.bazel.lock` file have to be serialized in a way that distinguishes them from label-valued attributes. This commit uses the fact that the string representation of labels always starts with `@@` to escape strings only if they start with `@@` (or happen to be of the form of an escaped string). Since string-valued attributes rarely start with `@@`, in particular when specified by humans and not macros, this greatly reduces the need for escaping in the lockfile. This commit raises the lockfile version to 3. Along the way also disables HTML escaping for attributes as it isn't needed and results in less readable representations of certain characters. Closes #19684. PiperOrigin-RevId: 571037360 Change-Id: I04bb60d371cd09326780004122e729d78c99732a Co-authored-by:
Fabian Meumertzheim <fabian@meumertzhe.im>
-
- Oct 06, 2023
-
-
Tiago Quelhas authored
This appears to have worked in 6.2.x, got broken in 6.3.x, and is working again at head. The divergence is too great at this point, so it's not possible to cherry-pick the relevant changes from head. Instead, I've written a targeted fix that falls back to downloading every action output if at least one of the outputs was materialized as a symlink. Fixes https://github.com/bazelbuild/bazel/issues/19143.
-
- Oct 05, 2023
-
-
hvadehra authored
Fixes https://github.com/bazelbuild/bazel/issues/19680 Backported from https://github.com/bazelbuild/rules_java/commit/325a9e1767f7ec0daac9bf79b04d4a9b2ab423eb: ``` Use JRTFS instead of initializing a FileManager to process --system PiperOrigin-RevId: 565773578 Change-Id: I1c8a803d1650d8c0beb9a6bf074b53369144e1df ```
-
keertk authored
Context: https://github.com/bazelbuild/bazel/issues/19598#issuecomment-1740539160 ~Release: https://github.com/bazelbuild/rules_java/releases/tag/6.3.2~ ~BCR PR: https://github.com/bazelbuild/bazel-central-registry/pull/966~ Release: https://github.com/bazelbuild/rules_java/releases/tag/5.5.1 BCR PR: https://github.com/bazelbuild/bazel-central-registry/pull/967
-
bazel.build machine account authored
Previously, extension entries in the lockfile were not removed when only the BFS order of modules using the extension changed. However, this change is visible in the module extension implementation function and must thus be considered when checking for staleness. Closes #19659. Commit https://github.com/bazelbuild/bazel/commit/aa458e0fc05621bbc8e673427d6466bcabe2b01b PiperOrigin-RevId: 570720034 Change-Id: I5836b6e1a0172e5d930fcfdacbea53fc090d300d Co-authored-by:
Fabian Meumertzheim <fabian@meumertzhe.im>
-
- Oct 04, 2023
-
-
Fabian Meumertzheim authored
Fixes failures to resolve repos such as `@remote_java_tools`, which are resolved against the using repository instead of `@bazel_tools` without labels. "Cherry-pick" of https://github.com/bazelbuild/rules_java/commit/784464a6aaa8e33cbf070b0df48e3a9686042a8a
-
- Oct 03, 2023
-
-
bazel.build machine account authored
We want `bazel_compatibiliy = [">=6.4.0"]` to match `6.4.0rc1` so that release candidates are indistinguishable from the actual release via Bazel version compatibility requirements. This allows more realistic testing of releases via RCs without having users to rely on hacks such as `bazel_compatibility = [">=6.3.9999"]`. Along the way change the error message on incompatibility to include the standard module key identifier, which is `<root>` for the root module instead of `<name>@<version>`, both of which can be empty. Closes #19678. Commit https://github.com/bazelbuild/bazel/commit/21cd4efaa8c766ac9f1d930c7b10052d91a3958e PiperOrigin-RevId: 569982709 Change-Id: I7dce89ac1c62c1539d71704f048dca65232c119c Co-authored-by:
Fabian Meumertzheim <fabian@meumertzhe.im> Co-authored-by:
Yun Peng <pcloudy@google.com>
-
- Oct 02, 2023
-
-
bazel.build machine account authored
- Store the unresolved registry string "containing %workspace% placeholder" in IndexRegistry and use it to create the remote_patches - Later when creating the repo rule, resolve the registry path in remote_patches fixes https://github.com/bazelbuild/bazel/issues/19621 Commit https://github.com/bazelbuild/bazel/commit/736a06813d698eea0a266d09f4664a11c1ff672e PiperOrigin-RevId: 570028910 Change-Id: I984c6b7494fb377bcf8b3568fa98c740c8618c33 Co-authored-by:
salma-samy <salmasamy@google.com>
-
bazel.build machine account authored
This PR contains 1 commit(s). 1)RELNOTES: Commit https://github.com/bazelbuild/bazel/commit/d3577c96bfa3619d87b68e28c1c7fb6980bc1424 PiperOrigin-RevId: 569510142 Change-Id: I46f3db411c720b79f3474da67a5b1614a0b7815f Co-authored-by:
Googler <pcloudy@google.com>
-
bazel.build machine account authored
This PR contains 1 commit(s). 1)Fixes CI breakage starting from Oct 1st: https://buildkite.com/bazel/bazel-bazel/builds/25047 ``` test_stable_and_volatile_status FAILED: Timestamp formatted date: 2023 Oct 01 20 03 45 Sun differs from workspace module provided formatted date: 2023 Oct 1 20 03 45 Sun. ``` RELNOTES: None Commit https://github.com/bazelbuild/bazel/commit/3453d035bb335a0e792fb379807dbdb812065619 PiperOrigin-RevId: 569993913 Change-Id: If4aeb5db0f5547d4ac3168689bb8e011ca454578 Co-authored-by:
Googler <pcloudy@google.com>
-
bazel.build machine account authored
When changes to module files result in module resolution rerunning, extension results from the lockfile may become stale due to changed usages even if the current build doesn't evaluate the affected extension. We now compare the current usages against the usages recorded in the lockfile and drop all extensions that became stale. Along the way, also trim tag locations when comparing usages for staleness detections as they do not affect the evaluation result. Closes #19658. Commit https://github.com/bazelbuild/bazel/commit/9bf8f396db5c8b204c61b34638ca15ece0328fc0 PiperOrigin-RevId: 569612685 Change-Id: I8e9e30c37076ef2cbfa6e0498b9e003a078e4c67 Co-authored-by:
Fabian Meumertzheim <fabian@meumertzhe.im>
-
- Sep 27, 2023
-
-
bazel.build machine account authored
When running external tests with Bzlmod, this results in apparent labels instead of canonical ones. Closes #19593. Commit https://github.com/bazelbuild/bazel/commit/4c154346c76250d2c0287e202ee0dc3eb07a28c7 PiperOrigin-RevId: 568312090 Change-Id: Ice4c48d9ae7e313b33ad41fe954ce57d5a1e2b12 Co-authored-by:
Fabian Meumertzheim <fabian@meumertzhe.im>
-
- Sep 26, 2023
-
-
bazel.build machine account authored
When matching paths or path segments in the Bash runfiles library, use a case-insensitive comparison when running in MSYS2 as Bazel emits paths that can be capitalized differently. In particular, this fixes failures when the output base path contains uppercase letters. Closes #19602. Commit https://github.com/bazelbuild/bazel/commit/ea4ab7d8e696f48253fd172fcfbd37661e4710d5 PiperOrigin-RevId: 568323218 Change-Id: Ic4655b82b1acbaa9ed50118913d713fba3d7f5de Co-authored-by:
Fabian Meumertzheim <fabian@meumertzhe.im>
-