| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
| |
On some systems, the dprintf header is only part of <stdio.h> if
requested (to allow compatibility with applications before the
standardization of dprintf). As we use dprintf, request it
by defining _WITH_DPRINTF.
Change-Id: Ia4a80e08760043c5343b4c333b146f4ea87d081b
PiperOrigin-RevId: 171409630
|
|
|
|
|
|
|
|
|
|
| |
Building with --experimental_discard_orphaned_artifacts will cause the .imports
file produced by the LTO indexing action to not be preserved, unless it is marked
as an input to the LTOBackendAction. It is only used in the input discovery phase,
not as an input to the actual action, so it was not initially listed as an input.
RELNOTES: None
PiperOrigin-RevId: 171387388
|
|
|
|
|
|
|
|
| |
catastrophes. Our stricter behavior in the face of errors means that it is no longer possible for a done node to depend on a not-done node in this build.
This opens up the possibility to discard graph edges on all --batch builds, or at least those with --discard_analysis_cache.
PiperOrigin-RevId: 171375405
|
|
|
|
|
|
|
| |
This should catch breakages due to changes in the AIDL tools bundled in the SDK.
Change-Id: Iaff6ce058112a57b2b8da3e00a1172ee49cfdd85
PiperOrigin-RevId: 171357883
|
|
|
|
|
|
|
|
|
| |
ActionContexts, etc., so that SpawnResult metadata is returned upwards.
Note that the TODOs mostly refer to changes that will appear in a subsequent CL (a CL to return SpawnResults, contained in ActionResults, from Actions/AbstractActions). I split off the remaining SpawnResult-related changes into this CL and kept the ActionResult-related changes separate.
RELNOTES: None.
PiperOrigin-RevId: 171355611
|
|
|
|
|
|
|
|
| |
Micro-optimize a few hot code paths which have a habit of iterating over short O(1)-access
lists.
RELNOTES: None
PiperOrigin-RevId: 171347524
|
|
|
|
|
| |
RELNOTES: n/a
PiperOrigin-RevId: 171344856
|
|
|
|
|
|
|
|
|
| |
SkylarkSemanticsCodec
Note that the syntax package and its test package still depend indirectly on the options parser via other Bazel-specific packages.
RELNOTES: None
PiperOrigin-RevId: 171342823
|
|
|
|
|
|
|
| |
Fixes #3846.
Change-Id: Ic510c539dfe321aa9a679cee7143fee77a17acc5
PiperOrigin-RevId: 171332064
|
|
|
|
|
|
| |
of Ubuntu instructions.
PiperOrigin-RevId: 171312843
|
|
|
|
|
|
|
| |
load.
RELNOTES: None
PiperOrigin-RevId: 171298089
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Also:
- check as the first thing in compile.sh that we
can locate the GNU coreutils, and remove the
duplicate check for the same thing on Windows
- check early in compile.sh that we can access
python.exe
Fixes https://github.com/bazelbuild/bazel/issues/3863
Change-Id: Ib48b405cf93eafd48e21b280bcbab4d45117c1d9
PiperOrigin-RevId: 171291435
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In this commit:
- testenv.sh no longer runs Bazel in a subshell
- testenv.sh prints informative log messages that
show the origin (testenv.sh) and the date
- testenv.sh logs to $TEST_log by appending to it,
not by overwriting it
This change speeds up
//src/test/shell/bazel:bazel_windows_example_test from
~260s to ~165s.
On Windows, Bash (MSYS) waits for all subprocesses
of a subshell to terminate before allowing the
subshell itself to terminate too, even if some
subprocesses are daemons.
I think this is a bug, and it's the culprit of
https://github.com/bazelbuild/bazel/issues/3148
Change-Id: If97ea6dfeb904af560b291a7acebd09e43863ab4
PiperOrigin-RevId: 171267462
|
|
|
|
|
|
|
| |
Also remove the use of the @UsesOnlyCoreTypes annotation on SkylarkSemanticsOptions. It was only there to help mark that the options class was safe to put in Skyframe.
RELNOTES: None
PiperOrigin-RevId: 171248504
|
|
|
|
| |
PiperOrigin-RevId: 171245323
|
|
|
|
|
|
| |
potentially more principled than just accessing the execRoot willy-nilly.
PiperOrigin-RevId: 171234480
|
|
|
|
|
|
|
|
| |
1. Prevent a redundant map.get() in SkyframeFilesetManifestAction#establishSkyframeDependencies
2. Make a more memory efficient FilesetEntrykey instead of reusing the LegacySkyKey.
RELNOTES: none
PiperOrigin-RevId: 171222499
|
|
|
|
| |
PiperOrigin-RevId: 171221156
|
|
|
|
| |
PiperOrigin-RevId: 171209823
|
|
|
|
|
|
|
|
|
|
|
| |
Because OFD locks are not per-process, F_OFD_GETLK does not report which
process holds the lock, so we use the contents of the lock file instead.
Works around a Linux kernel bug where POSIX record locks are lost at
execve() if any other threads exist.
RELNOTES: None.
PiperOrigin-RevId: 171209685
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 171205009
|
|
|
|
|
|
|
| |
inadvartently lost due to https://github.com/bazelbuild/bazel/commit/d8ba904a3b0598e97601bc670840e39f21799ead
RELNOTES: none
PiperOrigin-RevId: 171204884
|
|
|
|
| |
PiperOrigin-RevId: 171193160
|
|
|
|
|
|
|
| |
Currently, this whitelist includes every package.
RELNOTES: None
PiperOrigin-RevId: 171192613
|
|
|
|
|
|
|
|
|
|
| |
1. Add a fingerprint of the FilesetTraversalParams rather than the transitive closure of its attributes, while adding the FilesetTraversalParams to a Fingerprint.
2. Memoize the above fingerprint computations as well as hashCode computations for FilesetTraversalparams.
Use AutoValue's @Memoize as well as equals and hashcode to simplify the code.
RELNOTES: None
PiperOrigin-RevId: 171191126
|
|
|
|
| |
PiperOrigin-RevId: 171180273
|
|
|
|
|
|
| |
*** Reason for rollback ***
PiperOrigin-RevId: 171177811
|
|
|
|
| |
PiperOrigin-RevId: 171176871
|
|
|
|
|
|
|
| |
Added @RunWith, and modified test data to satisfy arg requirements.
RELNOTES: None
PiperOrigin-RevId: 171175255
|
|
|
|
|
|
|
| |
When --define EXECUTOR=remote is specified in bazel command, embedded
tools 'launcher' will be compiled remotely from source.
PiperOrigin-RevId: 171172084
|
|
|
|
|
|
|
|
|
| |
Fixes https://github.com/bazelbuild/bazel/issues/3777
Also adds a proguard integration test so that hopefully we notice next time it breaks.
RELNOTES: Updated Android proguard to 5.3.3. It now works with android-24+.
PiperOrigin-RevId: 171162295
|
|
|
|
|
|
|
|
| |
Unfortunately, since the invocation policy gets enforced on a user's command line early in the command environment setup, so the effective log level is not yet set. For this run, keep the logs at INFO, since any other level will disappear into the ether.
InvocationPolicy gets enforced not only at invocation startup but also elsewhere to recompute the default values. The log statements from these different runs overwhelm the log output from our tests, making it hard to find other events without filtering the log. Make all extra invocation policy enforcements log at FINE so that they only appear when extra detail is requested.
PiperOrigin-RevId: 171151573
|
|
|
|
| |
PiperOrigin-RevId: 171140260
|
|
|
|
|
|
|
| |
These depend on package loading and thus must be gone.
RELNOTES: None.
PiperOrigin-RevId: 171132297
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Introduce LauncherFileWriteAction, a
FileWriteAction that can create a native
{java,sh,py}_binary launcher from the launcher
stub and the user-specified launch information.
The LauncherFileWriteAction class does not use the
"copy" command of cmd.exe so it's not restricted
with path lengths.
The class stores a LaunchInfo object, which
describes the launch data that the launcher stub
reads to identify its payload.
The LaunchInfo is a lazy object, similar to
CustomCommandLine. LaunchInfo won't fully
construct the launch data until it is about to
write the data to the output. Thus LaunchInfo is
memory efficient because it won't create any
String objects in the analysis phase that it would
only read in the execution phase.
Fixes https://github.com/bazelbuild/bazel/issues/3802
Change-Id: I4ddd83369e7131d42e2e9b35f105ad2dc60bcc52
PiperOrigin-RevId: 171115105
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 171113424
|
|
|
|
|
|
|
| |
Mainly this just means using getters instead of fields to access option values.
RELNOTES: None
PiperOrigin-RevId: 171101597
|
|
|
|
|
|
|
| |
getMethods ordering is not guaranteed and actually change
depending on minor difference in the class path.
PiperOrigin-RevId: 171093246
|
|
|
|
|
|
| |
the amount of *available* physical memory. This includes memory used as cache or buffer that will be evicted if an application requests memory, and is a much more realistic metric of utilization than free memory, which is usually <1% of memory available to the machine.
PiperOrigin-RevId: 171087122
|
|
|
|
|
|
| |
RELNOTES: android_binary now supports custom debug keys via the debug_key
attribute.
PiperOrigin-RevId: 171081759
|
|
|
|
|
|
|
|
| |
The current build on ci.bazel.io fails with "Rpmdb checksum is invalid: dCDPT(pkg checksums)"
errors and our favorite search engine seems to recommend to do a yum clean all to fix it.
Change-Id: I0d574d56755bf3ce6c8ea043b698f4e1ecc3ac27
PiperOrigin-RevId: 171064618
|
|
|
|
|
|
| |
malloc attribute.
PiperOrigin-RevId: 171061196
|
|
|
|
|
|
|
|
|
|
|
| |
This is a first step toward making the core Skylark interpreter (the syntax/ directory) not depend on the options parser. Subsequent CLs will replace uses of SkylarkSemanticsOptions within the interpreter with uses of SkylarkSemantics, and move SkylarkSemanticsOptions to the packages/ directory alongside SkylarkSemanticsCodec.
SkylarkSemantics will also replace SkylarkSemanticsOptions as the value that gets passed through Skyframe. This is nice because SkylarkSemantics is strictly immutable, whereas options classes are only kinda-sorta-immutable.
The downside is significantly more redundancy when defining new options. But some of the work is saved by using AutoValue, and there are tests that protect us from dumb mechanical errors. The details are outlined in the javadoc for SkylarkSemanticsOptions and SkylarkSemanticsConsistencyTest.
RELNOTES: None
PiperOrigin-RevId: 171060034
|
|
|
|
|
|
| |
RELNOTES: none
PiperOrigin-RevId: 171056169
|
|
|
|
| |
PiperOrigin-RevId: 171048721
|
|
|
|
|
|
| |
true anymore. Looks like now each build command instantiates its own BuildTool to work with instead of BlazeRuntime holding a single instance that gets re-used.
PiperOrigin-RevId: 171047696
|
|
|
|
|
|
|
| |
into a shell window.
RELNOTES: None.
PiperOrigin-RevId: 171047048
|
|
|
|
|
|
|
| |
This migration flag only affects Java rules.
RELNOTES: None.
PiperOrigin-RevId: 171026607
|
|
|
|
|
|
|
| |
section and rename to just "mobile-install".
RELNOTES: None.
PiperOrigin-RevId: 171021110
|
|
|
|
|
|
|
|
|
|
|
|
| |
xcode_config rule in addition to ctx.fragments.apple .
Subsequent Bazel versions won't support these methods on ctx.fragments.apple
and thus need to be updated.
Progress towards https://github.com/bazelbuild/bazel/issues/3424 .
RELNOTES: None.
PiperOrigin-RevId: 171021097
|