aboutsummaryrefslogtreecommitdiffhomepage
path: root/src
Commit message (Collapse)AuthorAge
* --Gravatar Carmi Grushko2017-02-10
| | | | | PiperOrigin-RevId: 147105048 MOS_MIGRATED_REVID=147105048
* Remove unused dep from android_integration_test and clarify comment about ↵Gravatar Adam Michael2017-02-10
| | | | | | | | this mess that we have gotten ourselves into. -- PiperOrigin-RevId: 147097283 MOS_MIGRATED_REVID=147097283
* Emphasize that java_xxx_proto_library.strict_deps should not be used for new ↵Gravatar Carmi Grushko2017-02-10
| | | | | | | | code. -- PiperOrigin-RevId: 147096200 MOS_MIGRATED_REVID=147096200
* Use AliasProvider for DexArchiveAspect to "see through" alias targets until ↵Gravatar Googler2017-02-10
| | | | | | | | [] can be fixed. -- PiperOrigin-RevId: 147094979 MOS_MIGRATED_REVID=147094979
* Make aar_import fail fast if no android_sdk is set up.Gravatar Adam Michael2017-02-10
| | | | | | | | https://github.com/bazelbuild/bazel/issues/2500 -- PiperOrigin-RevId: 147089163 MOS_MIGRATED_REVID=147089163
* --Gravatar Carmi Grushko2017-02-10
| | | | | PiperOrigin-RevId: 147080281 MOS_MIGRATED_REVID=147080281
* Use //third_party/protobuf:protobuf_java instead of ↵Gravatar Carmi Grushko2017-02-09
| | | | | | | | | | | | //third_party/protobuf:protobuf to refer to the Java proto runtime. (second attempt) This is the name in the upstream protobuf repo. -- PiperOrigin-RevId: 147057949 MOS_MIGRATED_REVID=147057949
* Search for Test classes within the classpath used by the current ↵Gravatar Kush Chakraborty2017-02-09
| | | | | | | | classloader, instead of the system classpath. -- PiperOrigin-RevId: 147045814 MOS_MIGRATED_REVID=147045814
* Using os.pathsep in python stub template.txtGravatar Yun Peng2017-02-09
| | | | | | | | See https://github.com/bazelbuild/bazel/commit/7093b97ec3f332016822ed154e81bd86bc7ca645#commitcomment-20814099 -- PiperOrigin-RevId: 147043323 MOS_MIGRATED_REVID=147043323
* Generated files directory is passed to dependers as a user header search ↵Gravatar Cal Peyser2017-02-09
| | | | | | | | path. In the process, rename and replace the incorrectly named ObjcCommon.Builder#addUserHeaderSearchPaths -- PiperOrigin-RevId: 147038434 MOS_MIGRATED_REVID=147038434
* Add bootstrapping test to CI Gravatar Damien Martin-Guillerez2017-02-09
| | | | | | | | | | | Put it only as JDK-8, the generation of the distribution artifact is incorrect with JAVA_VERSION=1.8 -- Change-Id: I87a5f8ec4b12d3aa22a3360fcb9d488757e79461 Reviewed-on: https://cr.bazel.build/8575 PiperOrigin-RevId: 147037944 MOS_MIGRATED_REVID=147037944
* Test output directory presence for skylark repositories without a FileValue Gravatar Damien Martin-Guillerez2017-02-09
| | | | | | | | | | | | Using a FileValue depenendency was not needed and create over-invalidation of the repository. On a cold server, this duplicate the call to the repository function, including potential slow operation like downloads. -- Change-Id: Ie09fa45b2d77f8986f4a4e95d06e8133481aff50 Reviewed-on: https://cr.bazel.build/8138 PiperOrigin-RevId: 147032408 MOS_MIGRATED_REVID=147032408
* Java template windows performanceGravatar Yun Peng2017-02-09
| | | | | | | | | | Address issue #2426 Closes #2427. -- PiperOrigin-RevId: 147031246 MOS_MIGRATED_REVID=147031246
* Remove the first argument of TestStrategy.getArgs.Gravatar Ulf Adams2017-02-09
| | | | | | | | | All callers were performing identical steps before calling getArgs - move the functionality into getArgs instead. -- PiperOrigin-RevId: 147028753 MOS_MIGRATED_REVID=147028753
* Replace PackageProvider with TargetProvider where possibleGravatar Ulf Adams2017-02-09
| | | | | | | | | | I was trying to simplify GenQuery, and found this during an audit of the code; it's not sufficient to make any larger changes, but it may help eventuall. -- PiperOrigin-RevId: 147023626 MOS_MIGRATED_REVID=147023626
* Remove dead code - unused method in PackageManager interfaceGravatar Ulf Adams2017-02-09
| | | | | | -- PiperOrigin-RevId: 147018240 MOS_MIGRATED_REVID=147018240
* Fix int*list binary operator.Gravatar Laurent Le Brun2017-02-09
| | | | | | | | [2] * 3 should return [2, 2, 2] and not [2, 2, 2, 2]. -- PiperOrigin-RevId: 147017581 MOS_MIGRATED_REVID=147017581
* Bazel client, Windows: use more of AutoHandleGravatar Laszlo Csomor2017-02-09
| | | | | | -- PiperOrigin-RevId: 147008328 MOS_MIGRATED_REVID=147008328
* Add "CLEAN_UP" as a reason for retrieving a node.Gravatar Shreya Bhattarai2017-02-09
| | | | | | -- PiperOrigin-RevId: 146982656 MOS_MIGRATED_REVID=146982656
* Pass 'main_class' attribute value through in the IntelliJ aspect.Gravatar Googler2017-02-09
| | | | | | | | Then use it in the blaze plugin's main class run configuration producer. -- PiperOrigin-RevId: 146980092 MOS_MIGRATED_REVID=146980092
* make DexArchiveAspect propagate through alias targetsGravatar Googler2017-02-09
| | | | | | | | RELNOTES: n/a -- PiperOrigin-RevId: 146968274 MOS_MIGRATED_REVID=146968274
* experimental_objc_library excludes non-.h headers, as does objc_library.Gravatar Cal Peyser2017-02-09
| | | | | | -- PiperOrigin-RevId: 146958087 MOS_MIGRATED_REVID=146958087
* Use //third_party/protobuf:protobuf_java instead of ↵Gravatar Carmi Grushko2017-02-09
| | | | | | | | | | //third_party/protobuf:protobuf to refer to the Java proto runtime. This is the name in the upstream protobuf repo. -- PiperOrigin-RevId: 146949832 MOS_MIGRATED_REVID=146949832
* Fix spelling mistake.Gravatar Nathan Harmata2017-02-09
| | | | | | -- PiperOrigin-RevId: 146949259 MOS_MIGRATED_REVID=146949259
* Rollback of commit 602a98cbebeff2ba1c2d8605a9552b2c8f5622ae.Gravatar Googler2017-02-09
| | | | | | | | | | | | | | | | *** Reason for rollback *** Rolling forward with fixes for the incremental tool. *** Original change description *** Automated [] rollback of commit d11d510c571b10787856395709f9ad945ca70bb2. *** Reason for rollback *** -- PiperOrigin-RevId: 146940409 MOS_MIGRATED_REVID=146940409
* --Gravatar Carmi Grushko2017-02-09
| | | | | PiperOrigin-RevId: 146926312 MOS_MIGRATED_REVID=146926312
* Introduce a new SkyValue that merely contains the workspace name. The ↵Gravatar Nathan Harmata2017-02-09
| | | | | | | | | | | | workspace name is needed for package loading, and so splitting out this computation into a separate skyframe node that can be change-pruned gives us better incrementality; previously we'd need to reload all packages on a WORKSPACE file change. N.B. (i) This CL doesn't solve all the other performance issues with //external in Bazel/Blaze since it's still inefficiently used for resolving labels like @foo//bar:baz. (ii) This CL doesn't address the wasteful invalidation + change pruning of all the packages. -- PiperOrigin-RevId: 146925369 MOS_MIGRATED_REVID=146925369
* Bazel client, Windows: implement SetupStdStreamsGravatar Laszlo Csomor2017-02-09
| | | | | | | | See https://github.com/bazelbuild/bazel/issues/2107 -- PiperOrigin-RevId: 146921464 MOS_MIGRATED_REVID=146921464
* Rollback of commit 6521cb22788adc2a74f6c26221dbe302dc9ccc14.Gravatar Damien Martin-Guillerez2017-02-08
| | | | | | | | | | | | | | | | | | *** Reason for rollback *** Break JDK 7 build on ci.bazel.io Found out by downloading bazel 0.4.4 for JDK7 and `bazel test //src/test/shell/integration:stub_finds_runfiles_test --define JAVA_VERSION=1.7` This is due to JDK 7 using JavaBuilder that comes with version 0.1 of Bazel, which is not fixed for that issue. *** Original change description *** Don't add the class output dir to the classpath -- PiperOrigin-RevId: 146920718 MOS_MIGRATED_REVID=146920718
* Stop retrieving CcToolChainProvider statically from hard-coded attribute ↵Gravatar Rumou Duan2017-02-08
| | | | | | | | | | ":cc_toolchain" in RuleContext, instead take the provider from users and pass it around to where it is used. This gives J2ObjcAspect the ability to specify the C++ toolchain attribute under a different name to avoid attribute conflicts with attached rules that have already declared attribute ":cc_toolchain". -- PiperOrigin-RevId: 146920294 MOS_MIGRATED_REVID=146920294
* Make bazel test suites fail without a real test, by no longer adding an ↵Gravatar Kush Chakraborty2017-02-08
| | | | | | | | | | | | empty test in the TestSuiteBuilder. The current scenario can be bug-prone since changes to the TestSuiteBuilder code may bypass all tests, and in the absence of test failures, our tests will signal success. RELNOTES: Make it mandatory for Java test suites in bazel codebase, to contain at least one test. -- PiperOrigin-RevId: 146919833 MOS_MIGRATED_REVID=146919833
* Introduce a Skyframe function: ActionEnvironmentFunction Gravatar Damien Martin-Guillerez2017-02-08
| | | | | | | | | | | | | | | | | | ActionEnvironmentFunction returns the list of environment variable with the one overwritten by --action_env being replaced. This let other Skyframe function declares dependency to any value of the environment and being influenced by the --action_env flag. This will be used to declare dependency of remote repositories on environment variables (step 3 of https://bazel.build/designs/2016/10/18/repository-invalidation.html) -- Change-Id: I1ed3fb6f48e8e17d4d64c903fccecb6ed7596350 Reviewed-on: https://cr.bazel.build/7974 PiperOrigin-RevId: 146918603 MOS_MIGRATED_REVID=146918603
* Add a boolean flag to a Feature to specify whether it is enabled by default.Gravatar Googler2017-02-08
| | | | | | | | | This enables us to configure default features for each toolchain without having to hard-code anything in class such as CcCommon. -- PiperOrigin-RevId: 146904287 MOS_MIGRATED_REVID=146904287
* Apply --symlink_prefix to the output and exec root symlinks.Gravatar Luis Fernando Pino Duque2017-02-08
| | | | | | | | | | | | | | | | Turns out --symlink_prefix is not applied to the bazel-{out,workspace} unlike bazel-{bin,genfiles,testlogs} thus breaking the semantics of --symlink_prefix. This CL fixes the problem by using the symlink prefix instead of the product name when building the output and exec root symlinks. RELNOTES[INC]: Using --symlink_prefix is now applied to the output symlink (e.g. bazel-out) and the exec root symlink (e.g. bazel-workspace). -- PiperOrigin-RevId: 146902534 MOS_MIGRATED_REVID=146902534
* Bazel client: retry moving install base directoryGravatar Laszlo Csomor2017-02-08
| | | | | | | | | | | | | | | | | | | | | | | | | Do not give up immediately if renaming/moving the install base directory fails, wait and retry instead. This is necessary because on Windows the directory we just created and populated with the extracted embedded binaries may still be scanned by the antivirus, so there are open file handles in it so it cannot be renamed. This new logic ensures the AV has enough time to scan all files, close the handles, letting us successfully rename the directory. Fixes the occasional "install base directory cannot be renamed in place" error messages on Windows. See https://github.com/bazelbuild/bazel/issues/2107 -- PiperOrigin-RevId: 146899919 MOS_MIGRATED_REVID=146899919
* Just symlink instead of running 'lipo' on a single-architecture binaryGravatar Chris Parsons2017-02-08
| | | | | | -- PiperOrigin-RevId: 146847283 MOS_MIGRATED_REVID=146847283
* Treat configuration errors as failures in the master log.Gravatar Peter Schmitt2017-02-08
| | | | | | -- PiperOrigin-RevId: 146820813 MOS_MIGRATED_REVID=146820813
* Rollback of commit d11d510c571b10787856395709f9ad945ca70bb2.Gravatar Alex Humesky2017-02-08
| | | | | | | | *** Reason for rollback *** -- PiperOrigin-RevId: 146820790 MOS_MIGRATED_REVID=146820790
* Directory headers are filtered out of header inputs to objc compilation.Gravatar Cal Peyser2017-02-08
| | | | | | -- PiperOrigin-RevId: 146813606 MOS_MIGRATED_REVID=146813606
* Move all the resource processing tools into a "busybox".Gravatar Googler2017-02-08
| | | | | | | | | This makes the code simpler as well as reducing the number of targets to build. It also makes testing and profiling different action strategies vastly easier. -- PiperOrigin-RevId: 146812659 MOS_MIGRATED_REVID=146812659
* AppleCrosstoolTransition sets cpu based on platform.Gravatar Cal Peyser2017-02-08
| | | | | | -- PiperOrigin-RevId: 146812370 MOS_MIGRATED_REVID=146812370
* Allow aspects to adveritise providers they provide.Gravatar Dmitry Lomov2017-02-07
| | | | | | -- PiperOrigin-RevId: 146794883 MOS_MIGRATED_REVID=146794883
* Bazel client, Windows: compile more with MSVCGravatar Laszlo Csomor2017-02-07
| | | | | | | | | | | | | | | In this change: * remove some pdie calls from unimplemented method bodies in blaze_util_windows.cc, if implementing that method is not that important and/or can wait * move code from the msys-only #ifdef parts to common where it makes sense See https://github.com/bazelbuild/bazel/issues/2107 -- PiperOrigin-RevId: 146791575 MOS_MIGRATED_REVID=146791575
* Move android_sdk_for_testing bind into Android{S,N}dkRepositoryRule so that ↵Gravatar Adam Michael2017-02-07
| | | | | | | | | | eventually we can remove it from Bazel's WORKSPACE file. We'll need to wait for the next Bazel release to remove it from the WORKSPACE file. This should hopefully make the process of the Bazel sheriff running android_integration_test.sh a little easier. -- PiperOrigin-RevId: 146789106 MOS_MIGRATED_REVID=146789106
* Remove dead code in SkyframeLabelVisitorGravatar Ulf Adams2017-02-07
| | | | | | | | | | Two of the functions are never used, several of the parameter are not used or can be simplified (require callers to convert from Target -> Label). -- PiperOrigin-RevId: 146787380 MOS_MIGRATED_REVID=146787380
* Benchmark part 4: draw line chartsGravatar Yue Gan2017-02-07
| | | | | | -- PiperOrigin-RevId: 146773562 MOS_MIGRATED_REVID=146773562
* Add quotes to improve space supportGravatar Alexander Chung2017-02-07
| | | | | | | | | | | These changes addresses issues where Windows users have a space in their username. Allows the default output_base path to be used. Closes #2491. -- Reviewed-on: https://github.com/bazelbuild/bazel/pull/2491 PiperOrigin-RevId: 146773331 MOS_MIGRATED_REVID=146773331
* Rollback of commit 59450eb3770f539352c959dfae7ba04fd32e47b3.Gravatar Yue Gan2017-02-07
| | | | | | | | | | | | | | | | | | | | | | | *** Reason for rollback *** Previously rollbacked cl was fixed. *** Original change description *** Automated [] rollback of commit eaa5281942eaeda294b7e36ab012f592c1f637c2. *** Reason for rollback *** BazelBuilderTest failed to build on ci.bazel.io See https://github.com/bazelbuild/bazel/issues/2468 *** Original change description *** Benchmark part 3: main stuff -- PiperOrigin-RevId: 146764611 MOS_MIGRATED_REVID=146764611
* Windows: fix off-by-one errors with MAX_PATHGravatar Laszlo Csomor2017-02-07
| | | | | | | | | | | | | | | | | | In almost every place we compared paths against MAX_PATH, we had it wrong. MAX_PATH is the null-terminated maximum length, so paths exactly MAX_PATH long (not counting the null-terminator) were incorrectly considered short. Also fix the error message in the MSVC python wrapper, because it reported an incorrect path length limit in the warning message. See https://github.com/bazelbuild/bazel/issues/2107 -- PiperOrigin-RevId: 146762382 MOS_MIGRATED_REVID=146762382
* WindowsFileSystem.java: Fix createSymbolicLink when target is a relative path Gravatar Yun Peng2017-02-07
| | | | | | | | | | Fixed https://github.com/bazelbuild/bazel/issues/2494 -- Change-Id: I2ca335fa5b3a7759f57085717128912f09363789 Reviewed-on: https://cr.bazel.build/8650 PiperOrigin-RevId: 146761747 MOS_MIGRATED_REVID=146761747
generated by cgit v1.2.3 (git 2.39.1) at 2024-07-06 20:12:42 +0000