| Commit message (Collapse) | Author | Age |
|
|
|
|
| |
--
MOS_MIGRATED_REVID=126797730
|
|
|
|
|
|
|
|
| |
- Use CREATE_NO_WINDOW instead of DETACHED_PROCESS (apparently, that's what we need)
- Remove CREATE_BREAKAWAY_FROM_JOB. We now put the Bazel server into its own job that doesn't allow breakaway processes, so it's superfluous.
--
MOS_MIGRATED_REVID=126791316
|
|
|
|
|
|
|
|
|
|
|
| |
This is apparently required by some versions MSVCRT.DLL including the one used in the CL.EXE we happen to be using for testing.
This was learned by reading the source code of OpenJDK.
Fixes #1480.
--
MOS_MIGRATED_REVID=126786461
|
|
|
|
|
|
|
|
|
|
| |
This fixes #1461, which leads to bad sha1 values for some maven jars.
Closes #1473.
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/1473
MOS_MIGRATED_REVID=126785326
|
|
|
|
|
|
|
|
|
|
| |
This is in preparation for getting rid of some of the TestConstants, makes it
easier to open-source more tests, and also allows us to run tests against
subsets of the rule classes. That is in preparation for modularizing the
rule class provider.
--
MOS_MIGRATED_REVID=126782163
|
|
|
|
|
|
|
|
| |
- Use the abrupt exit protocol to return the correct exit code when the server dies unexpectedly in gRPC mode
- Report the command waiting time correctly even if the waiting is done within the server
--
MOS_MIGRATED_REVID=126780186
|
|
|
|
|
|
|
|
|
| |
Collapse the "evaluating" boolean into the "signaledDeps" int field, since signaledDeps is always 0 if evaluating is false, so we can use the sentinel value -1 to indicate that evaluation has not yet started. This leads to a slightly less tolerant node entry: it must "start evaluating" before you can do things like set its value. Places that wasn't being done have been fixed, at least as far as we have test coverage for.
Also, factor the "dirty" parts of BuildingState out into a subclass. It would probably be cleaner to use composition here, but I don't want to pay the price of another object.
--
MOS_MIGRATED_REVID=126729331
|
|
|
|
|
|
|
|
|
|
| |
Both source and generated hdrs are included in the output group.
Might be cleaner to only include generated headers -- perhaps by
adding a new field to CppCompilationContext. This solution seems
lighter-weight, however.
--
MOS_MIGRATED_REVID=126725901
|
|
|
|
| |
MOS_MIGRATED_REVID=126723341
|
|
|
|
|
|
|
| |
The biggest savings here is that we were not eagerly discarding the InMemoryNodeEntry#directDeps field after an entry was marked dirty, even though we would never read its value again. But rather than just fix that, by getting rid of the field in BuildingState, we can potentially save memory with smaller BuildingState objects as well.
--
MOS_MIGRATED_REVID=126709632
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=126706609
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a rollback of a rollback, with the change that gnu++11 is used instead of
c++11.
A [] with this change was run, and the resulting handful of compile errors
were addressed.
Modified: blaze objc target handling, osx CROSSTOOL and mock osx CROSSTOOL.
RELNOTES: When building ObjectiveC++, pass the flag -std=gnu++11.
--
MOS_MIGRATED_REVID=126700947
|
|
|
|
|
|
|
| |
As mentioned in https://groups.google.com/d/msgid/bazel-discuss/cebcf019-fcb4-4d7b-87be-1a3922b15e77%40googlegroups.com.
--
MOS_MIGRATED_REVID=126697864
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In the end, foo.9.png should result in an R.java
field R.drawable.foo (not R.drawable.foo_9).
Also, given foo.9.png and foo.png, aapt will give
an error:
res/drawable/foo.png:0: error: Resource entry foo is already defined.
res/drawable/foo.9.png:0: Originally defined here.
So it seems like we should generate a merge
conflict warning as well. Adjust FQN accordingly.
--
MOS_MIGRATED_REVID=126693820
|
|
|
|
|
|
|
| |
#1433
--
MOS_MIGRATED_REVID=126693120
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=126691559
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=126687108
|
|
|
|
|
|
|
|
|
| |
The cleanup is much less orderly than on Unix: we simply rely on Windows to terminate all child processes by putting the Bazel binary in a job.
Fixes #1134.
--
MOS_MIGRATED_REVID=126686643
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=126685659
|
|
|
|
|
|
|
|
|
|
|
|
| |
Don't encode paths as UTF-8 to md5sum them (the map keys are Strings derived
from Paths, for which Fingerprint.addPath() takes the same shortcut).
Remove defensive copy from the constructor (which did not need to be public).
Remove redundant call to Fingerprint.reset().
--
MOS_MIGRATED_REVID=126682477
|
|
|
|
|
|
|
|
|
| |
So people don't redistribute the binaries without the sources.
--
Change-Id: Ia3f91285d40669f8aa367633bb54214e9fdf1454
Reviewed-on: https://bazel-review.googlesource.com/#/c/3954
MOS_MIGRATED_REVID=126681605
|
|
|
|
|
|
| |
This makes the regeneration instruction in much simpler (since now they do publish 64-bit Linux binaries), and more importantly, fixes a race condition between a client request and the gRPC server timeout thread.
Change-Id: I9c8b628530fa0192804f8e67b285963ac26110c4
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The stopUpdateThread() method tries to stop the update thread
by calling the interrupt() and join() methods on that thread.
When getting interrupted while waiting for the thread to join,
do not ignore the exception, instead try again to make sure
we don't leave that method before the other thread is actually
stopped.
While there, also clean up the synchronized blocks for the thread
handling: all blocks that handle multiple global variables like
buildComplete, updateThread, etc, are synchronized while the actual
thread-manipulating operations are outside those blocks.
--
MOS_MIGRATED_REVID=126679343
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=126673732
|
|
|
|
|
|
|
|
|
| |
This is in preparation for splitting up the rules into per-language modules.
We'll also add test coverage to make sure each module is individually useful,
so that it's possible to build a Bazel binary with a reduced set of rules.
--
MOS_MIGRATED_REVID=126672702
|
|
|
|
|
|
|
|
|
|
| |
This java test is fixable after Bazel no longer append .exe as suffix
to .so cc_binary target on Windows.
--
Change-Id: I3a377839f00cf1e372f1ecb25692e86807e1ad43
Reviewed-on: https://bazel-review.googlesource.com/#/c/3964
MOS_MIGRATED_REVID=126637503
|
|
|
|
|
|
|
|
|
| |
The test was failing because IdlClass can't handle file path with back-slash
--
Change-Id: Ica72da756fd4bd9b4f8d907ff795549a59edc8be
Reviewed-on: https://bazel-review.googlesource.com/#/c/3966
MOS_MIGRATED_REVID=126636692
|
|
|
|
|
|
|
| |
--
Change-Id: Ic474eff981328b0a467606a01f88d72c26dfff74
Reviewed-on: https://bazel-review.googlesource.com/#/c/3965
MOS_MIGRATED_REVID=126636071
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=126633568
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=126631881
|
|
|
|
|
|
|
|
| |
We have some modules that assume 1:1 correspondence between servers and
workspaces, which I'd like to fix.
--
MOS_MIGRATED_REVID=126628292
|
|
|
|
|
|
|
|
|
| |
Subprocesses now get killed if the Bazel server itself is killed and so do their subprocesses.
Also implemented Subprocess#close() so that we get a little more control over when the native structures are cleaned up.
--
MOS_MIGRATED_REVID=126628000
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=126620866
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
types.
Fixes #921
Certain parameters, such as the `executable` and `command` parameters of
ctx.action, allow multiple types. However, the allowed types are not enumerated
in the SkylarkSignature annotation, causing the generated Skylark Library
document to not display any type information for those params.
This change adds a new field, `allowedTypes`, to `SkylarkSignature` that is a
list of `ParamType` objects. If the param can accept multiple types, then
`type` is set to `Object.class`, and `allowedTypes` is set to the list of types
that can be accepted.
--
MOS_MIGRATED_REVID=126617047
|
|
|
|
|
|
|
|
|
| |
An instance of the builder is passed to all modules, which can each add / set
things on the builder. This reduces the BlazeModule API surface, while also
being more flexible for future changes.
--
MOS_MIGRATED_REVID=126613981
|
|
|
|
|
|
|
|
|
|
| |
The solution is setting RUNFILES_MANIFEST_ONLY=1 in template file
if only runfile manifest feature is enabled.
--
Change-Id: I6c96cc1212818bd57adcdfb59fa0de66d2d38037
Reviewed-on: https://bazel-review.googlesource.com/#/c/3960
MOS_MIGRATED_REVID=126577520
|
|
|
|
|
|
| |
This review was merged at the wrong patchset leaving some change behind.
Change-Id: I018accd516c73cc63cd9368df2daa9c389c93bc3
|
|
|
|
|
|
|
|
|
|
| |
Those source jars comes from
javac.jar = https://github.com/google/error-prone-javac/archive/1.9.0-dev-r2644-2.zip
javac7.jar = https://github.com/google/error-prone-javac/archive/1.9.0-dev-r2973-2.zip
As a consequence also updated the version in third_party readme.
Change-Id: I4c9d749d2b4acb1254cd65efbabf4e6515924414
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Broke some targets
--
MOS_MIGRATED_REVID=126574275
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=126572660
|
|
|
|
|
|
|
|
|
| |
Also remove some bashism to fix #1456.
--
Change-Id: I374f1290a3eb9e9e5bcc48e19a1c0ab1c5bdaa99
Reviewed-on: https://bazel-review.googlesource.com/#/c/3952/
MOS_MIGRATED_REVID=126572632
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=126571069
|
|
|
|
|
|
|
| |
We should really do something about the mess that is loading our JNI libraries -- io.bazel.EnableJNI is mentioned eight times in the code in various diverse contexts. This change is not the right place to do it, though.
--
MOS_MIGRATED_REVID=126570481
|
|
|
|
|
|
|
|
|
| |
style path
--
Change-Id: I219bce744a73333ff3a79bedc78ee78c415629e8
Reviewed-on: https://bazel-review.googlesource.com/#/c/3961
MOS_MIGRATED_REVID=126569740
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=126566280
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Breaks CI, see, e.g., http://ci.bazel.io/job/bazel-tests/BAZEL_VERSION=HEAD,PLATFORM_NAME=ubuntu_15.10-x86_64/92/console
*** Original change description ***
C++ reimplementation of singlejar tool: first checkin.
--
MOS_MIGRATED_REVID=126565472
|
|
|
|
|
|
|
|
|
| |
what CreateProcess() does.
Test cases don't need to be changed because this issue was caught by CreateProcess() instead.
--
MOS_MIGRATED_REVID=126560893
|
|
|
|
|
|
|
| |
It seems like the Bazel server dies (or isn't reused) between the first and the second "bazel build" in test_input_digests.
--
MOS_MIGRATED_REVID=126511647
|
|
|
|
|
|
|
| |
last build's deps. This is only an issue with cycles, since there we try to maintain the invariant that a parent is not done before its children by removing its deps on its children before we construct its cycle value.
--
MOS_MIGRATED_REVID=126494009
|
|
|
|
|
|
|
| |
was unnecessary.
--
MOS_MIGRATED_REVID=126457804
|