| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
correctly""
Roll-forward with fix: the original change did not produced any changelog if
this was not a release branch, use a default, empty one in that case. The
debian version number will then be LAST_VERSION~HEAD
This reverts commit e4cf9aa8b63173326cfe72ba76be4303bc038def.
--
Change-Id: I9e19b1132570ea20d90053734418f2703b1a641e
Reviewed-on: https://cr.bazel.build/7976
PiperOrigin-RevId: 142525180
MOS_MIGRATED_REVID=142525180
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
On ci.bazel.io local branch names are not set, so the release script
was not finding information about the master branch. If the master ref
does not exist, this change fall backs to looking at origin/master instead.
Fixes #2263.
To be cherry-picked for #2246.
--
Change-Id: Ibe4f3533e529d79917233d89951f88cb58d14ce3
Reviewed-on: https://cr.bazel.build/8033
PiperOrigin-RevId: 142524954
MOS_MIGRATED_REVID=142524954
|
|
|
|
|
|
|
|
|
|
| |
To be cherry-picked for #2246.
--
Change-Id: I50bbd7dc00e4305f36d9a2a3a8841d6d9bcd2bd7
Reviewed-on: https://cr.bazel.build/8034
PiperOrigin-RevId: 142524920
MOS_MIGRATED_REVID=142524920
|
|
|
|
|
|
|
|
|
|
| |
PathFragment.getParentDirectory() may return null. Fixes #2212.
Also adds coverage-specific attributes to the java_binary rule.
--
PiperOrigin-RevId: 142516883
MOS_MIGRATED_REVID=142516883
|
|
|
|
|
|
|
|
|
|
| |
This is needed to support both shrinking and splitting at the same time,
which will become the default for any android_binary which has splits
defined on it once shrinking becomes default (if it hasn't already).
--
PiperOrigin-RevId: 142497302
MOS_MIGRATED_REVID=142497302
|
|
|
|
|
|
|
|
|
|
| |
--experimental_transparent_compression flag
Also add test to ensure lazy strings aren't forced.
--
PiperOrigin-RevId: 142496520
MOS_MIGRATED_REVID=142496520
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 142494003
MOS_MIGRATED_REVID=142494003
|
|
|
|
|
|
|
|
| |
This clarifies documentation, renames or rearranges constructors, and defines a BuildConfiguration option that will be made to control transparent compression in a follow-up CL. The follow-up updates call sites to use the new create() factory method.
--
PiperOrigin-RevId: 142491333
MOS_MIGRATED_REVID=142491333
|
|
|
|
|
|
|
|
|
|
|
|
| |
If none is specified, the highest version installed in <sdk>/build-tools/ will
be used.
RELNOTES: android_sdk_repository build_tools_version is now optional. The
highest installed build-tools will be used if none is specified.
--
PiperOrigin-RevId: 142490569
MOS_MIGRATED_REVID=142490569
|
|
|
|
|
|
|
|
| |
lint-api.
--
PiperOrigin-RevId: 142489545
MOS_MIGRATED_REVID=142489545
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 142489262
MOS_MIGRATED_REVID=142489262
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 142484589
MOS_MIGRATED_REVID=142484589
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Breaks CI
"Parameter 'url' has no default value", see http://ci.bazel.io/view/Bazel%20bootstrap%20and%20maintenance/job/Bazel/JAVA_VERSION=1.7,PLATFORM_NAME=linux-x86_64/1104/console.
*** Original change description ***
Make Bazel build dot
This change has several parts, it:
* Adds a "make" repository rule, which runs ./configure && make on a
repository.
* Modifies the tar.gz decompressor to restore timestamps. This was
an issue with dot, as make examines the timestamp to determine if
files need to be rebuilt. Because Bazel was not preserving the
archive's timestamp, it was rebuilding things that it did not need to
(and, I think, exposed some bugs in dot's Makefile).
* Actually add dot as an externa...
***
--
PiperOrigin-RevId: 142469299
MOS_MIGRATED_REVID=142469299
|
|
|
|
|
|
|
|
|
|
| |
Previously it was assuming '$' was only present for inner classes,
but that isn't the case. This was causing problems specifically for
AutoValue extensions, which generate class names that start with '$'.
--
PiperOrigin-RevId: 142468150
MOS_MIGRATED_REVID=142468150
|
|
|
|
|
|
|
|
| |
crosstool.
--
PiperOrigin-RevId: 142459402
MOS_MIGRATED_REVID=142459402
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Broken by https://github.com/bazelbuild/bazel/commit/a4d0ea406e8622e305fc3253075cfee60da3d3d2
Reason is that we include both file_posix.cc and
file_windows.cc when compiling for MSYS, and I
forgot to put the POSIX implementation of
SplitPath/IsAbsolute/IsRootDirectory behind
`#ifndef __CYGWIN__`.
--
PiperOrigin-RevId: 142456232
MOS_MIGRATED_REVID=142456232
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change has several parts, it:
* Adds a "make" repository rule, which runs ./configure && make on a
repository.
* Modifies the tar.gz decompressor to restore timestamps. This was
an issue with dot, as make examines the timestamp to determine if
files need to be rebuilt. Because Bazel was not preserving the
archive's timestamp, it was rebuilding things that it did not need to
(and, I think, exposed some bugs in dot's Makefile).
* Actually add dot as an external repository. I made the dot-graph
target manual, so it won't be downloaded/built by the default //...
target.
* Remove dot scrubbing from the Bazel export process.
* Added some names to download_and_extract params, because it's really
annoying to only be able to reference them positionally.
--
PiperOrigin-RevId: 142452055
MOS_MIGRATED_REVID=142452055
|
|
|
|
|
|
| |
lombok-ast 0.2.3 and dependencies asm-analysis 5.0.4, asm-tree 5.0.4)
Change-Id: I37d82e442d660ebf6182c1196938125aa8be12c4
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Use/implement utility methods to join paths, check
if they are the root directory or are absolute,
etc. Doing so (instead of say checking if a path
starts with "/") allows for correct behavior on
Windows.
See https://github.com/bazelbuild/bazel/issues/2107
--
PiperOrigin-RevId: 142446027
MOS_MIGRATED_REVID=142446027
|
|
|
|
|
|
|
|
|
|
| |
Use $PATHSEP to create a Java classpath.
Fixes https://github.com/bazelbuild/bazel/issues/2262
--
PiperOrigin-RevId: 142445784
MOS_MIGRATED_REVID=142445784
|
|
|
|
|
|
|
|
|
|
|
| |
This allows correct behavior of Dirname and
Basename on Windows.
See https://github.com/bazelbuild/bazel/issues/2107
--
PiperOrigin-RevId: 142441234
MOS_MIGRATED_REVID=142441234
|
|
|
|
|
|
|
|
|
|
| |
linking.
This can lead to conflicts if done for non-test binary targets.
--
PiperOrigin-RevId: 142441056
MOS_MIGRATED_REVID=142441056
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 142438943
MOS_MIGRATED_REVID=142438943
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 142430323
MOS_MIGRATED_REVID=142430323
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In the Bazel client's file_test, when testing
multi-threaded pipe access, wait for all data to
be written into the pipe.
Pipes are not synchonization primitives in that
read(2) returns immediately, reading as much data
as it can, and won't block if it cannot read as
much as requested. (This is even tested by the
last ASSERT_EQ, trying to read 40 bytes.)
This is however also true for the second ASSERT_EQ
that attempts to read 5 bytes. The Send on the
writer_thread is racing with the Receive on the
main thread (as it should), and sometimes the main
thread wins, resulting in fewer bytes received
than previously expected.
--
PiperOrigin-RevId: 142429243
MOS_MIGRATED_REVID=142429243
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
which have converters that return lists. The problem was that the policy might,
say, disallow values ["a", "b"], and a flag --foo might have a converter which
takes a string and splits it by commas to produce a list. The options parser
would apply the converter to --foo=a,b to produce ["a", "b"], but invocation
policy would compare each element of the policy to the list itself, which will
never work.
--
PiperOrigin-RevId: 142297177
MOS_MIGRATED_REVID=142297177
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 142295816
MOS_MIGRATED_REVID=142295816
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit 9012bf1676bd6426229625e2567bfa399f89dabe.
Fixes #2260.
--
Change-Id: Ia08dd65d55274acdd15993cfde4eab225fb01df0
Reviewed-on: https://cr.bazel.build/8012
PiperOrigin-RevId: 142294105
MOS_MIGRATED_REVID=142294105
|
|
|
|
|
|
|
|
|
|
|
| |
Blaze and Bazel each use -isystem rather than -I when specifying "includes" for cc_* rules. This distinction matters, e.g. for which warnings are enabled. Update documentation to reflect the current state of the world.
RELNOTES:
Update "-I" to "-isystem" in documentation to reflect current behavior.
--
PiperOrigin-RevId: 142290840
MOS_MIGRATED_REVID=142290840
|
|
|
|
|
|
|
|
|
|
|
|
| |
with non-k8 cpus.
Fixes https://github.com/bazelbuild/bazel/issues/2258.
--
Change-Id: I920a558f15374d8f5f643c5ef67945247b6c692f
Reviewed-on: https://cr.bazel.build/8011
PiperOrigin-RevId: 142287815
MOS_MIGRATED_REVID=142287815
|
|
|
|
|
|
|
|
| |
Fixes #2231.
--
PiperOrigin-RevId: 142266332
MOS_MIGRATED_REVID=142266332
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If an Aspect registered an action that an extra-action is
shadowing, its name is used when creating the extra-action's ID and
name.
Since recently, an aspect can see other aspects applied to the same
target. This CL record the names of other aspects applied to the target
as well, disambiguating the action owners.
--
PiperOrigin-RevId: 142264153
MOS_MIGRATED_REVID=142264153
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Rolling forward, cl fixing underlying issue is uploaded, will land this one as soon as I get lgtm to the fix from emscripten crosstool owners.
*** Original change description ***
Automated [] rollback of commit 2d87bf1937c81ef84358fd5f6a372875f6c6fabf.
*** Reason for rollback ***
We have to roll back unknown commit, on which this one depends. Will resubmit after I fix the underlying issue.
*** Original change description ***
Support versioned shared library targets for cc_binary linkshared=1
This change allows versioned shared libraries (e.g. "libfoo.so.1.2") to be
built and linked.
--
PiperOrigin-RevId: 142263653
MOS_MIGRATED_REVID=142263653
|
|
|
|
|
|
|
|
|
|
| |
This allows Bazel to talk to multiple instances of the server, if these exist, enabling server-side parallelism (due to using separate gRPC channels).
TESTED: internally and local server
--
PiperOrigin-RevId: 142262973
MOS_MIGRATED_REVID=142262973
|
|
|
|
|
|
|
|
|
|
|
| |
A number of the shorter commands were not displayed in a code block, making them trickier to copy and paste into a console.
Closes #2257.
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/2257
PiperOrigin-RevId: 142262893
MOS_MIGRATED_REVID=142262893
|
|
|
|
|
|
|
|
|
|
|
| |
Partial fix of #2256
To cherry-pick for #2246
--
Change-Id: Ib25cc1dd85fd4af59b36eb2ac215ebd31d4d9eaa
Reviewed-on: https://cr.bazel.build/7975
PiperOrigin-RevId: 142262764
MOS_MIGRATED_REVID=142262764
|
|
|
|
|
|
|
|
| |
This might be used to influence resource allocation for actions later.
--
PiperOrigin-RevId: 142262023
MOS_MIGRATED_REVID=142262023
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
symlinked/new build file, which has less changes of causing conflicts. Fixes #2226."
This reverts commit 2f31d60d1454cd324196a5159262c1ba32eabda8.
Re-open #2226.
--
Change-Id: I7f223df4bb239daf8c306955e92f817310e6cd4f
Reviewed-on: https://cr.bazel.build/7950
PiperOrigin-RevId: 142257579
MOS_MIGRATED_REVID=142257579
|
|
|
|
|
|
|
|
|
| |
More renaming and some reformatting to make StandaloneTestStrategy more
closely resemble the internal implementation of TestStrategy.
--
PiperOrigin-RevId: 142254302
MOS_MIGRATED_REVID=142254302
|
|
|
|
|
|
|
|
|
| |
This just changes the order of variable initialization, method names, and
similar. It should not result in any semantic changes.
--
PiperOrigin-RevId: 142251887
MOS_MIGRATED_REVID=142251887
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 142250621
MOS_MIGRATED_REVID=142250621
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
cc_binary if we are doing dynamic linking anyway. The additional option is
only for a smooth rollout and will go away once everything works as expected.
The benefit is in an incremental save-build-test-cycle. When editing a test (or
any of it's transitive headers), the linker input currently changes, meaning we
need to do the full link again before the test can run. However, in conjunction
with the option --interface_shared_objects, this actually isn't necessary. With
this new option, the test source gets compiled into a .so file and while that
file changes with each source change, the .ifso file often does not change.
Thus, the costly link linking to gether all the .so and .ifso files can be
retrieved from cache. Thus, this change should remove this linking step from
the critical path of many save-build-test-cycles.
--
PiperOrigin-RevId: 142244352
MOS_MIGRATED_REVID=142244352
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Create WindowsPipe which implements IPipe, and is
a Windows-native implementation of pipe handling.
It wraps the ::CreatePipe, ::WriteFile, and
::ReadFile API functions.
Start using WindowsPipe on MSYS.
Also move everything from file_test.cc into
file_posix_test.cc, because these test methods
heavily depend on POSIX and they test file_posix's
functionality anyway.
Also add tests for pipes: this will use the
platform-specific implementation of IPipe.
file_test.cc is now platform-independent, and we
can test it with --cpu=x64_windows_msvc (and it
passes!).
See https://github.com/bazelbuild/bazel/issues/2107
Might also fix:
https://github.com/bazelbuild/bazel/issues/2182
https://github.com/bazelbuild/bazel/issues/2248
--
PiperOrigin-RevId: 142240377
MOS_MIGRATED_REVID=142240377
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
We have to roll back unknown commit, on which this one depends. Will resubmit after I fix the underlying issue.
*** Original change description ***
Support versioned shared library targets for cc_binary linkshared=1
This change allows versioned shared libraries (e.g. "libfoo.so.1.2") to be
built and linked.
--
PiperOrigin-RevId: 142240145
MOS_MIGRATED_REVID=142240145
|
|
|
|
|
|
|
|
| |
size while halving the number of syscalls required to get an MD5 of a file. This shaves a few hundred milliseconds off of startup time.
--
PiperOrigin-RevId: 142235555
MOS_MIGRATED_REVID=142235555
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Prevents warnings like the following under fastbuild/dbg:
In file included from /usr/lib/gcc/x86_64-pc-linux-gnu/5.4.0/include/g++-v5/x86_64-pc-linux-gnu/bits/os_defines.h:39:0,
from /usr/lib/gcc/x86_64-pc-linux-gnu/5.4.0/include/g++-v5/x86_64-pc-linux-gnu/bits/c++config.h:482,
from /usr/lib/gcc/x86_64-pc-linux-gnu/5.4.0/include/g++-v5/string:38,
from third_party/protobuf/3.0.0/src/google/protobuf/empty.pb.h:7,
from third_party/protobuf/3.0.0/src/google/protobuf/empty.pb.cc:5:
/usr/include/features.h:331:4: warning: #warning _FORTIFY_SOURCE requires compiling with optimization (-O) [-Wcpp]
# warning _FORTIFY_SOURCE requires compiling with optimization (-O)
--
Change-Id: I364bb2962ef930c9079ebddcc5855a0b4ee5c138
Reviewed-on: https://cr.bazel.build/7050
PiperOrigin-RevId: 142229574
MOS_MIGRATED_REVID=142229574
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(i) Use a CountDownLatch in ParallelQueryUtils#executeQueryTasksAndWaitInterruptibly to avoid busy-looping while waiting for query subtask completion (this busy-looping unnecessarily ties up a thread). But we still retain the fail-fast semantics we want (I renamed the method to emphasize this).
(ii) Also have a special-case in ParallelQueryUtils#executeQueryTasksAndWaitInterruptibly for evaluating one query subtask so we don't wastefully use another thread.
(iii) Also add ThreadSafety annotations to ParallelQueryUtils.
----
(i) and (ii) combine to address the following theoretical issue. Suppose we're evaluating a query expression of the form "(e1 - e2) + (e3 - e4)". The old code would (with the worst-case FJP thread scheduling) have the following threads at the _same_ time:
Main QueryCommand thread - executeQueryTasksAndWaitInterruptibly(queryTasks = [(e1 - e2), (e3 - e4)]
FJP thread - executeQueryTasksAndWaitInterruptibly(queryTasks = [e2])
FJP thread - eval(e2)
FJP thread - executeQueryTasksAndWaitInterruptibly(queryTasks = [e4])
FJP thread - eval(e4)
So of those 5 concurrent threads, 3 would be doing busy-loop waiting. For more pathological query expressions, we could end up tying up lots of threads doing wasteful busy-loops.
--
PiperOrigin-RevId: 142215680
MOS_MIGRATED_REVID=142215680
|
|
|
|
|
|
|
|
| |
for android resource processing.
--
PiperOrigin-RevId: 142215076
MOS_MIGRATED_REVID=142215076
|
|
|
|
|
|
|
|
| |
classpath, such as if needed to support generated sources.
--
PiperOrigin-RevId: 142214383
MOS_MIGRATED_REVID=142214383
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 142194378
MOS_MIGRATED_REVID=142194378
|