| Commit message (Collapse) | Author | Age |
... | |
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 177460834
|
|
|
|
| |
PiperOrigin-RevId: 177459771
|
|
|
|
|
|
|
| |
Replace code definitions that cannot be recognised by Jekyll with standard
definitions.
PiperOrigin-RevId: 177453968
|
|
|
|
| |
PiperOrigin-RevId: 177453738
|
|
|
|
| |
PiperOrigin-RevId: 177452571
|
|
|
|
|
|
|
|
|
|
|
|
| |
Don't make copies of Events on replay. The same events may be replayed a lot,
so it's better to copy before storing the events. Also avoid a copy if the
tag doesn't actually change.
The intent of this change is to reduce gc churn on incremental builds. When
I wrote this change (~a year ago), this was a noticable source of gc churn in
some benchmarks I ran at the time.
PiperOrigin-RevId: 177450696
|
|
|
|
|
|
|
| |
This is a partial roll-forward of https://github.com/bazelbuild/bazel/commit/e8d32b7c922f65539b74357711d5ad6b70934115, which was rolled back due to
genrule breakages - this part doesn't affect genrules, so it should be safe.
PiperOrigin-RevId: 177450542
|
|
|
|
| |
PiperOrigin-RevId: 177447905
|
| |
|
|
|
|
|
|
|
| |
Also, minor fix for the += operator check.
RELNOTES: None.
PiperOrigin-RevId: 177444203
|
|
|
|
|
| |
RELNOTES: in the Label() function, relative_to_caller_repository is now deprecated.
PiperOrigin-RevId: 177443907
|
|
|
|
|
|
|
|
|
|
| |
Bazel should display the root cause of a test failure to the user. For
example, if a test could not be executed on a remote executor due to
there being no network connection, then it shouldn't display the test
as failed but tell the user about the network error.
RELNOTES:
PiperOrigin-RevId: 177439578
|
|
|
|
|
|
|
|
|
|
|
| |
Slow read: a 1253924941-byte read from image.tar.gz took 5396ms.
is 221 MB/s, which is smokin' fast, not slow :P
Fixes: #3967
Change-Id: Ieca7464e0a670ade52f80172408334c9fc3a5b52
PiperOrigin-RevId: 177438364
|
|
|
|
|
|
|
| |
Debug messages (generated with Skylark's `print` function) used to be filtered out by the output filter: if such messages are generated during the analysis phase in a package different to the target package (e.g. if a user builds //foo:foo and the message is generated in a dependency //bar:bar), the message are not shown by default, which makes an erroneous impression that the code for //bar:bar hasn't been executed at all and interferes with debugging. Now the output filter doesn't affect debug messages at all.
RELNOTES: Debug messages generated by `print()` are not being filtered out by --output_filter anymore, it's recommended not to use them in production code.
PiperOrigin-RevId: 177431255
|
|
|
|
| |
PiperOrigin-RevId: 177428407
|
|
|
|
|
|
|
|
|
|
|
| |
It was previously sending each label individually over gRPC, where each call
has a lot of overhead.
This makes queries with a large amount of output _a lot_ faster. For an example
query where all packages are already loaded, I observe a difference of ~3.5s
before this change to ~1.6s after this change.
PiperOrigin-RevId: 177426957
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 177420511
|
|
|
|
|
|
|
|
|
| |
everywhere instead of duplicating process-wrapper --shell_arguments in Blaze.
To avoid a cyclic dependency, I broke up exec/local:local into exec/local:local and exec/local:options.
RELNOTES: None.
PiperOrigin-RevId: 177419268
|
|
|
|
|
|
| |
Follow-up to https://github.com/bazelbuild/bazel/commit/0b2352de3101e87647d083f6089246079dda0f75
PiperOrigin-RevId: 177415788
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 177414939
|
|
|
|
|
|
|
|
| |
This change allows java_plugins to be enabled for the set of packages
described by a package group, using a new java_plugin_configuration rule
that can be added to a java_toolchain configuration.
PiperOrigin-RevId: 177410831
|
|
|
|
|
|
|
| |
//third_party/protobuf:protoc dependency to process_wrapper_test.
RELNOTES: None.
PiperOrigin-RevId: 177399066
|
|
|
|
|
|
|
| |
crashing.
RELNOTES: None
PiperOrigin-RevId: 177376100
|
|
|
|
|
|
|
|
|
| |
Make variables are derived from toolchain.
This will allow c++ targets to use c++ Make variables once platforms are
activated without declaring an explicit dependency on the c++ toolchain.
PiperOrigin-RevId: 177365568
|
|
|
|
|
|
|
|
|
| |
rules with access to the CcToolchainProvider.
cc_common is required to migrate open-source users of the Skylark endpoints on
CppConfiguration to CcToolchainProvider.
PiperOrigin-RevId: 177364710
|
|
|
|
|
|
|
| |
This key context can be used by actions to share partial key computations, for instance when computing MD5s for nested sets.
RELNOTES: None
PiperOrigin-RevId: 177359607
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 177342763
|
|
|
|
|
|
|
| |
If the check is useful, it can be done in the linter.
RELNOTES: None.
PiperOrigin-RevId: 177342483
|
|
|
|
| |
PiperOrigin-RevId: 177341750
|
|
|
|
| |
PiperOrigin-RevId: 177339358
|
|
|
|
|
|
| |
deps from a compressed GroupedList without uncompressing it. Also some minor GC improvements.
PiperOrigin-RevId: 177338852
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 177337384
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 177332323
|
|
|
|
|
|
|
| |
The previous change was accidental.
RELNOTES: None.
PiperOrigin-RevId: 177330228
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 177326265
|
|
|
|
|
|
|
|
| |
purportedly to diagnose issue #4181.
My real hope is to achieve the effect I got in discard_graph_edges_test, where the debugging messages seem to have made the flakiness go away, but since this is less multithreaded, I'm less hopeful.
PiperOrigin-RevId: 177325229
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 177321286
|
|
|
|
|
|
| |
more logically belongs with other c++ rule types.
PiperOrigin-RevId: 177313718
|
|
|
|
|
|
|
|
|
| |
According to the SimpleBlobStore interface `containsKey` should look up blobs in the CAS. However, the URL it requests is missing `CAS_PREFIX`,
so it will never find anything.
Closes #4118.
PiperOrigin-RevId: 177313658
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
and expose transitive source jars to Skylark.
Initial change was rolled back (unknown commit). java_common.compile wouldn't fill the JavaRuleOutputJarsProvider when there was only one input source jar. Fixed that and added test (there was one before, but didn't check this particular provider).
Slightly refactor java classes to take in specific host javabase inputs and host java executable for creating the source jar, instead of always relying on fetching them from native java rules specific attributes.
Creating the output source jar in java_common.compile makes the behavior more similar to java_library.
Exposing the transitive_source_jars to Skylark helps with the Skylark migration from the old 'java' provider to JavaInfo.
Progress on #2614.
RELNOTES: transitive_source_jars is now exposed on JavaInfo.
PiperOrigin-RevId: 177311138
|
|
|
|
|
|
|
|
| |
The usage is `strip_prefix` not `strip-prefix`.
Closes #4162.
PiperOrigin-RevId: 177311042
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 177311029
|
|
|
|
|
|
| |
It'd be nice to go further and break out a bunch of this code into more generally useful places (especially for callers that don't care about aspects). But that's a big mess and beyond the scope of what I'm aiming for here.
PiperOrigin-RevId: 177307854
|
|
|
|
|
|
|
|
| |
Add Java to list of supported programming languages.
Closes #4095.
PiperOrigin-RevId: 177307650
|
|
|
|
|
|
|
|
|
|
| |
Links to cpp use cases outside of tutorial directory.
Fixes #4174 (I think?)
Closes #4175.
PiperOrigin-RevId: 177307565
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This fixes the following error I got when building from scratch on Raspbian:
```
src/main/protobuf/invocation_policy.proto: File not found.
src/main/protobuf/command_line.proto: File not found.
```
Note:
```
protoc --version
libprotoc 3.0.0
```
Closes #4187.
PiperOrigin-RevId: 177306773
|
|
|
|
|
|
|
|
| |
- Support custom ancestors and rule implementations.
- Refactor defaults into MockRuleDefaults.
- More thorough documentation.
PiperOrigin-RevId: 177303642
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When I clone from a git repo that doesn't have the default branch the same as the branch that I want ; it doesn't seem to fetch the appropriate branch. I am using a name rather than explicit sha.
What happens is:
```
+ git reset --hard build-with-bazel
fatal: ambiguous argument 'build-with-bazel': unknown revision or path not in the working tree.
```
because it hasn't fetched that ref.
Closes #4039.
PiperOrigin-RevId: 177298578
|
|
|
|
|
|
|
|
| |
Extend the protocol to support also showing meta data about
an action execution, if the underlying test action is able
to report it.
PiperOrigin-RevId: 177294531
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
interconnected with 'main_class' in java_test rule.
for manual testing I used BUILD file:
java_test(
name = "mytest",
srcs = glob(["*.java"]),
main_class = "com.test.Test",
use_testrunner = 1,
)
RELNOTES: java_tests no complain when use_testrunner is explicitly set to 1 and main_class is set.
PiperOrigin-RevId: 177291746
|