| Commit message (Collapse) | Author | Age |
|
|
|
| |
PiperOrigin-RevId: 202389874
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 202386363
|
|
|
|
| |
PiperOrigin-RevId: 202386041
|
|
|
|
|
|
|
|
|
| |
This is a much cleaner, more elegant approach than previous regex matching.
This still leaves room for unknown-name rule definitions, in case, for example, a user namespaces their rule definition not at the top level.
For example: "foo.bar = rule(...)"
RELNOTES: None.
PiperOrigin-RevId: 202380975
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 202364245
|
|
|
|
|
|
| |
FeatureConfiguration.
PiperOrigin-RevId: 202363333
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 202360925
|
|
|
|
|
|
|
|
|
|
| |
If there are multiple modules with the same name:
- If only one is marked 'documented', that one takes precedence.
- If one is a subclass of the others, the subclass takes precedence.
- Otherwise, an exception is thrown.
RELNOTES: None.
PiperOrigin-RevId: 202359443
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 202339577
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 202325860
|
|
|
|
|
|
| |
unless necessary.
PiperOrigin-RevId: 202317115
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Commit https://github.com/bazelbuild/bazel/commit/f5043d6831ea1c266104363b4e8911eb97f96fbc
was incorrect in that it cached the file names,
not the directory names.
This commit fixes that. I verified that the number
of calls to ExtractBlazeZipProcessor::Process is
greater than the calls to MakeDirectories within
(1038 vs. 172 on Linux).
See https://github.com/bazelbuild/bazel/issues/5444
Change-Id: I314bdc9337c9782a5ceaed7aac785a552b222b1f
Closes #5484.
Change-Id: I314bdc9337c9782a5ceaed7aac785a552b222b1f
PiperOrigin-RevId: 202314400
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add a simple profiler that can measure function
call counts and durations, and report statistics
by printing to stderr.
Motivation:
I recently needed a profiler for PR #5445 and
PR #5448, so I'm adding the polished code now.
Usage:
1. depend on //src/main/cpp/util:profiler
2. use StopWatch, Task, and ScopedTask objects
as shown in profiler.h's class documentation
See https://github.com/bazelbuild/bazel/issues/5444
Change-Id: I43f0afd124b486c694f451e8455a66ffca8137b6
Closes #5461.
Change-Id: I43f0afd124b486c694f451e8455a66ffca8137b6
PiperOrigin-RevId: 202314319
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The targets in //examples/shell:* now use the Bash
runfiles library in
@bazel_tools//tools/bash/runfiles and work on
Windows.
Also undef the RUNFILES_* envvars in
bazel_example_test::test_shell (which builds the
shell example project) so that the runfiles
library discovers its own runfiles instead of
trying (and failing) to use the enclosing test's
runfiles (which it shouldn't use, because the test
executes "bazel run //examples/shell:bin" so that
target's runfiles are independent of the enclosing
test's runfiles).
Fixes https://github.com/bazelbuild/bazel/issues/3839
Closes #5480.
Change-Id: I44f9bf9b11f7fac0e1c0995a44c2336846dc2bc8
PiperOrigin-RevId: 202313105
|
|
|
|
| |
PiperOrigin-RevId: 202311773
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 202308240
|
|
|
|
|
|
|
|
|
| |
The Skylark constructor of CcCompilationInfo now accepts headers. This may be
the last piece needed to get a working prototype of foreign C++ libraries. Next
step would be open sourcing the sandwich.
RELNOTES:none
PiperOrigin-RevId: 202306252
|
| |
|
|
|
|
|
|
|
|
| |
`estimated_size_` and `kMaximumOutputSize` are in `size_t` (`unsigned long long`) for 64-bit processor, but `%lu` only accept `unsigned long`. `%zu` will handle `size_t` for 32-bit and 64-bit processors correctly.
Closes #5473.
PiperOrigin-RevId: 202291659
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Update all runfiles libraries to have the same
header comment format, including the build rule
to depend on the namespace / header / module to
import
- Fix runfiles_test.cc to include the right files
(recent refactoring commit has split
src/main/cpp/util/path.cc from
file_[platform].cc)
- Change exported variable
_rlocation_isabs_pattern in runfiles.bash to be
upper-case, so it is visibly a variable and not
a function.
See https://github.com/bazelbuild/bazel/issues/4460
Change-Id: I17e18308506ab9f5c9f410ef6bc6b9df912d42a9
Closes #5481.
Change-Id: I17e18308506ab9f5c9f410ef6bc6b9df912d42a9
PiperOrigin-RevId: 202291629
|
| |
|
|
|
|
|
|
|
| |
of DefaultInfo() was used.
RELNOTES: None.
PiperOrigin-RevId: 202192091
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This skydoc rewrite uses an actual skylark interpreter with a faked build API (implementing the actual build API that Bazel uses).
There's a lot left to do here, this is a barebones start.
For example, this does not yet handle:
- load() statements
- non-global build API elements (e.g. apple_common)
- output of any rule information other than attribute names
- markdown output format
RELNOTES: None.
PiperOrigin-RevId: 202187207
|
|
|
|
|
|
| |
these values when being invoked.
PiperOrigin-RevId: 202173180
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 202167782
|
|
|
|
|
|
|
|
| |
Logger messages aren't printed to the console, they're written to /usr/local/google/tmp, and can be prohibitively large for these debug server logs.
Instead I'm going with your original suggestion in https://github.com/bazelbuild/bazel/commit/b74922932b25a71c626b47ea9a9afb7dbc506cec, and selectively suppressing debug events by wrapping the EventHandler on the way in to SkylarkDebugServer.
PiperOrigin-RevId: 202166571
|
|
|
|
|
|
|
|
|
| |
Consolidate the creation of JavaCompilationArgsProviders, and avoid explicit
handling of the 'direct' and 'recursive' cases in clients. Also add some
higher-level methods to the builder API to support adding dependencies
with dep/export/runtime_dep-like semantics.
PiperOrigin-RevId: 202166383
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 202162804
|
|
|
|
| |
PiperOrigin-RevId: 202162534
|
|
|
|
|
|
|
|
|
| |
CppCompileAction.discoverInputsStage2 retrieves values of discovered modules
from ActionExecutionValue.
This addresses a possible a correctness issue.
PiperOrigin-RevId: 202162180
|
|
|
|
| |
PiperOrigin-RevId: 202161910
|
|
|
|
| |
PiperOrigin-RevId: 202151257
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 202150316
|
|
|
|
|
|
|
| |
taken from https://releases.bazel.build/bazel-toolchains.html
RELNOTES: None
PiperOrigin-RevId: 202145248
|
|
|
|
|
|
|
| |
This was never used. We thought it will be useful, but it's not.
RELNOTES: None.
PiperOrigin-RevId: 202143524
|
|
|
|
|
|
|
| |
Makes it non-instantiable so that it's easier to migrate SWIG rules to Skylark.
RELNOTES:none
PiperOrigin-RevId: 202136054
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Also handle statements in conditional breakpoints.
This is more consistent with other common debuggers (e.g. java, python).
Calls Parser#parseStatement with local parsing level, so some statement types aren't handled (e.g. load statements), which is broadly consistent with other debuggers.
Assignment, augmented assignment, and return statements return a non-None value,
and simple expression statements still return the result of evaluating the expression.
TAG_CHANGE_OK=This proto has never yet been used
TYPE_CHANGE_OK=This proto has never yet been used
PiperOrigin-RevId: 202135678
|
|
|
|
|
|
|
|
|
|
|
|
| |
add helper JUnit TestWrapper class to do some action on test timeout
i.e. we want to dump the current state of the test on timeout before
exit
for the new junit integration test framework
Closes #5436.
PiperOrigin-RevId: 202123320
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 202118168
|
|
|
|
|
|
|
| |
they are used on the phone.
RELNOTES: None.
PiperOrigin-RevId: 202117007
|
|
|
|
|
|
| |
and for often required operations like creating file and its parent directories
PiperOrigin-RevId: 202115025
|
|
|
|
|
|
|
| |
As //tools/defaults will be deprecated soon. All usages of //tools/defaults:jdk and //tools/defaults:java_toolchain should be replaced by corresponding targets in //tools/jdk/BUILD package
RELNOTES:none
PiperOrigin-RevId: 202114489
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Before, Bazel expected that it can compile whatever appeared in cc_library.srcs
directory artifacts. That is true for C/C++ source files, and for headers when
the C++ toolchain supported header parsing/processing (which used
CppCompileAction). When the toolchain doesn't support header parsing/processing,
Bazel would crash.
Addresses issue #5092. One part of it.
Fixes #5372.
RELNOTES: None.
PiperOrigin-RevId: 202114286
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
the tests had been disabled for flakyness due to
timeouts. I think the right solution is remove the
individual test timeouts as on a highly loaded
machine fine grained timeouts typically don't make
much sense.
After removing the individual test timeouts no more
flakyness was found in 1000 runs.
Closes #5465.
PiperOrigin-RevId: 202113697
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Baseline: b93ae42e8e693ccbcc387841a17f58259966fa38
Cherry picks:
+ 4b80f2455e7e49a95f3a4c9102a67a57dad52207:
Add option to enable Docker sandboxing.
+ 6b1635279e8b33dc1ac505ac81825e38f8797a14:
Allow disabling the simple blob caches via CLI flag overrides.
+ 4ec0a7524913ab2c4641368e3f8c09b347351a08:
Use BUILD.bazel instead of BUILD for external projects
Incompatible changes:
- Bazel now always runs binaries in with "bazel run" in
interactive mode. The "--nodirect_run" command line option is now
a no-op.
- "bazel run --noas_test" is not supported anymore.
- Indentation on the first line of a file was previously ignored.
This is now fixed.
New features:
- C++,runfiles: to access data-dependencies (runfiles) in C++
programs, use the runfiles library built into Bazel. For usage
info, see
https://github.com/bazelbuild/bazel/blob/master/tools/cpp/runfiles
/runfiles.h
Important changes:
- Bazel now allows almost all 7-bit ASCII characters in labels.
- Remove vestigial java_plugin.data attribute
- Bazel supports including select Java 8 APIs into Android apps
targeting pre-Nougat Android devices with
--experimental_desugar_java8_libs
- Flag `--incompatible_disable_glob_tracking` is removed.
- SkyQuery's rbuildfiles now returns targets corresponding to
broken packages.
- Introduce build support for providing cache prefetch hints.
- Update the skylark DefaultInfo documentation to spell out
runfiles, data_runfiles and default_runfiles
- An internal action for symlinking runfiles will use Command
instead of a Spawns. This should have no functional chages; the
only user visible consequence should be that the internal action
is no longer be included in statistics when calculating processes
count.
- --batch is deprecated
- execution strategies line no longer handles differently the case
where all processes have the same strategy.
- The --experimental_remote_spawn_cache flag is now enabled by
default, and remote caching no longer needs --*_strategy=remote
flags (it will fail if they are specified).
- android_binary.aapt_version='aapt2' now supports en_XA and ar_XB
- Added --apple_enable_auto_dsym_dbg flag.
- non_propagated_deps has been removed from objc_library and
apple_binary.
- For Android projects, Bazel now supports building fonts as
resources. See
https://developer.android.com/guide/topics/ui/look-and-feel/fonts-in-xml
for more information on the feature.
- With --incompatible_no_support_tools_in_action_inputs enabled, Skylark
action inputs are no longer scanned for tools. Move any such
inputs to the newly introduced 'tools' attribute.
|
|
|
|
|
|
| |
Closes #5435.
PiperOrigin-RevId: 202100672
|
|
|
|
|
|
|
|
|
| |
To get a CcCompilationInfo instance from Skylark it will either have to be
through its constructor (not yet fully implemented) which will not schedule any
actions or through a call to compile() which does schedule actions.
RELNOTES:none
PiperOrigin-RevId: 202099841
|
|
|
|
|
|
|
|
|
| |
it consistently takes over 10 minutes for little
benefit on presubmit. we'll continue to run it on
postsubmit for every commit.
RELNOTES: None
PiperOrigin-RevId: 202094016
|
|
|
|
| |
PiperOrigin-RevId: 202092962
|
|
|
|
| |
PiperOrigin-RevId: 202023187
|