aboutsummaryrefslogtreecommitdiffhomepage
Commit message (Collapse)AuthorAge
* PiperOrigin-RevId: 184726412Gravatar Googler2018-02-06
|
* Don't generate the blaze generated extension registry for Android tests that ↵Gravatar Googler2018-02-06
| | | | | | | | | | define a binary_under_test. They are filtered out for deployment anyways so it's unnecessary work and it confuses the one version detector. RELNOTES: n/a PiperOrigin-RevId: 184725205
* Always do filtering in execution (even after doing it in analysis)Gravatar Googler2018-02-06
| | | | | | | | | | | | Filtering only in analysis was neglecting the possibility of resources being in filesets, the contents of which are not available in analysis. As such, we must *always* filter in execution, even though it's usually just going to be a no-op. Also, add some documentation of same. RELNOTES: none PiperOrigin-RevId: 184722564
* @AutoCodec support for superclasses having generic parameters.Gravatar shahan2018-02-06
| | | | PiperOrigin-RevId: 184720361
* Add Supplier support to AutoCodec.Gravatar cpeyser2018-02-06
| | | | PiperOrigin-RevId: 184710375
* Update ToolchainResolutionFunction to consider multiple availableGravatar John Cater2018-02-06
| | | | | | | | | execution platforms. Part of #4442. Change-Id: I6678d57f4aaadcb19032bf58820606242ba66a25 PiperOrigin-RevId: 184707708
* Add a new tool to check the deps of aar_import. This is the first cl of aGravatar cnsun2018-02-06
| | | | | | | series. The following CLs will integrate this into bazel. RELNOTES:n/a. PiperOrigin-RevId: 184706507
* Throw NoCodecException on ByteString getCodec specializationGravatar michajlo2018-02-06
| | | | | | Looks like this got missed. PiperOrigin-RevId: 184701334
* Fix CrosstoolConfigurationLoader to not assume the presense of a BUILDGravatar John Cater2018-02-06
| | | | | | | file. Change-Id: I5b66b91f016e12e546600f585546fc56d9511303 PiperOrigin-RevId: 184698749
* Delete the now-useless interfaces ServerCommand and CommandExecutor.Gravatar lberki2018-02-06
| | | | | | | | | We apparently don't have any other implementations of these interfaces than BlazeCommandDispatcher, so let's not have them at all; we can always put back an interface with the exec() method if need be. RELNOTES: None. PiperOrigin-RevId: 184698573
* Makes @AutoCodec only use Instantiator parameter type information and ignoreGravatar shahan2018-02-06
| | | | | | field type information. PiperOrigin-RevId: 184695891
* runfiles test: extract mock Java code to a fileGravatar Laszlo Csomor2018-02-06
| | | | | | | | | | | | | Move the mock java file in //src/test/py/bazel:runfiles_test to an actual file in the source tree. This change makes the test more readable, and the file more easily discoverable. See https://github.com/bazelbuild/bazel/issues/4460 Change-Id: I94b033f63b218554b0e0e11814fde4c13bf7cca0 PiperOrigin-RevId: 184692391
* Move BlazeRuntime/BlazeCommandDispatcher shutdown to where they are created.Gravatar lberki2018-02-06
| | | | | RELNOTES: None. PiperOrigin-RevId: 184692000
* Return JavaPluginInfoProvider via JavaInfo in android_library.Gravatar elenairina2018-02-06
| | | | PiperOrigin-RevId: 184689620
* Converts wrapped_clang from a bash script to a C++ source file which is ↵Gravatar kaipi2018-02-06
| | | | | | | | | | | | compiled as part of bazel's repository bootstrap. This should make crosstool's clang invocations faster. An added benefit of this is that wrapped_clang.cc supports the "DSYM_HINT" flags specified through the CROSSTOOL, so with this change, apple_binary gets support for the --apple_generate_dsym flag. The dSYM generation issue has been flagged multiple times: https://github.com/bazelbuild/bazel/issues/4312 https://github.com/bazelbuild/bazel/issues/3940 https://github.com/bazelbuild/bazel/issues/3372 RELNOTES: apple_binary can now generate dSYM outputs with the --apple_generate_dsym=true flag. PiperOrigin-RevId: 184688215
* Add a marshaller in AutoCodec for Iterable. This marshaller performs a ↵Gravatar cpeyser2018-02-06
| | | | | | runtime check on the type of the iterable, performing custom serialization for a NestedSet. PiperOrigin-RevId: 184686288
* Remove log_levels attribute from android_instrumentation_test.Gravatar jingwen2018-02-06
| | | | | | | | | This can be encapsulated in a device script fixture as an environment variable. https://developer.android.com/studio/command-line/logcat.html#filteringOutput RELNOTES: None. PiperOrigin-RevId: 184683289
* Remove ShutdownBlazeServerException in favor of indicating that the server ↵Gravatar lberki2018-02-06
| | | | | | | should be shut down in BlazeCommandResult. RELNOTES: None. PiperOrigin-RevId: 184678994
* Rename the host platform information in the configuration.Gravatar John Cater2018-02-06
| | | | | | | Part of #4442. Change-Id: I21baffe59431ccd3d76754596ec2a605dbbe4354 PiperOrigin-RevId: 184678470
* C++: Remove last instatiation of CppModel outside CcLibraryHelper.Gravatar plf2018-02-06
| | | | | | | This is the second try for this CL. The first one caused Blaze to crash when building Exoblaze as shown in b/72936965. In this CL I fix the condition of when to generate non-PIC compilation actions for WrapCcHelper. RELNOTES:none PiperOrigin-RevId: 184671661
* Detect deprecated operations on dict() variables in SkylintGravatar cparsons2018-02-06
| | | | | RELNOTES: None. PiperOrigin-RevId: 184667932
* Automated rollback of commit 4260c30a03a9b83d48a5e8690aca19cd80be4c38.Gravatar ulfjack2018-02-06
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | *** Reason for rollback *** Try again with fixes. *** Original change description *** Automated rollback of commit 10b0d8aa6b73a024cc007c5e075cb329add878ef. *** Reason for rollback *** Breaks Google-internal targets, sadly. *** Original change description *** Ban middlemen from runfiles artifacts. Previous changes have removed all middlemen from runfiles artifacts. This CL locks it down and removes various now-redundant *WithoutMiddlemen() methods from Runfiles. I put a check for middlemen in ConflictChecker.put, which should be a chokepoint for runfiles arti... *** PiperOrigin-RevId: 184661375
* runfiles,py: add test to run a data-dependencyGravatar Laszlo Csomor2018-02-06
| | | | | | | | | | | | Update the runfiles test's mock Python binary to run another mock Python binary and assert that the outer binary propagates the runfiles information to the inner one. See https://github.com/bazelbuild/bazel/issues/4460 Change-Id: I3bba799a376642196777f7bc988837084a53bc93 PiperOrigin-RevId: 184650962
* Add debugging helper to Environment.Extension to say why something's unequalGravatar brandjon2018-02-06
| | | | | RELNOTES: None PiperOrigin-RevId: 184649483
* Ignore VSCode filesGravatar Loo Rong Jie2018-02-06
| | | | | | Closes #4488. PiperOrigin-RevId: 184648112
* Basic tooling to desugar select core librariesGravatar kmb2018-02-05
| | | | | | RELNOTES: None. PiperOrigin-RevId: 184619885
* Fix test compilation failure.Gravatar felly2018-02-05
| | | | PiperOrigin-RevId: 184587712
* Add NestedSet support in AutoCodec for type parameters which have an ↵Gravatar cpeyser2018-02-05
| | | | | | InjectingObjectCodec. PiperOrigin-RevId: 184566571
* PiperOrigin-RevId: 184564534Gravatar Googler2018-02-05
|
* Include module-info.class files in interface jarsGravatar cushon2018-02-05
| | | | | | | | | instead of removing them, since builds that use modules need them to be visible across compilation boundaries. Note that the module-infos don't contain any implementation that needs to be removed, so ijar just copies the entire file through. PiperOrigin-RevId: 184562080
* Fix Fileset incrementality bug when Fileset consumes a generated file. The ↵Gravatar felly2018-02-05
| | | | | | | | | | | | | | | | native skyframe implementation was actually quite incorrect in this case: It was adding a skyframe dependency on a FileValue for the output file. Without a transitive dependency on the source files and actions that determine the output file's state, this could never work (and explains why the incremental build would fail). Instead, we now depend on the Artifact corresponding to the output file instead. This change updates the business logic RecursiveFilesystemTraversalFunction. This approach keeps the business logic of Fileset filesystem traversal centralized in RFTF. To avoid making weird recursive Skyframe nodes in the output tree, we inline Skyframe dependencies and do direct filesystem operations over the output tree. There are now three states we can be in when looking up a file: 1. Source file: As before, make a skyframe dep on the corresponding file 2. Top-level file of an output tree: Make a dep on the corresponding Artifact 3. Recursive file under an output directory: Do direct filesystem operations. It doesn't make sense to make Skyframe nodes corresponding to these files. In the future, I think we should consider failing fast on this case. RELNOTES: None PiperOrigin-RevId: 184556044
* Tag a few aspect classes with @AutoCodec and make CcProtoAspect abstract, ↵Gravatar janakr2018-02-05
| | | | | | since it's never instantiated on its own. PiperOrigin-RevId: 184554483
* Refactor ArtifactSkyKey to get rid of an unnecessary wrapper class: actually ↵Gravatar janakr2018-02-05
| | | | | | | | essentially promote OwnedArtifact to ArtifactSkyKey and rename it to ArtifactSkyKey. The king is dead... Also add some other execution-phase codecs. PiperOrigin-RevId: 184552706
* Simplify RuleClassProviders by making most RuleSets have their own class.Gravatar lpino2018-02-05
| | | | PiperOrigin-RevId: 184540561
* Fix AndroidDevice to never put the unified launcher's runfiles middleman in ↵Gravatar Benjamin Peterson2018-02-05
| | | | | | | | | | | the runfiles tree. As I understand it, this is only a theoretical issue today because $unified_launcher is generally a flat file. (Flat files never have runfiles middlemen.) However, it's good to be future proof. Change-Id: If77edfa9dd7475ab93b19c62b08f8d86a77acbe6 PiperOrigin-RevId: 184540188
* Add type assertion that TreeFileArtifact's parentTreeArtifact member is aGravatar cpeyser2018-02-05
| | | | | | SpecialArtifact. PiperOrigin-RevId: 184539696
* Fix manifest_merger documentation link.Gravatar ajmichael2018-02-05
| | | | | RELNOTES: None PiperOrigin-RevId: 184538771
* Pass ctime to the TimestampGranularityMonitorGravatar ulfjack2018-02-05
| | | | | | | | We're now using ctime to detect file changes, so the timestamp granularity monitor should as well. Unfortunately, we currently get nanosecond ctime from Linux, but then only return millis from FileStatus, so this doesn't change the accuracy of the monitor at all. PiperOrigin-RevId: 184536539
* Update DarwinSandboxedSpawnRunner to correctly set the sandbox configuration ↵Gravatar ruperts2018-02-05
| | | | | | | rule for the execution statistics path. RELNOTES: None. PiperOrigin-RevId: 184534589
* Optimize GetRandomStrGravatar Loo Rong Jie2018-02-05
| | | | | | Closes #4489. PiperOrigin-RevId: 184532916
* Support legacy multidex.Gravatar ajmichael2018-02-05
| | | | | | | Fix the create_main_dex_list stub script to find the dx jar binary correctly. RELNOTES: None PiperOrigin-RevId: 184532530
* Add a "direct" mode to "blaze run" that makes the process being run a directGravatar lberki2018-02-05
| | | | | | | | | | | | | | child of the process where the Blaze client itself was run. Limitations: - Untested on Windows; it should work because ExecuteProgram() is implemented there, too, but since Windows doesn't support exec(), there is at least one process in between Progress towards #2815. RELNOTES[NEW]: The new "--direct_run" flag on "blaze run" lets one run interactive binaries. PiperOrigin-RevId: 184528845
* Automated rollback of commit 17830c25a816d67ba79e783acaa6a085b516bd43.Gravatar jmmv2018-02-05
| | | | | | | | | | | | | | | *** Reason for rollback *** Causes Blaze to crash when building Exoblaze as shown in b/72936965. Confirmed as root cause by rolling back this CL, building a Blaze from HEAD, and successfully using it to build Exoblaze. *** Original change description *** C++: Remove last instatiation of CppModel outside CcLibraryHelper. RELNOTES:none PiperOrigin-RevId: 184528551
* remote: correct link to remote caching documentation.Gravatar buchgr2018-02-05
| | | | | RELNOTES: None PiperOrigin-RevId: 184518931
* sha256 python tool: stream instead of reading whole file beforehandGravatar Hadrien Chauvin2018-02-05
| | | | | | | | This is a rather small change to a Python tool used to produce a SHA256 hash. Currently, the whole file is loaded in memory before computing the hash, which causes problem when large files are processed. For instance, github.com/bazelbuild/rules_docker uses it to compute the hash of Docker images, which can be multiple GB in size. This PR avoids the tool to cause issues in a limited-memory environment. Closes #4243. PiperOrigin-RevId: 184518900
* python,runfiles: runfiles library in @bazel_toolsGravatar Laszlo Csomor2018-02-05
| | | | | | | | | | | | | Also update the Python stub script template to set $RUNFILES_MANIFEST_FILE or $RUNFILES_DIR so the runfiles library only needs to look for those. See https://github.com/bazelbuild/bazel/issues/4460 RELNOTES[NEW]: python,runfiles: You can now depend on `@bazel_tools//tools/runfiles:py-runfiles` to get a platform-independent runfiles library for Python. See DocString of https://github.com/bazelbuild/bazel/blob/master/src/tools/runfiles/runfiles.py for usage information. Change-Id: I4f68a11cb59f2782e5203e39fe60cc66b46023a2 PiperOrigin-RevId: 184515490
* C++: Remove last instatiation of CppModel outside CcLibraryHelper.Gravatar plf2018-02-05
| | | | | RELNOTES:none PiperOrigin-RevId: 184510731
* Expose structField callable methods of skylark objects to dir() and str() callsGravatar cparsons2018-02-05
| | | | | RELNOTES: None. PiperOrigin-RevId: 184498836
* Convert "-" to "" when generating module nameGravatar Googler2018-02-05
| | | | | RELNOTES: None. PiperOrigin-RevId: 184492828
* docs: document --workspace_status_commandGravatar laszlocsomor2018-02-05
| | | | | | | | | Add docs for the --workspace_status_command flag. Fixes https://github.com/bazelbuild/bazel/issues/4220 RELNOTES: none PiperOrigin-RevId: 184492241