This project is mirrored from https://github.com/bazelbuild/bazel.git.
Pull mirroring updated .
- Oct 18, 2024
-
-
bazel.build machine account authored
createDexMergerActions continues to be exposed to Starlark due to it's use for SpawnActionTemplate which is not exposed to Starlark. We must pass a file containing global information to the final dexmerging step in order to support Java 17 Record desugaring. This change adds an optional parameter to the Starlark interface to forward the globals file to the Dex Merger. PiperOrigin-RevId: 660045021 Change-Id: Ie3b961ff2687f48ca29a94e67180c0e5875ddbe3 Commit https://github.com/bazelbuild/bazel/commit/2daa0a3d893a3c18021e7c1191d4cacc270dd062 Co-authored-by:
Andrew Sinclair <asinclair@google.com>
-
- Oct 17, 2024
-
-
bazel.build machine account authored
Fixes #23981 Closes #23982. PiperOrigin-RevId: 686486627 Change-Id: I5f03b63601a535f8d551c005b00bf040846a324d Commit https://github.com/bazelbuild/bazel/commit/b0f1430f0e9b7608b9ecc64b20c3b0fe40ac4a43 Co-authored-by:
Fabian Meumertzheim <fabian@meumertzhe.im>
-
Ian (Hee) Cha authored
Fixes #21884 Fixes #23053 Closes #23215. PiperOrigin-RevId: 686518093 Change-Id: I1a6699b169fe4291ad0dda3be7e74f38c8e37bf1 Commit https://github.com/bazelbuild/bazel/commit/0fdb36f8a5cf79fda9931b6e3f119bb5f41f0701 Co-authored-by:
Fabian Meumertzheim <fabian@meumertzhe.im>
-
bazel.build machine account authored
When cancelling an asynchronous repository download task, an interrupt signal is sent to the download thread. This doesn't mean that the download stops immediately. Avoid restarting a download until the previous download has actually stopped, so that the new download is able to clean old data without crashing (on Windows). Fixes #21773 Closes #23837. PiperOrigin-RevId: 686175953 Change-Id: I8d75f905b739d38b6cb430d5b5e84fda9a2d14e3 Commit https://github.com/bazelbuild/bazel/commit/48338d2ff33586a0d053e358da6b94e23fe0e2eb Co-authored-by:
Fredrik Medley <fredrik@meroton.com>
-
- Oct 16, 2024
-
-
lberki authored
This really just exposes the existing LABEL_DICT_UNARY type that already exists in Java. Other than writing some boring conversion logic, all pieces fell together pretty pleasantly. Work towards #7989. That one calls for a string-to-label-list-dict type, but I'm planning to resolve that as WAI, since string-to-label-dict is close enough. RELNOTES: None. PiperOrigin-RevId: 686415025 Change-Id: Ib07ada7ab2ede95220ed1cc2d3569996fc4afb88
-
- Oct 15, 2024
-
-
Ivo List authored
The logic picked the first instead of the highest version due to a typo. Closes #23936. PiperOrigin-RevId: 684528776 Change-Id: Ic61c84ca2f3489e43fc71944824e7e2311543ab9 Co-authored-by:
Fabian Meumertzheim <fabian@meumertzhe.im>
- Oct 11, 2024
-
-
Fabian Meumertzheim authored
Work towards https://github.com/bazelbuild/bazel/issues/19301 Fixes https://github.com/bazelbuild/bazel/issues/23580 RELNOTES: `override_repo` and `inject_repo` can be used to override and inject repos in module extensions. Closes https://github.com/bazelbuild/bazel/pull/23534. PiperOrigin-RevId: 678139661 Change-Id: Iea7caca949c00e701f056c1037e273fee9740e93 (cherry picked from commit https://github.com/bazelbuild/bazel/commit/46341b1a59c7a1cc8ca0dc604ad53b6de7fee653) Fixes #23724 Fixes #23799 Also includes: * Disallow importing injected repos (8472c9df ) --------- Co-authored-by:
Xùdōng Yáng <wyverald@gmail.com>
-
Xùdōng Yáng authored
commits: * d62e0a0f * c3393dac --------- Co-authored-by:
Fredrik Medley <fredrik@meroton.com>
-
Xùdōng Yáng authored
Closes #23800. PiperOrigin-RevId: 684529045 Change-Id: I14dc53b6f2e39c7a05ee3a8b872eb220af45cef9 Co-authored-by:
Fabian Meumertzheim <fabian@meumertzhe.im>
-
Xùdōng Yáng authored
Also switch back to Zulu where possible. Closes #23913. PiperOrigin-RevId: 684397892 Change-Id: I1b563bd45f85bd8ec5cfbaf8550f0a59ea8f0b54 Co-authored-by:
Fabian Meumertzheim <fabian@meumertzhe.im>
-
bazel.build machine account authored
Fixes https://github.com/bazelbuild/bazel/issues/23885 Closes #23102. PiperOrigin-RevId: 684433748 Change-Id: I12cdb9a04f930a52e57bbd8551c8f2559a15932a Commit https://github.com/bazelbuild/bazel/commit/c2d316b4d3f832d0c5677f0abc63c27d059873b8 Co-authored-by:
Keith Smiley <keithbsmiley@gmail.com>
-
- Oct 10, 2024
-
-
Tom Renn authored
On windows, bazel will run the workspace_status_command, and receive carriage return characters \r even if the workspace_status_command did not include them. Fixes https://github.com/bazelbuild/bazel/issues/13442 PiperOrigin-RevId: 684055158 Change-Id: Idd3bd9c954d64b0a2d674dd7d90cf61c00955917 Co-authored-by:
Googler <tomrenn@google.com>
-
Keith Smiley authored
This cherry picks 62dc3b5b and 0b0d9084 which allows setting install_name and soname on shared libraries. No defaults changed here. Fixes https://github.com/bazelbuild/bazel/issues/23842 --------- Co-authored-by:
Fabian Meumertzheim <fabian@meumertzhe.im>
-
bazel.build machine account authored
This allows path mapping to apply to actions that reference execpaths in custom compiler options via location expansion. Work towards #6526 Closes #23630. PiperOrigin-RevId: 680941133 Change-Id: Ia10e2df481dcfe4480cbf9dfb1e12ec3b07d8ab2 Commit https://github.com/bazelbuild/bazel/commit/b4b35af91283709689ffca37c4d1eb4f5eee0c30 Co-authored-by:
Fabian Meumertzheim <fabian@meumertzhe.im>
-
Fabian Meumertzheim authored
(contains the refactor in f311efc5 to reduce merge conflicts) Adds support for spaces and newlines in source and target paths of runfiles symlinks to `build-runfiles` as well as to the Bash, C++, and Java runfiles libraries (the Python runfiles library has moved out of the repo). If a symlink has spaces or newlines in its source path, it is prefixed with a space in the manifest and spaces, newlines, and backslashes in the source path are escaped with `\s`, `\n`, and `\b` respectively. This scheme has been chosen as it has the following properties: 1. There is no change to the format of manifest lines for entries whose source and target paths don't contain a space. This ensures compatibility with existing runfiles libraries. 2. There is even no change to the format of manifest lines for entries whose target path contains spaces but whose source path does not. These manifests previously failed in `build-runfiles`, but were usable on Windows and supported by the official runfiles libraries. This also ensures that the initialization snippet for the Bash runfiles library doesn't need to change, even when used on Unix with a space in the output base path. 3. The scheme is fully reversible and only depends on the source path, which gives runfiles libraries a choice between reversing the escaping when parsing the manifest (C++, Java) or applying the escaping when searching the manifest (Bash). Fixes https://github.com/bazelbuild/bazel/issues/4327 RELNOTES: Bazel now supports all characters in the rlocation and target paths of runfiles and can be run from workspaces with a space in their full path. Closes https://github.com/bazelbuild/bazel/pull/23331. PiperOrigin-RevId: 683362776 Change-Id: I1eb79217dcd53cef0089d62a7ba477b1d8f52c21 (cherry picked from commits https://github.com/bazelbuild/bazel/commit/7407cef3837b4fe14e48e1a925f9b886c0cc945d and f311efc5 ) Closes #23715 --------- Co-authored-by:
Googler <jhorvitz@google.com>
-
- Oct 09, 2024
-
-
Keith Smiley authored
The inability to pass C or C++ specific compiler flags to targets that contain a mix of those sources is a common sticking point for new users. These mirror the global `--conlyopt` and `--cxxopt` flags but at the target level. Fixes https://github.com/bazelbuild/bazel/issues/22041 RELNOTES: Add conlyopts and cxxopts attributes to cc rules Closes #23840 PiperOrigin-RevId: 682144094 Change-Id: I0fe8b728c493652d875ce6a6dd2a9989c36b1f24 (cherry picked from commit 5854788d)
-
Fabian Meumertzheim authored
Before: ``` Caused by: java.util.NoSuchElementException: Resource foo is not tracked in this resource set. at com.google.devtools.build.lib.actions.ResourceManager.assertExtraResourcesTracked(ResourceManager.java:499) at com.google.devtools.build.lib.actions.ResourceManager.areResourcesAvailable(ResourceManager.java:540) ``` After: ``` ERROR: src/test/java/com/google/devtools/build/lib/actions/BUILD:102:10: Testing //src/test/java/com/google/devtools/build/lib/actions:ActionsTests failed: Resource foo is not being tracked by the resource manager. Available resources are: cpu, memory ``` Fixes #19572 Closes #23541. PiperOrigin-RevId: 682282327 Change-Id: Ifdff5f85de9e45ac119c2a2cfd161c054a722546 (cherry picked from commit e5ab94bf ) Closes #23868 Co-authored-by:
Alessandro Patti <ale812@yahoo.it>
-
Fabian Meumertzheim authored
Closes #23873. PiperOrigin-RevId: 682416574 Change-Id: I531cbdadac035bb14585eafe5be093823bca2214 (cherry picked from commit cab7d45d) Closes #23874
-
Yun Peng authored
- Adding `--vendor_dir` to ignored package prefixes as if it's added in the `.bazelignore` file. - This allows users to do `bazel build //...` after vendoring external deps in the source root without manually adding the vendor dir in `.bazelignore`. Fixes https://github.com/bazelbuild/bazel/issues/23521 Closes #23771. PiperOrigin-RevId: 680994986 Change-Id: I9c8b76ca20b9060232dfe05460a8fc857c92e93f Backporting https://github.com/bazelbuild/bazel/commit/d42301b0714ab80aa376715995bc73849a451638
-
Ivo List authored
Fixes: https://github.com/bazelbuild/bazel/issues/23905 Commits: https://github.com/bazelbuild/bazel/commit/dbb9670fb2719323c3e9b5df8ab045d187cf8c63 https://github.com/bazelbuild/bazel/commit/84c15a00d4a756fb82af5079b4e71f5cf933fe94 https://github.com/bazelbuild/bazel/commit/f9ed0b03269ee5364f01e1d177129e4597ba0a48 https://github.com/bazelbuild/bazel/commit/cc3ba22c3e9256dc2d9f419e25c9b653d7f81577 https://github.com/bazelbuild/bazel/commit/7e1393937c56ca25ad678851ec0de93c913eae7d https://github.com/bazelbuild/bazel/commit/0f6d0d839381e9ccee5fd8857c449d6d76ba8714 https://github.com/bazelbuild/bazel/commit/38239d9d71eefb577c3966d17a4fbaae3eedf4fb https://github.com/bazelbuild/bazel/commit/3cb5beaa1550896e0df54d00b66ea215b1e47048 https://github.com/bazelbuild/bazel/commit/3bc5dea1f0e9105489c641c72f322b9e17548b94 https://github.com/bazelbuild/bazel/commit/7518bbb4a67021ec8efcc64e74ebaa72074311d9 https://github.com/bazelbuild/bazel/commit/963e7a230aa31c06e3c4d695e9eb5f9947c8fd6e https://github.com/bazelbuild/bazel/commit/ae0274497028964751310f4fd15117953bf30806 https://github.com/bazelbuild/bazel/commit/8d3bd0e0f95f2abeb9b6d9fc8b32ab4af717fa0f (partial) --------- Co-authored-by:
Googler <shahan@google.com> Co-authored-by:
Tim Peut <timpeut@google.com>
-
Fabian Meumertzheim authored
When the flag is flipped, `ctx.path` no longer watches paths resolved from `Label` parameters and other methods on `ctx` no longer watch such paths even with `watch = "no"`. Closes #23750. PiperOrigin-RevId: 681978073 Change-Id: I9bef5c735db54c971beb806aa1f1a0eb287e3ff2 (cherry picked from commit 50196979) Closes #23768
-
Ian (Hee) Cha authored
Fixes #23754 Closes #23755. PiperOrigin-RevId: 679472028 Change-Id: I0ea922ee6edf28c5643c6f2b524371f1d5405c9c Commit https://github.com/bazelbuild/bazel/commit/765d5e0a64926517d686ff567d280914df08e7dc Co-authored-by:
Fabian Meumertzheim <fabian@meumertzhe.im>
-
- Oct 08, 2024
-
-
Fabian Meumertzheim authored
The cherry-pick of the compact execlog runfiles changes assumed that runfiles only appear in the top-level tool nested set, but this isn't true for genrules. Instead, as in Bazel 8, it can be assumed that all middleman are also contained in inputs, which makes it possible to remove the extra middleman parameter and pass all runfiles tree information down to transitive log calls. Fixes #23884
-
- Oct 05, 2024
-
-
bazel.build machine account authored
Previously the execution logs were always written to relative paths. This caused an issue if you put this flag in your `.bazelrc` and expected the log to be produced in a relative directory. You can now use `%workspace%` to handle writing to the root of your workspace. Fixes https://github.com/bazelbuild/bazel/issues/22267 Closes #23813. PiperOrigin-RevId: 682196916 Change-Id: I5f6fe3c72cfc3fe9a891e0d44440cb49bbc787d8 Commit https://github.com/bazelbuild/bazel/commit/9aaeb9fe2c1edaca38f91c53a5620a2df2220302 Co-authored-by:
Keith Smiley <keithbsmiley@gmail.com>
-
- Oct 04, 2024
-
-
Tiago Quelhas authored
The format is auto-detected from the first few bytes of the input file. PiperOrigin-RevId: 680915789 Change-Id: I6f1b4a2334912f25a8c41761a970e8f75265cc13
-
- Oct 03, 2024
-
- Oct 02, 2024
-
-
https://bazel.build/remote/cache-remoteTiago Quelhas authored
* Recommend the compact format over the binary and JSON formats. * Note that `//src/tools/execlog:parser` can be used with any format. * Note that `//src/tools/execlog:converter` can be used to convert between formats. PiperOrigin-RevId: 680941049 Change-Id: I81caf27a4ff6aef0ea97667df5ccbba1c3f10d58
-
Tiago Quelhas authored
Fixes #18643. PiperOrigin-RevId: 678723961 Change-Id: I3da378d2009de2632228d1e914ae451c96cf5b75
-
Yun Peng authored
Mitigating #23726 PiperOrigin-RevId: 678213406 Change-Id: I99ea19f3dcf56a359e39274ce9043a6b4f64b6a4 Backporting https://github.com/bazelbuild/bazel/commit/355b000accfff4ea29876a46321308fe9422a9d1#diff-544556920c45b42cbfe40159b082ce8af6bd929e492d076769226265f215832fR85
-
bazel.build machine account authored
Otherwise `"<root>"` ends up being escaped with Unicode escape sequences, which is unnecessarily complex. Work towards #22691 Closes #23785. PiperOrigin-RevId: 680633877 Change-Id: Ic3c90c33bbf1209efa90be78b432e2132f0a1f05 Commit https://github.com/bazelbuild/bazel/commit/e959d78517abc0f50b2251e8225355a96e4c59d1 Co-authored-by:
Fabian Meumertzheim <fabian@meumertzhe.im>
-
- Oct 01, 2024
-
-
bazel.build machine account authored
In some (legacy) projects, nuget is used to handle C++ packages. Nuget packages are working fine with WORKSPACE `http_archive` directives when explicitly specifying `type = "zip"`. However, when migrating to bzlmod, we ran into issues when the url in source.json is a nupkg file. This PR resolves that issue and allows consumption of nupkg archives as Bazel modules. Closes #23645. PiperOrigin-RevId: 680636414 Change-Id: Ia7fd3fc738a2dd68b1063dba0dc847c5b0668401 Commit https://github.com/bazelbuild/bazel/commit/b38703665f1324b04ce12d4a84443077510f8ee4 Co-authored-by:
Dennis van den Berg <dennispvandenberg@gmail.com>
-
Tiago Quelhas authored
*** Reason for rollback *** The experiment with using sqlite didn't pan out. We might find other uses for it in the future, but we can always resurrect it from version control; no need to saddle Bazel with the additional dependency until then. *** Original change description *** Implement a JNI wrapper around SQLite. This will be used by the implementation of garbage collection for the disk cache, as discussed in https://github.com/bazelbuild/bazel/issues/5139 and the linked design doc. I judge this to be preferred over https://github.com/xerial/sqlite-jdbc for the following reasons: 1. It's a much smaller dependency. 2. The JDBC API is too generic and becomes awkward to use when dealing with the peculiarities of SQLite. 3. We can (more easily) compile it from source for all host platforms, including the BSDs. *** PiperOrigin-RevId: 679600756 Change-Id: Ic3748fa30404a31504426c523c9b9a60ec451863
-
Fabian Meumertzheim authored
Cherry-picks the following changes: * Optimize representation of runfiles in compact execution log (#23321) * Keep runfiles tree IDs in memory for multiple test attempts (#23703) * Fix naming inconsistency in `spawn.proto` (#23706) * Mark tool runfiles as such in expanded execution log (#23702) The cherry-picks required introducing a `Map<Artifact, RunfilesTree>` shim to `RunfilesSupplier` that matches the Bazel 8 way of obtaining a `RunfilesTree` from a runfiles middleman via `InputMetadataProvider`. Closes #23683 Closes #23710 Closes #23711 Closes #23734
-
Tiago Quelhas authored
Otherwise they are lost, making debugging very difficult. PiperOrigin-RevId: 679540076 Change-Id: I4000ad55745578b0cd8d5c2cc9766e5c7f18059d
-
- Sep 30, 2024
-
-
Tiago Quelhas authored
Modules may now register idle tasks via CommandEnvironment.addIdleTask(). When the server becomes idle, IdleTaskManager (previously called IdleServerTasks) runs registered tasks in series, followed by a final task which triggers a GC and shrinks interner pools. Pending tasks will be interrupted if the server becomes busy again, but IdleTaskManager waits for them to terminate orderly before letting a new command run. Cherry-pick note: in the 7.x tree, the default idle task only runs a GC; it doesn't shrink interner pools like in 8.x. Therefore, I've omitted the latter from this cherry-pick. PiperOrigin-RevId: 678167274 Change-Id: Iae17d4dd304b24b401a6c45986d4c0d861902113
-
- Sep 28, 2024
-
-
bazel.build machine account authored
`//tools/launcher:launcher_maker` produces launchers *for* Windows, but there is no reason why it must *run on* Windows. By making it runnable on all platforms, `*_binary` targets can be built *for* Windows from any platform assuming that a suitable cross-compiling C++ toolchain is available. Closes #23731. PiperOrigin-RevId: 679251350 Change-Id: I1b380d5b28a616ace88a3b049a2b4554aa209ae3 Commit https://github.com/bazelbuild/bazel/commit/108f1171c18387f80596e8709c7b7552c47fe457 Co-authored-by:
Fabian Meumertzheim <fabian@meumertzhe.im>
-
- Sep 27, 2024
-
-
Keith Smiley 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. This is a cherry pick of f0ade80c and eb50e5b8 --------- Co-authored-by:
Googler <plf@google.com>
-
- Sep 26, 2024
-
-
bazel.build machine account authored
This allows Kythe extraction to work with BwoB. Closes #23669. PiperOrigin-RevId: 676371827 Change-Id: I354cb9b9c0ec3511c6d866956fca1ff06a27cfab Commit https://github.com/bazelbuild/bazel/commit/055314eb8694c827931340583aa125b40f0673bb Co-authored-by:
Fabian Meumertzheim <fabian@meumertzhe.im>
-
Grzegorz Lukasik authored
Fixes https://github.com/bazelbuild/bazel/issues/20681 Closes #20684. PiperOrigin-RevId: 595228741 Change-Id: I06bab1efa25deaa4085acfffd350dc62f9f73aa3 Co-authored-by:
Benjamin Peterson <benjamin@engflow.com>
-