| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
| |
SkyFunction if it throws an exception but still has missing deps. Instead, pretend it didn't throw, and restart it when its known deps are all done, presumably to throw the same exception. This removes a basic source of non-determinism.
--
MOS_MIGRATED_REVID=127129202
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=127126897
|
|
|
|
|
|
|
|
| |
Properly handle unary tags in AttrXmlResourceValue
Handle CData for string content.
--
MOS_MIGRATED_REVID=127118005
|
|
|
|
| |
MOS_MIGRATED_REVID=127108931
|
|
|
|
|
|
|
| |
This minimizes API divergence and allows us to make use of performance enhancements in guava, such as https://github.com/google/guava/issues/1197.
--
MOS_MIGRATED_REVID=127108107
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=127099896
|
|
|
|
|
|
|
|
|
| |
This should let the users wrap around ci.sh if they want to use the instructions from
the comments (those related to Gerrit and Travis-CI), as opposed to having to edit the
script.
--
MOS_MIGRATED_REVID=127093626
|
|
|
|
| |
MOS_MIGRATED_REVID=127091947
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=127086608
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=127084529
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Now, we can use:
bazel query 'tests(//src/test/java/...) - attr(tags, no_windows, tests(//src/test/java/...))'
to find all the tests passing on Windows.
--
Change-Id: I5c7f05fbf9718bc335e19fd17916a14c286bedbf
Reviewed-on: https://bazel-review.googlesource.com/#/c/3970
MOS_MIGRATED_REVID=127078158
|
|
|
|
|
|
|
| |
--
Change-Id: I12ae7bdf6b7fe5340843bc1750313556970f4c90
Reviewed-on: https://bazel-review.googlesource.com/c/4020
MOS_MIGRATED_REVID=127076309
|
|
|
|
|
|
|
|
|
|
| |
...and only use the hard-coded "/tmp" as default for the default.
Note that is unchanged that blaze.rpcserver.tmpdir still overrides.
--
Change-Id: I2ad6b9904b7cde3917968090e85cf2d6c8ad88ab
Reviewed-on: https://bazel-review.googlesource.com/#/c/3962
MOS_MIGRATED_REVID=127076270
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Change the bootstrapping process so that setting the BAZEL_WRKDIR
environment variable will tell the bootstrap process to mostly write
to that directory---apart from adding the symlinks next to the WORKSPACE
file. So setting this variable will avoid the usual writes to random
places in the file system (like /tmp and the user's home directory).
--
Change-Id: I9d1af747e75cc2a7bb1af08308acc9dfd927e920
Reviewed-on: https://bazel-review.googlesource.com/#/c/3963
MOS_MIGRATED_REVID=127075535
|
|
|
|
|
|
|
| |
--
Change-Id: I4c9d749d2b4acb1254cd65efbabf4e6515924414
Reviewed-on: https://bazel-review.googlesource.com/#/c/3921/
MOS_MIGRATED_REVID=127074886
|
|
|
|
|
|
|
|
| |
These are needed to add `blaze run` support to skylark_ios_application
so that they can be passed in as parameters to the ios_runner script.
--
MOS_MIGRATED_REVID=126955658
|
|
|
|
|
|
|
| |
Mergee manifests are pre-processed and written to a temp directory, based on their original path, before the final merge. Previously only the filename was used, resulting in each mergee overwriting the previous, all of which were <temp_dir>/AndroidManifest.xml. Using the full path of each manifest ensures this overwriting cannot occur.
--
MOS_MIGRATED_REVID=126942789
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=126939078
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Hook up the RClassGeneratorAction to blaze code.
This is currently only used for android_binary
targets to build the final R classes of the
binary + all of its libraries.
Behind a flag and off by default (flip on later).
--
MOS_MIGRATED_REVID=126935165
|
|
|
|
|
|
|
| |
alternate graph implementations to optimize how they construct node entries.
--
MOS_MIGRATED_REVID=126932020
|
|
|
|
|
|
|
| |
* Debug and fastbuild compilation modes now pass -enable-testing flag enabling internal symbol imports in test code.
--
MOS_MIGRATED_REVID=126925229
|
|
|
|
|
|
|
| |
interfaces, in preparation for further changes.
--
MOS_MIGRATED_REVID=126924789
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=126923745
|
|
|
|
|
|
|
| |
* This seems to fix an issue with Clang loading the same header twice when it's discovering module maps implicitly. Also makes the command line cleaner.
--
MOS_MIGRATED_REVID=126922449
|
|
|
|
|
|
|
|
|
|
|
| |
1. Return EOF for streams representing Windows process pipes.
2. Fix the timing of process.close()
3. Un-synchronized reading of stderr and stdout.
--
Change-Id: Iec98f45db9984be2c2b066962801cbd3ca60da3f
Reviewed-on: https://bazel-review.googlesource.com/#/c/4000/
MOS_MIGRATED_REVID=126910063
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add an event to the event bus that is guaranteed to come after the
completion of the command. Listeners can use this event to clean up
any resources that still need to be cleaned up. As first customer, add
the ExperimentalEventHandler so that it is guaranteed not to leak the
update thread.
--
Change-Id: Ia20bae8a00541aa1338e49f74a7320ac098ab71d
Reviewed-on: https://bazel-review.googlesource.com/#/c/4011
MOS_MIGRATED_REVID=126909844
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When the progress bar has to be updated, but we cannot do so immediately, e.g.,
due to rate limiting, we start a thread to do this eventually (the "update
thread"). That thread gets stopped if either we realize during an update of the
progress bar that it is no longer needed, or if we get informed about the
completion of the build. Now, since the update thread does updates of the
progress bar (that is its whole purpose) it can get the duty to stop itself.
To avoid the deadlock when the thread there blockingly waits for itself
to terminate, just skip that termination and let the update thread run
till the end of the build.
--
Change-Id: Iba08806f5e416f1fa1825969eceaf6cf54c24e6c
Reviewed-on: https://bazel-review.googlesource.com/#/c/4010
MOS_MIGRATED_REVID=126906395
|
|
|
|
|
|
|
|
|
|
|
| |
passes between the Ping() and Run() calls and make Ping() and Cancel() calls restart the server timeout interval.
This "fixes" a race condition where the client would call Ping(), the server would time out and then the Run() call would fail. Of course, this is not an principled fix because in theory, the timeout can still happen between the two calls, but now there are only simple file system operations and a tiny bit of CPU use between the two so it should be vanishingly unlikely. We use ->Ping() to verify server liveness after we start it up, so in theory, the timeout could strike between those two calls, too...
TESTED=By running "bazel --max_timeout_secs=2 info install_base" 100 times in a test and running the test 200 times. This procedure triggered the bug pretty reliably.
--
MOS_MIGRATED_REVID=126902519
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=126850134
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The --splits flag is now --split, since I remembered about how allowMultiple exists.
More importantly, split APKs are now correctly moved to filenames which are fairly
trivially constructed from the input split flags, allowing Bazel to just do a simple
one-character replace on the split flags and know what files the resource processing
action is going to output.
One more step in the quest for world domination, or rather, split APKs for resources.
Next: Actually supporting this in android_binary.
--
MOS_MIGRATED_REVID=126838431
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=126837234
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add the rclass_generator.sh, and fill in the
boiler-plate for mock tools, etc. Mostly cargo-
culting references to resources_processor.sh.
Rename earlier pieces to use RClassGenerator
prefix instead of AndroidResourceCompilation.
--
MOS_MIGRATED_REVID=126831848
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=126813515
|
|
|
|
|
|
|
|
|
| |
* Adds output file map support, to handle compiler outputs with multiple inputs such as Whole Module Optimization compilation.
* Properly archives object file outputs into a static library.
--
MOS_MIGRATED_REVID=126811405
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=126803908
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Apparently we now try to open output files for the process twice: once when we are constructing the output streams, and the second time when we tell the process to redirect its outputs. This causes the outputs to be empty on Windows
*** Original change description ***
Do redirection of stdout / stderr in Java instead of reimplementing it in every process wrapper again.
--
MOS_MIGRATED_REVID=126801016
|
|
|
|
|
|
|
| |
This change is similar to a previous change that introduced WorkspaceBuilder.
--
MOS_MIGRATED_REVID=126799657
|
|
|
|
|
| |
--
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
|