| Commit message (Collapse) | Author | Age |
... | |
|
|
|
|
|
|
| |
Taken from releases.bazel.build/bazel-toolchains.html
RELNOTES: None.
PiperOrigin-RevId: 203494047
|
|
|
|
|
|
|
| |
This metric measures the used heap size at the end of the build, after a GC. Because this is expensive it is only collected if a flag is passed.
RELNOTES:
PiperOrigin-RevId: 203492365
|
|
|
|
|
| |
RELNOTES: [JavaInfo] Outputs are merged in java_common.merge().
PiperOrigin-RevId: 203474741
|
|
|
|
|
|
|
|
|
|
|
| |
The only reason that those python wrapper scripts still exists is for
TensorFlow's Windows GPU build. As we will create a custom GPU CROSSTOOL
in TF repo, we can finally remove wrapper scripts from Bazel.
Closes #5526.
RELNOTES: Python wrapper scripts for MSVC are removed.
PiperOrigin-RevId: 203472223
|
|
|
|
|
|
|
| |
It's no longer needed.
RELNOTES: None.
PiperOrigin-RevId: 203469119
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 203466429
|
|
|
|
|
|
|
|
|
|
| |
In this way, their name is one they can actually be referred to by.
This is necessary, as Skylark repository rules end up in the resolved
file when freezing the versions of external dependencies---and the call
to the repository function might be indirect.
Change-Id: Ie1b5a28fac4f690c424de848b42d0c4a217d494d
PiperOrigin-RevId: 203466286
|
|
|
|
|
|
|
| |
want to use input discovery when building modules for performance reasons.
RELNOTES: None.
PiperOrigin-RevId: 203463009
|
|
|
|
| |
PiperOrigin-RevId: 203461813
|
|
|
|
|
|
|
|
|
|
|
| |
building with C++ modules, .d file scanning is not effective as Clang (only
compiler supporting Bazel's version of C++ modules) reads all of the files
passed in anyway.
This is not meant to be activated yet, but for running experiments.
RELNOTES: None.
PiperOrigin-RevId: 203459168
|
|
|
|
|
|
|
|
|
|
|
| |
Commit d3f7f7ae introduced a bug in the FileTransport implementations
where events might not be written to file in the correct order. This
change fixes this.
Fixes #5515
RELNOTES: None
PiperOrigin-RevId: 203457636
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 203454741
|
|
|
|
|
|
|
| |
modules.
RELNOTES: None.
PiperOrigin-RevId: 203454562
|
|
|
|
| |
PiperOrigin-RevId: 203454459
|
|
|
|
|
|
|
| |
Fixes #5246
RELNOTES: None.
PiperOrigin-RevId: 203453340
|
|
|
|
|
|
|
|
|
|
| |
Clang reports missing -Wl,-z,relro as "ld: unknwon option:
-z"). This cl fixes the autodetection to expect the short variant.
Fixes #5468.
RELNOTES: NONE.
PiperOrigin-RevId: 203449206
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Implement a native DeletePath method that can
delete files, directories, and junctions. The
method should tolerate when concurrent
processes delete the file.
The new JNI function is more robust than Java IO
file deletion function because it can also delete
readonly files.
See https://github.com/bazelbuild/bazel/issues/5513
Closes #5520.
Change-Id: I21ea36dd64960b294e2b51600273bf4290ad7c0f
PiperOrigin-RevId: 203448581
|
|
|
|
|
|
|
| |
Fix https://github.com/bazelbuild/bazel/issues/5516
RELNOTES: None
PiperOrigin-RevId: 203448188
|
|
|
|
|
|
|
|
|
|
|
| |
...as this file uses blaze_util::JoinPath. Apparently, until
recently, that header file was pulled in indirectly, so that
this wasn't detected until now. Nevertheless, the header files
for functions used directly should also be included explicitly
anyway.
Change-Id: Id181480c6ec7fd146ce8b7b00980319f13c3f518
PiperOrigin-RevId: 203445044
|
|
|
|
|
|
|
| |
Should not be needed anymore since we have dynamic configurations for a while.
RELNOTES: None.
PiperOrigin-RevId: 203435557
|
|
|
|
|
|
|
| |
PiperOrigin-RevId: 203300374
Change-Id: Iaa47f870ab2e0cad40a202aad2c7f9430f73c856
PiperOrigin-RevId: 203407392
|
|
|
|
|
|
|
|
| |
java_toolchain.package_configuration javacopts
to allow package_configuration to override compatible_with javacopts.
PiperOrigin-RevId: 203396587
|
|
|
|
|
| |
RELNOTES: Remove support for java_runtime_suite; use alias() together with select() instead.
PiperOrigin-RevId: 203393253
|
|
|
|
|
|
|
|
|
|
| |
So far, bazel sync would only report error that happened during
the actual fetch operation. However, errors can also happen earlier,
e.g., when loading or parsing the WORKSPACE file. Report these
errors as well.
Change-Id: Ifa4961b0101f338d7618c52eb607951acba7ccdf
PiperOrigin-RevId: 203359188
|
| |
|
|
|
|
|
|
|
|
|
|
| |
On some systems (including some versions of FreeBSD) it is a requirement
that _WITH_DPRINTF be defined for <stdio.h> to provide the appropriate
header for dprintf(3). Therefore, the respective #define has to come
before any #include as those might pull is <stdio.h>.
Change-Id: I25d55c9c7c0912e8619faf774d2e09f9af9a6a53
PiperOrigin-RevId: 203351202
|
|
|
|
|
|
|
|
|
|
|
| |
It's no longer fatal for the test if $JAVA_HOME
environment variable is unset.
Before this fix the test was crashing if JAVA_HOME
was not set.
RELNOTES: none
PiperOrigin-RevId: 203350738
|
|
|
|
|
|
|
|
|
|
|
| |
Use the "with" statement to open files in various
Python scripts used by Bazel, to ensure these
files are closed eagerly.
See https://github.com/bazelbuild/bazel/issues/5512
RELNOTES: none
PiperOrigin-RevId: 203346678
|
|
|
|
|
|
|
| |
Before this cl the sysroot variable was not present, and that's a bug.
RELNOTES: None
PiperOrigin-RevId: 203346557
|
|
|
|
|
|
| |
Fixes #5469
PiperOrigin-RevId: 203343005
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Use try-with-resources to ensure OutputStreams
that we open via FileSystem.OutputStream(path)
are closed.
Eagerly closing OutputStreams avoids hanging on to
file handles until the garbage collector finalizes
the OutputStream, meaning Bazel on Windows (and
other processes) can delete or mutate these files.
Hopefully this avoids intermittent file deletion
errors that sometimes occur on Windows.
See https://github.com/bazelbuild/bazel/issues/5512
RELNOTES: none
PiperOrigin-RevId: 203342889
|
|
|
|
|
|
|
|
|
|
|
| |
Flags passed through clang to linker get -Wl, stripped in the error message
(e.g. -Wl,-no-as-needed will be reported as "ld: unknwon option:
-no-as-needed"). This cl fixes the autodetection to expect the stripped variant.
Fixes #5468.
RELNOTES: None.
PiperOrigin-RevId: 203341563
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Use try-with-resources to ensure InputStreams that
we open via FileSystem.InputStream(path) are
closed.
Eagerly closing InputStreams avoids hanging on to
file handles until the garbage collector finalizes
the InputStream, meaning Bazel on Windows (and
other processes) can delete or mutate these files.
Hopefully this avoids intermittent file deletion
errors that sometimes occur on Windows.
See https://github.com/bazelbuild/bazel/issues/5512
RELNOTES: none
PiperOrigin-RevId: 203338148
|
|
|
|
|
|
|
| |
Makes it nicer to debug failures
RELNOTES: None.
PiperOrigin-RevId: 203305592
|
|
|
|
|
|
|
| |
Instead of just a path, events now include information about the type of file (output, source file, stdout/stderr, test logs, etc.). This information can be used by the uploaders to determine a) whether to upload, b) what kind of lease to give the files.
RELNOTES: None
PiperOrigin-RevId: 203285549
|
|
|
|
|
|
|
| |
Closes #5424.
Change-Id: I16bb70ffec9d541c56ed0579ae616407073d46f2
PiperOrigin-RevId: 203279412
|
|
|
|
|
|
|
| |
See https://github.com/bazelbuild/bazel/issues/5254#issuecomment-402131986
RELNOTES: None
PiperOrigin-RevId: 203273587
|
|
|
|
|
|
|
| |
https://github.com/bazelbuild/bazel/commit/732dc512801c32207c252a76ca8d9e5544560339.
RELNOTES: Allow @ in package names.
PiperOrigin-RevId: 203270369
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 203264765
|
|
|
|
|
|
| |
These fields can have very large values that don't fit into int. There's also no added value from storing an int instead of a String.
PiperOrigin-RevId: 203260628
|
|
|
|
| |
PiperOrigin-RevId: 203257616
|
|
|
|
| |
PiperOrigin-RevId: 203248319
|
|
|
|
|
|
|
|
| |
Signed-off-by: Bin Lu <bin.lu@arm.com>
Closes #5477.
PiperOrigin-RevId: 203241216
|
|
|
|
| |
PiperOrigin-RevId: 203230801
|
|
|
|
|
|
| |
nodes, instead of invalidating them. Invalidating isn't sound, because we're depending on externally injected state to be re-read during evaluation. Also rename the method to resetConfigurationCollectionForTesting since it's only used in tests.
PiperOrigin-RevId: 203172895
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 203169316
|
|
|
|
| |
PiperOrigin-RevId: 203167019
|
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 203166771
|
|
|
|
|
|
|
|
| |
producing add_dep commands where possible and avoids the need for direct dependencies on supertypes of directly depended types
RELNOTES: None.
PiperOrigin-RevId: 203164113
|
|
|
|
| |
PiperOrigin-RevId: 203159437
|