| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
| |
through JavaInfo, instead of returning them also through ConfiguredTarget. Since these providers can not be found in ConfiguredTarget anymore they have to be retrieved from JavaInfo instead.
RELNOTES: None.
PiperOrigin-RevId: 206585413
|
|
|
|
|
|
|
| |
that it can be accessed in Skylark. One example where this is used is in Android IDL processing where the manifestProtoOutput is used to split out the Android IDL generated Java classes from the overarching outputJar produced by the android_library rule.
RELNOTES: none
PiperOrigin-RevId: 206580880
|
|
|
|
| |
PiperOrigin-RevId: 206573961
|
|
|
|
| |
PiperOrigin-RevId: 206568465
|
|
|
|
|
|
|
|
|
| |
RELNOTES: When using Bazel's remote execution feature and Bazel has to
fallback to local execution for an action, Bazel used non-sandboxed
local execution until now. From this release on, you can use the new
flag --remote_local_fallback_strategy=<strategy> to tell Bazel which
strategy to use in that case.
PiperOrigin-RevId: 206566380
|
|
|
|
| |
PiperOrigin-RevId: 206564363
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
//src/test/shell/integration:execution_phase_tests
now runs on Windows.
See https://github.com/bazelbuild/bazel/issues/4292
Change-Id: Ia46f26d7fa428cc17cd6988859d427165174fe29
Closes #5688.
Change-Id: I5d001825431e8a0ee7d2ce6be911544b72c3bdd2
PiperOrigin-RevId: 206560081
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
//src/test/shell/integration:startup_options_tests
now runs on Windows.
See https://github.com/bazelbuild/bazel/issues/4292
Change-Id: I255b227f7b6b788f21b45b743e7065a646252a36
Closes #5706.
Change-Id: Ibee4997783a820858fc2d2bdda02082a91385d0e
PiperOrigin-RevId: 206551029
|
|
|
|
|
|
|
| |
We want to make sure that the profile captures all Skyframe invocations, so
that we can catch cases where we accidentally introduce new ones.
PiperOrigin-RevId: 206543307
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
//src/test/shell/integration:experimental_ui_test
now runs on Windows.
See https://github.com/bazelbuild/bazel/issues/4292
Change-Id: I7997e8a2e8dce9377c0326b9ed3f6c55a09b2708
Closes #5690.
Change-Id: I7997e8a2e8dce9377c0326b9ed3f6c55a09b2708
PiperOrigin-RevId: 206535860
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
//src/test/shell/integration:loading_phase_tests
now runs on Windows.
The inherently incompatible parts of the test are
now in
//src/test/shell/integration:loading_phase_posix_tests
See https://github.com/bazelbuild/bazel/issues/4292
Change-Id: I90db31449e72aed2138916eed6289bcc20af5cae
Closes #5685.
Change-Id: I38727aed1b548ec8b566f99551e63cceac78180b
PiperOrigin-RevId: 206533515
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 206393574
|
|
|
|
| |
PiperOrigin-RevId: 206389059
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
honored when creating the host platform.
Fixes #5695.
Change-Id: Iaa99c8189421893440e5e5140450c70de69d7b86
Closes #5696.
Change-Id: Iaa99c8189421893440e5e5140450c70de69d7b86
PiperOrigin-RevId: 206371468
|
|
|
|
|
|
|
| |
providers of the same type.
RELNOTES: A rule error is now thrown if a Skylark rule implementation function returns multiple providers of the same type.
PiperOrigin-RevId: 206371385
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 206368137
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
http://https://github.com/bazelbuild/bazel/commit/71479d3ef1627a30b9ec75ca50e6a90cf7db6377 broke thousands of targets in the nightly, notably:
//abuse/ares/rulesystem/generator/python/rule_set:main (x1754)
//net/encapdecap/common/templates:gen_dr_scopes (x903)
//testing/cloud/vex/public:vex_main_internal (x782)
//wireless/android/play/playlog/server:playlog_server (x401)
*** Original change description ***
C++: Removes calls to setCcLinkparamsStore of CcLinkingInfo.Builder
This is in preparation for deleting CcLinkParamsStore. All remaining calls
to the setCcLinkparamsStore method of the CcLinkingInfo builder have been removed.
RELNOTES:none
PiperOrigin-RevId: 206361808
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Go back to the default constructor - instead of requiring everywhere to know the correct hash function, we'll have the default rely on global state. It will make transition easier, even if it makes the origin of the hash less obvious.
*** Original change description ***
Remove default MD5 in most of Bazel's virtual filesystems.
This forces the ex-default to be explicit in a lot of tests, but I'd rather that than have the risk of implicit md5-use in production code.
To keep this CL smaller, do not remove the default from UnixFS quite yet.
RELNOTES: None.
PiperOrigin-RevId: 206358838
|
|
|
|
|
|
|
| |
instead of just skipping the add dep errors.
RELNOTES: follow-up to https://github.com/bazelbuild/bazel/commit/1ac359743176e659e9c7472645e3142f3c44b9e8
PiperOrigin-RevId: 206350053
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Rolling forward with fixes.
*** Original change description ***
PiperOrigin-RevId: 206339696
|
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 206328416
|
|
|
|
|
|
|
|
|
|
| |
The "distdir" option is no longer experimental and therefore should not be
marked as such. Also, the "experimental_repository_hash_file" and
"experimental_verify_repository_rules" are not really about loggig; but they
actually are still experimental.
Change-Id: I5c30c7c0871822c077a713819ae47b250a7d8a71
PiperOrigin-RevId: 206326885
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
//src/test/shell/integration:python_test now runs
on Windows.
See https://github.com/bazelbuild/bazel/issues/4292
Change-Id: Ie408ea55973a32fc5ee6e74f9bed5e3fa9f818b1
Closes #5684.
Change-Id: Ie408ea55973a32fc5ee6e74f9bed5e3fa9f818b1
PiperOrigin-RevId: 206321651
|
|
|
|
|
|
|
|
| |
/cc @laszlocsomor
Closes #5655.
PiperOrigin-RevId: 206319221
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
//src/test/shell/integration:progress_reporting_test
now runs on Windows.
See https://github.com/bazelbuild/bazel/issues/4292
Change-Id: Ic6a4c466156e26717beacb3bbbb270a8c2ccccd0
Closes #5675.
Change-Id: I4152dbe38a9880cbdad5d897b3d8b082b200552b
PiperOrigin-RevId: 206315309
|
|
|
|
|
|
|
|
| |
Use the Bash runfiles library under @bazel_tools,
do not depend on it from source.
RELNOTES: none
PiperOrigin-RevId: 206312278
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 206310700
|
|
|
|
|
|
|
| |
chrome://tracing is able to load gzipped profiles out of the box.
RELNOTES: None
PiperOrigin-RevId: 206308018
|
|
|
|
|
|
|
|
|
|
| |
At this time, this is only implemented for the StandaloneTestStrategy.
This solves a race condition on Posix-like systems, where we cannot guarantee that the pipes are actually fully flushed to disk when the test process exits, and this can cause the test.xml to be empty, which makes it hard to debug issues. (The test.log files do not show up in normal CI systems, only the test.xml files.)
Progress on #4608.
PiperOrigin-RevId: 206292179
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When the experimental UI is asked to limit its overall output, reserve a certain
fraction for output to be generated after the build is complete. In this way,
at least a final status, or a bit of the test summary, is shown.
Also, to help staying within the limit also for small limits, from a certain
threshold onwards, more severely restrict the output we allow for each individual
action.
Change-Id: I912aec0dd17639d9864133a10359f93537b473ad
PiperOrigin-RevId: 206288651
|
|
|
|
|
| |
RELNOTES:none
PiperOrigin-RevId: 206287557
|
|
|
|
|
|
|
| |
This was missed in earlier patch.
RELNOTES: None.
PiperOrigin-RevId: 206276771
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Reporting strict deps errors in addition to attribution errors is helpful
particularly with code-generating annotation processors that may fail due
to missing transitive deps. Currently those failures prevent add_dep
suggestions from being emitted, making the problem harder to diagnose.
The presence of other errors may prevent some SJD issues from being detected,
but in theory should never lead to spurious SJD errors from being reported,
so the additional errors should generally be helpful.
PiperOrigin-RevId: 206261677
|
|
|
|
|
|
|
|
|
|
|
|
| |
and just skip the diagnostics at the end if strict deps errors are disabled.
This is necessary to javac-turbine, where we don't report strict deps errors
(we rely on JavaBuilder for enforcement) but where we still want to emit
jdeps.
See also bazelbuild/rules_scala#559
PiperOrigin-RevId: 206257304
|
|
|
|
|
|
|
|
| |
classpath is
non-empty but there are no annotation processors to run.
PiperOrigin-RevId: 206244327
|
|
|
|
|
|
|
| |
Previously, only trivial relative paths (within the same package) were handled correctly. Now paths such as ":foo/bar.bzl" are handled appropriately.
RELNOTES: None.
PiperOrigin-RevId: 206237161
|
|
|
|
|
|
| |
used at the start of execution.
PiperOrigin-RevId: 206230049
|
|
|
|
|
|
|
|
|
| |
This forces the ex-default to be explicit in a lot of tests, but I'd rather that than have the risk of implicit md5-use in production code.
To keep this CL smaller, do not remove the default from UnixFS quite yet.
RELNOTES: None.
PiperOrigin-RevId: 206223521
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
as a list, rather than as a single line (i.e., newline delimited rather than
space delimited).
Before:
SUBCOMMAND: # //src/main/java/com/google/devtools/build/lib:string_util [action 'Building src/main/java/com/google/devtools/build/lib/libstring_util.jar (2 source files) [for host]']
(cd /tmp/devbazel_output_base/execroot/io_bazel && \
exec env - \
LC_CTYPE=en_US.UTF-8 \
external/embedded_jdk/bin/java -XX:+UseParallelOldGC -XX:-CompactStrings '--add-exports=jdk.compiler/com.sun.tools.javac.api=ALL-UNNAMED' '--add-exports=jdk.compiler/com.sun.tools.javac.code=ALL-UNNAMED' '--add-exports=jdk.compiler/com.sun.tools.javac.comp=ALL-UNNAMED' '--add-exports=jdk.compiler/com.sun.tools.javac.file=ALL-UNNAMED' '--add-exports=jdk.compiler/com.sun.tools.javac.main=ALL-UNNAMED' '--add-exports=jdk.compiler/com.sun.tools.javac.tree=ALL-UNNAMED' '--add-exports=jdk.compiler/com.sun.tools.javac.util=ALL-UNNAMED' '--add-opens=jdk.compiler/com.sun.tools.javac.file=ALL-UNNAMED' '--patch-module=java.compiler=external/bazel_tools/third_party/java/jdk/langtools/java_compiler.jar' '--patch-module=jdk.compiler=external/bazel_tools/third_party/java/jdk/langtools/jdk_compiler.jar' '--add-opens=java.base/java.nio=ALL-UNNAMED' -jar external/bazel_tools/tools/jdk/JavaBuilder_deploy.jar @bazel-out/host/bin/src/main/java/com/google/devtools/build/lib/libstring_util.jar-2.params)
After:
SUBCOMMAND: # //src/main/java/com/google/devtools/build/lib:string_util [action 'Building src/main/java/com/google/devtools/build/lib/libstring_util.jar (2 source files) [for host]']
(cd /tmp/devbazel_output_base/execroot/io_bazel && \
exec env - \
LC_CTYPE=en_US.UTF-8 \
external/embedded_jdk/bin/java \
-XX:+UseParallelOldGC \
-XX:-CompactStrings \
'--add-exports=jdk.compiler/com.sun.tools.javac.api=ALL-UNNAMED' \
'--add-exports=jdk.compiler/com.sun.tools.javac.code=ALL-UNNAMED' \
'--add-exports=jdk.compiler/com.sun.tools.javac.comp=ALL-UNNAMED' \
'--add-exports=jdk.compiler/com.sun.tools.javac.file=ALL-UNNAMED' \
'--add-exports=jdk.compiler/com.sun.tools.javac.main=ALL-UNNAMED' \
'--add-exports=jdk.compiler/com.sun.tools.javac.tree=ALL-UNNAMED' \
'--add-exports=jdk.compiler/com.sun.tools.javac.util=ALL-UNNAMED' \
'--add-opens=jdk.compiler/com.sun.tools.javac.file=ALL-UNNAMED' \
'--patch-module=java.compiler=external/bazel_tools/third_party/java/jdk/langtools/java_compiler.jar' \
'--patch-module=jdk.compiler=external/bazel_tools/third_party/java/jdk/langtools/jdk_compiler.jar' \
'--add-opens=java.base/java.nio=ALL-UNNAMED' \
-jar \
external/bazel_tools/tools/jdk/JavaBuilder_deploy.jar \
@bazel-out/host/bin/src/main/java/com/google/devtools/build/lib/libstring_util.jar-2.params)
RELNOTES: --subcommands can now take a "pretty_print" value ("--subcommands=pretty_print") to print the
arguments of subcommands as a list for easier reading.
PiperOrigin-RevId: 206213009
|
|
|
|
| |
PiperOrigin-RevId: 206203357
|
|
|
|
| |
PiperOrigin-RevId: 206195967
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 206195789
|
|
|
|
|
|
| |
Similar to the sequence number, the timestamp should be immutable and computed when the event is enqueued (not at serialization time).
PiperOrigin-RevId: 206186036
|
|
|
|
|
|
| |
https://github.com/bazelbuild/bazel/commit/9b29a1bd7bbe37500b28a6508cb82ca1943c75b5
PiperOrigin-RevId: 206182289
|
| |
|
|
|
|
|
|
|
|
| |
Instead of using the default thread pool size of 200, use the number set for
the loading phase. This is in preparation for interleaving the loading and
target pattern eval phases.
PiperOrigin-RevId: 206172915
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 206157591
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is accomplished by:
- Setting the APPLE_CROSSTOOL configuration distinguisher in AppleCrosstoolTransition
- Doing nothing in AppleCrosstoolTransition in case we are already in an Apple configuration so that funky use cases like a binary having a dependency on a swift_library both directly and through an objc_library work
- Adding the "apl-" prefix to the output directory name in APPLE_CROSSTOOL configurations
Plus a few minor cleanups:
- Removed some unused methods
- Nopped out --enable_apple_crosstool_transition if the new flag is set
- Nopped out --target_uses_apple_crosstool if the new flag is set
These latter reduce the possible space of Apple configurations, thus making the code a bit more comprehensible.
RELNOTES: None.
PiperOrigin-RevId: 206157413
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 206156886
|
|
|
|
|
|
|
| |
This significantly reduces the size of the resulting profiles. Do we need the
events that I remove? What do we do with the data? Who knows?
PiperOrigin-RevId: 206153368
|