| Commit message (Collapse) | Author | Age |
|
|
|
| |
PiperOrigin-RevId: 185728682
|
|
|
|
|
|
| |
Roll forward of unknown commit
PiperOrigin-RevId: 185727344
|
|
|
|
|
| |
Change-Id: I636d98fdee72c1cae7547f1dc26f78fe4b3e0bb3
PiperOrigin-RevId: 185723619
|
|
|
|
|
|
| |
just as well as the target.
PiperOrigin-RevId: 185721605
|
|
|
|
|
|
|
| |
This avoids iterator, string builder, and string garbage.
RELNOTES: None
PiperOrigin-RevId: 185703066
|
|
|
|
|
|
|
| |
statistics tests.
RELNOTES: None.
PiperOrigin-RevId: 185700811
|
|
|
|
| |
PiperOrigin-RevId: 185694489
|
|
|
|
|
|
|
|
| |
MacOSX's `mktemp` command requires the template parameter.
Closes #4576.
PiperOrigin-RevId: 185686952
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Breaks Kokoro and I accidentally submitted the change without presubmit checks.
*** Original change description ***
Make __init__.py files creation optional
Introduce a new attribute to py_binary and py_test to control whether to
create `__init__.py` or not.
Fixes https://github.com/bazelbuild/rules_python/issues/55
Closes #4470.
PiperOrigin-RevId: 185676592
|
|
|
|
|
|
|
|
|
|
|
| |
Introduce a new attribute to py_binary and py_test to control whether to
create `__init__.py` or not.
Fixes https://github.com/bazelbuild/rules_python/issues/55
Closes #4470.
PiperOrigin-RevId: 185672243
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The Windows native {java,py,sh}_binary launcher
now picks up the RUNFILES_MANIFEST_FILE and
RUNFILES_DIR envvars from the environment. This
enables running such binaries even when they are
data-dependencies of other binaries and thus have
no runfiles (manifest or directory) of their own.
See https://github.com/bazelbuild/bazel/issues/4460
Change-Id: I1bc8e30f81b9932ea7c96ded2717ac9d0600403d
PiperOrigin-RevId: 185656004
|
|
|
|
|
|
|
|
|
|
| |
We can now compile
//src/tools/singlejar:token_stream on Windows.
See https://github.com/bazelbuild/bazel/issues/2241
Change-Id: I98f86e608e5ebaf685e4de26b2dabe75fcca78d2
PiperOrigin-RevId: 185655986
|
|
|
|
|
|
|
| |
Fixes MSVC C4311 pointer truncation warning.
Change-Id: Ic64168d620db010717189200c37c419cccac0653
PiperOrigin-RevId: 185653953
|
|
|
|
|
| |
Change-Id: Icbc478f87d622665b16c13c76518087ac089899e
PiperOrigin-RevId: 185645880
|
|
|
|
|
| |
Change-Id: Ib0c957de68a8a8035f2e13d7c9fe8d1549a3744d
PiperOrigin-RevId: 185645675
|
|
|
|
| |
PiperOrigin-RevId: 185624059
|
|
|
|
| |
PiperOrigin-RevId: 185609826
|
|
|
|
|
|
|
|
| |
concrete subclasses. Improve debugging message on serialization failures.
Lot of test-side changes to make sure aspects are properly registered with the RuleClassProvider.
PiperOrigin-RevId: 185607202
|
|
|
|
|
|
|
| |
Cleaning up references to {Des,S}erializationContext.UNTHREADED_PLEASE_REMOVE,
deleting the code is easier than deciding how to adapt context.
PiperOrigin-RevId: 185602054
|
|
|
|
|
|
| |
based on feature configuration
PiperOrigin-RevId: 185600940
|
|
|
|
|
|
| |
Also make AspectKey#toString a little more informative.
PiperOrigin-RevId: 185600069
|
|
|
|
| |
PiperOrigin-RevId: 185595397
|
|
|
|
|
| |
RELNOTES:None
PiperOrigin-RevId: 185590627
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 185580415
|
|
|
|
|
|
| |
are referenced by TopLevelTargets when we discard the analysis cache.
PiperOrigin-RevId: 185574670
|
|
|
|
|
|
|
|
| |
parameter isn't present. Allows us to handle cases where the class type encodes the parameter value. This also gives a compile-time check that field is present before blindly using it in codec.
Lets us get rid of a non-AutoCodec class.
PiperOrigin-RevId: 185573686
|
|
|
|
|
|
|
| |
expr - the expression to be evaluated
word - the configuration (represented by the strings 'host', 'target', or 'null') to try to find the result(s) of 'expr' in. If some but not all results of expr can be found in the specified config, then the subset that can be is returned. If no results of expr can be found in the specified config, then an error is thrown.
PiperOrigin-RevId: 185572590
|
|
|
|
|
|
|
| |
Added a little javadoc and tests.
RELNOTES: None
PiperOrigin-RevId: 185569985
|
|
|
|
|
|
|
|
|
|
|
|
| |
I neglected to unify the message text before submit. This uses the Go version
for both go and Java.
R=laurentlb,mkanat
CC=blaze-firehose+cl
RELNOTES:
unifly lint glob(["**/*.java"]) message
PiperOrigin-RevId: 185569422
|
|
|
|
|
|
|
|
| |
Remove WalkableGraph#isUpToDate and BuildDriver#alreadyEvaluated and delegate the
work to implementation.
RELNOTES: None
PiperOrigin-RevId: 185562370
|
|
|
|
|
|
|
|
|
|
|
| |
The values (if present) are written into the manifest with this format:
Target-Label: <label>
Injecting-Rule-Kind: <kind>
In the future, JavaBuilder will make sure of this instead of command line arguments to find owners for jars for its add_dep commands.
PiperOrigin-RevId: 185557317
|
|
|
|
| |
PiperOrigin-RevId: 185556666
|
|
|
|
|
| |
RELNOTES:None
PiperOrigin-RevId: 185553306
|
|
|
|
|
|
| |
(Des|S)erializationContext.
PiperOrigin-RevId: 185547740
|
|
|
|
|
|
|
|
|
|
|
| |
ControlFlowChecker has a precondition check that assumes nested functions do not occur. While this assumption is reasonable for a valid Skylark syntax, linter can actually be invoked on malformed files and users would get a stack trace instead of a human-readable linter error.
Alternative and possibly a better strategy would to not run CFChecker in case parse errors are detected.
fixes #4511
Closes #4512.
PiperOrigin-RevId: 185538897
|
|
|
|
|
|
|
| |
try-with-resources code segments
RELNOTES:None
PiperOrigin-RevId: 185536875
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 185535264
|
|
|
|
| |
PiperOrigin-RevId: 185528799
|
|
|
|
|
|
|
| |
CppConfiguration
RELNOTES: None.
PiperOrigin-RevId: 185527875
|
|
|
|
|
|
|
|
|
|
| |
"blaze run --direct_run" so that the called binary knows about the working directory the client was called from.
Its cwd is its runfiles directory and if not for the fact that we have to convey *two* directories to it, I'd have considered changing that. As it is, however, we can't convey two directories with the cwd of the binary so we have to use environment variables.
RELNOTES[NEW]: "blaze run --direct_run" now exports the BUILD_{WORKSPACE,WORKING}_DIRECTORY variables to tell the binary about the cwd of the client and the workspace root.
PiperOrigin-RevId: 185515884
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add new flag called `--local_tmp_root`, which (if
specified) tells Bazel what temp directory should
locally executed actions use.
Fixes https://github.com/bazelbuild/bazel/issues/4621
Related to https://github.com/bazelbuild/bazel/issues/3215
RELNOTES[NEW]: The new "--local_tmp_root=<path>" flag allows specifying the temp directory for locally executed actions.
Change-Id: Ice69a5e63d0bf4d3b5c9ef4dbdd1ed1c5025f85e
PiperOrigin-RevId: 185509555
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add an optional 'shallow_since' parameter to new_git_repository to allow
more shallow clones. As opposed to a fixed depths, specifying a date does
not get outdated if the branch progresses further.
Also, use fully shallow clones if no commit is specified. A (floating)
branch or tag can always be cloned in a truly shallow fashion.
Improves on #4359.
Change-Id: I8459c8f55042c98da2e43f57b7960a291004d26b
PiperOrigin-RevId: 185504534
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
https://github.com/bazelbuild/bazel/issues/4625
What I thought was a short fix is turning into a long hunt, so I better roll this back to get the build green again.
I'm not yet 100% certain what the interactions are, but there's a chance that it's back to the drawing board.
*** Original change description ***
Fixing test-setup.sh occasionally missing stdout/stderr, on systems where "tail --pid" is supported.
The solutions aren't mine, the new test was taken from Ola's unknown commit and the way to avoid race condition courtesy of sethkoehler@
Mitigates #4608 for compatible Linux systems.
TESTED=manual scripts and new test case.
RELNOTES: None
PiperOrigin-RevId: 185482604
|
|
|
|
|
|
| |
Fixes #4614
PiperOrigin-RevId: 185474153
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 185455486
|
|
|
|
|
|
|
|
| |
- Add a TOC for document sections
- Consistently capitalize section titles
- Upgrade "Functions" to a top-level section, since this is an important reference point
PiperOrigin-RevId: 185446368
|
|
|
|
|
|
| |
Previously, RuleContext was referenced via the objc implementation of CppSemantics. Objects of that class are no longer held by CppCompileAction post-analysis.
PiperOrigin-RevId: 185446320
|
|
|
|
| |
PiperOrigin-RevId: 185441432
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 185436886
|
|
|
|
|
|
|
| |
compile time.
RELNOTES: None.
PiperOrigin-RevId: 185432867
|