aboutsummaryrefslogtreecommitdiffhomepage
Commit message (Collapse)AuthorAge
* Add JimFS to third_partyGravatar Liam Miller-Cushon2017-03-09
| | | | Change-Id: I9d16ab783e4d91f7a515103c4b6191c169f73570
* Add an --copy_bridges_from_classpath argumentGravatar Googler2017-03-09
| | | | | | | | | | This argument allows to copy bridges from interfaces that are on the classpath to the desugared classes. RELNOTES: Add an --copy_bridges_from_classpath argument to android desugaring tool -- PiperOrigin-RevId: 149631699 MOS_MIGRATED_REVID=149631699
* Bazel client, Windows: CreateDirectoryW path limitGravatar Laszlo Csomor2017-03-09
| | | | | | | | | | | | | | | Fix the path limit for non-UNC-prefixed paths when using CreateDirectoryW. According to MSDN [1], this is only 248 chars, as opposed to the usual 260 (MAX_PATH). See https://github.com/bazelbuild/bazel/issues/2107 [1] https://msdn.microsoft.com/en-us/library/windows/desktop/aa363855(v=vs.85).aspx -- PiperOrigin-RevId: 149627964 MOS_MIGRATED_REVID=149627964
* Singlejar: Windows-aware jar tool pathGravatar Laszlo Csomor2017-03-09
| | | | | | | | See https://github.com/bazelbuild/bazel/issues/2107 -- PiperOrigin-RevId: 149626394 MOS_MIGRATED_REVID=149626394
* Description redacted.Gravatar Nathan Harmata2017-03-09
| | | | | | -- PiperOrigin-RevId: 149585165 MOS_MIGRATED_REVID=149585165
* Desugar calls to Objects.requireNonNull(Object o) to o.getClass()Gravatar Googler2017-03-09
| | | | | | | | | | | | Only requireNonNull(Object o) is desugared. The following two overloaded versions are NOT desugared. requireNonNUll(Object o, String msg) requireNonNull(Object o, Supplier msg) RELNOTES: desugar calls to Objects.requireNonNull(Object o) with o.getClass() for android -- PiperOrigin-RevId: 149579668 MOS_MIGRATED_REVID=149579668
* Merging remote_cache and remote_worker into a single binary. Gravatar Ola Rozenfeld2017-03-09
| | | | | | | | | | | | | | | It can still be used as only a cache server, or only a worker with a wrapper of Hazelcast, so no functionality is lost, but it is now simpler to use in local testing / prototyping. Changed README files appropriately. TESTED=locally -- Change-Id: I3fdff9d434ce8cae5a6a700df0cb9f5bc364b60c Reviewed-on: https://cr.bazel.build/9253 PiperOrigin-RevId: 149569790 MOS_MIGRATED_REVID=149569790
* Set -> ImmutableSet in Platform.javaGravatar Cal Peyser2017-03-09
| | | | | | -- PiperOrigin-RevId: 149567942 MOS_MIGRATED_REVID=149567942
* Closing missing quote in htmlGravatar Laurent Le Brun2017-03-09
| | | | | | -- PiperOrigin-RevId: 149560999 MOS_MIGRATED_REVID=149560999
* Make external workspace handling forwards and backwards compatible.Gravatar Googler2017-03-09
| | | | | | | | | Add a field to the IntelliJ aspect proto which handles both current and future formats. -- PiperOrigin-RevId: 149559228 MOS_MIGRATED_REVID=149559228
* Add support for 'macos' platform_type in apple binary. This type is only ↵Gravatar Cal Peyser2017-03-09
| | | | | | | | supported for crosstool builds - there is no support in LegacyCompilationSupport. -- PiperOrigin-RevId: 149558653 MOS_MIGRATED_REVID=149558653
* Bazel client: use PathAsJvmFlag for JVM flagsGravatar Laszlo Csomor2017-03-09
| | | | | | | | | | | | | | | | | The Windows-implementation of this function shortens paths that we pass to the JVM, such as the Bazel server jar's path, the log file path, etc. These must be shortened because the JVM doesn't handle long paths. We don't shorten paths passed to the Bazel server itself though because Bazel can handle long paths. See https://github.com/bazelbuild/bazel/issues/2107 -- PiperOrigin-RevId: 149548361 MOS_MIGRATED_REVID=149548361
* BEP: provide timing information for tests Gravatar Klaus Aehlig2017-03-09
| | | | | | | | | | For tests, also provide information on the time the test took. -- Change-Id: I8e71391e4dd97627d6293159a0cbb0d922683af7 Reviewed-on: https://cr.bazel.build/9214 PiperOrigin-RevId: 149547633 MOS_MIGRATED_REVID=149547633
* Bring back the persistent test runner functionality, on ExperimentalTestRunner.Gravatar Kush Chakraborty2017-03-09
| | | | | | | | This is essentially a rollforward of commit 7d0561b6ca92d72bd8767d4dca50e5437976812c, and changes triggering the perisitent runner using an environment variable instead of argument as suggested in commit 7d0561b6ca92d72bd8767d4dca50e5437976812c -- PiperOrigin-RevId: 149540564 MOS_MIGRATED_REVID=149540564
* Small fixes: title case and rendering of rule names.Gravatar Googler2017-03-09
| | | | | | -- PiperOrigin-RevId: 149536881 MOS_MIGRATED_REVID=149536881
* Create ExperimentalTestRunner which is just the same as BazelTestRunner, but ↵Gravatar Kush Chakraborty2017-03-09
| | | | | | | | | | a testbed of upcoming changes, without breaking existing test targets. To use the alternate test runner a java test should add the tag "experimental_testrunner" and depend on "@bazel_tools//tools/jdk:ExperimentalTestRunner_deploy.jar" (instead of @bazel_tools//tools/jdk:TestRunner_deploy.jar) -- PiperOrigin-RevId: 149536298 MOS_MIGRATED_REVID=149536298
* Make Bazel build with MSVC-default-toolchain Bazel Gravatar Yun Peng2017-03-08
| | | | | | | | | | | | | After this change, a msys bazel can be built with a MSVC-default Bazel by adding --cpu=x64_windows_msys --host=x64_windows_msys See https://github.com/bazelbuild/bazel/issues/2627 -- Change-Id: Iaa82bf4dd911c5740b98d3b2739dfccca6203f79 Reviewed-on: https://cr.bazel.build/9293 PiperOrigin-RevId: 149532274 MOS_MIGRATED_REVID=149532274
* Make MSVC CROSSTOOL default on Windows Gravatar Yun Peng2017-03-08
| | | | | | | | | | | | | | | | The default C++ CROSSTOOL on Windows now becomes MSVC, --cpu=x64_windows_msvc is still supported To use MSYS toolcahin, add --cpu=x64_windows_msys and --host_cpu=x64_windows_msys for host compilation See https://github.com/bazelbuild/bazel/issues/2627 -- Change-Id: Ie788a39cb5ffbc9fc956ccfd51a3cc816c74543a Reviewed-on: https://cr.bazel.build/9292 PiperOrigin-RevId: 149530250 MOS_MIGRATED_REVID=149530250
* Make sure that the external version of skylark-overview.html is being ↵Gravatar Florian Weikert2017-03-08
| | | | | | | | displayed properly. -- PiperOrigin-RevId: 149528271 MOS_MIGRATED_REVID=149528271
* Windows: Assist JNI builds with a target for jni_md.h. Gravatar Asim Shankar2017-03-08
| | | | | | | | | | | | | This rule can be used in building JNI shared libraries for Windows. For example, see TensorFlow usage of these targets in jdk.BUILD: https://github.com/tensorflow/tensorflow/blo[]a98083a6c16f263d668271889863596efbeb84/tensorflow/java/src/main/native/BUILD#L68 Closes #2599. -- Reviewed-on: https://github.com/bazelbuild/bazel/pull/2599 PiperOrigin-RevId: 149527656 MOS_MIGRATED_REVID=149527656
* Introduce strip_debug_symbols feature to crosstoolGravatar Marcel Hlopko2017-03-08
| | | | | | | | | This cl removes hard coded -Wl,-S flag from Blaze and moves it to the crosstool. -- PiperOrigin-RevId: 149525225 MOS_MIGRATED_REVID=149525225
* Do not create symlink pointing at itself with ↵Gravatar Marcel Hlopko2017-03-08
| | | | | | | | | | | | | | | strip_include_prefix/include_prefix This cl fixes a bug when strip_include_prefix and include_prefix are used in such a way that the resulting virtual header is be accessible from the same path as the original header and bazel would attempt to create symlink pointing at itself. Fixes #2635 -- PiperOrigin-RevId: 149524480 MOS_MIGRATED_REVID=149524480
* Fix a broken link to the newly added one-page Skylark overview.Gravatar Florian Weikert2017-03-08
| | | | | | | | Now we only have to find out why it's not being rendered properly. -- PiperOrigin-RevId: 149524453 MOS_MIGRATED_REVID=149524453
* Make gold autodetection more robust on macosGravatar Marcel Hlopko2017-03-08
| | | | | | | | | | | | | | Some macos clang versions don't fail when setting -fuse-ld=gold, which makes cc_configure.bzl think gold linker is available, when it is actually not. The sideeffect of this cl is that we will not autodetect gold when only a very old (year 2010 and older) is present. I assume this is fine. Fixes #2502 -- PiperOrigin-RevId: 149521872 MOS_MIGRATED_REVID=149521872
* Add an android integration test for missing environment variables. Gravatar Adam Michael2017-03-08
| | | | | | | | | | | This is a test for https://bazel-review.googlesource.com/c/9213 and would have caught https://github.com/bazelbuild/bazel/issues/2621. -- Change-Id: I6c0fb10cc86f6f0dab02e931e9710e1b5168320c Reviewed-on: https://cr.bazel.build/9270 PiperOrigin-RevId: 149512997 MOS_MIGRATED_REVID=149512997
* Add a source_jars variable to OutputJar.Gravatar Irina Iancu2017-03-08
| | | | | | | | | | | Having a correlation between an output jar and a source jar is not enough. There may be situations when an output jar is generated from more source jars, not just one. We need this flexibility especially in Skylark for the java sandwich, when the user can compile multiple source jars. -- PiperOrigin-RevId: 149510534 MOS_MIGRATED_REVID=149510534
* Uppercase some hand-selected environment variable names on Windows/MSVC.Gravatar Dmitry Lomov2017-03-08
| | | | | | | | -- Change-Id: Ie1f3be6258f024d352ff4571a5355660f409f70d Reviewed-on: https://cr.bazel.build/9291 PiperOrigin-RevId: 149470780 MOS_MIGRATED_REVID=149470780
* Apply the apple crosstool transition to j2objc_library.Gravatar Cal Peyser2017-03-08
| | | | | | -- PiperOrigin-RevId: 149460936 MOS_MIGRATED_REVID=149460936
* VanillaJavaBuilder: don't crash formatting diagnostics without a source fileGravatar Liam Miller-Cushon2017-03-08
| | | | | | | | Fixes #2646 -- PiperOrigin-RevId: 149448578 MOS_MIGRATED_REVID=149448578
* Apple-specific environment variables are derived from the CROSSTOOL insteadGravatar Cal Peyser2017-03-08
| | | | | | | | | of hardcoded in AppleCcToolchain. Also, apply environment variables to objc archives. -- PiperOrigin-RevId: 149439637 MOS_MIGRATED_REVID=149439637
* Support composed dependency transitions with dynamic configs.Gravatar Greg Estren2017-03-08
| | | | | | -- PiperOrigin-RevId: 149439502 MOS_MIGRATED_REVID=149439502
* Global cleanup change.Gravatar Googler2017-03-08
| | | | | | -- PiperOrigin-RevId: 149437323 MOS_MIGRATED_REVID=149437323
* Env.vars: server won't ignore the client envGravatar Dmitry Lomov2017-03-08
| | | | | | | | | | | | | | | | | | Make the --ignore_client_env flag a no-op. The client will pass --client_env flags to the server even in --batch mode. This simplifies the code as well as ensuring that the server always uses the up-do-date client environment. We'll gradually get rid of all System.getenv calls in the server, because the server should always respect the client env. Roll forward of 149403129 with fixes. -- PiperOrigin-RevId: 149435060 MOS_MIGRATED_REVID=149435060
* Fix bug with streaming bounded deps/allrdeps/rdeps.Gravatar Nathan Harmata2017-03-08
| | | | | | -- PiperOrigin-RevId: 149431500 MOS_MIGRATED_REVID=149431500
* Fix buildtools test on WindowsGravatar Kristina Chodorow2017-03-08
| | | | | | | | It looks like Windows PathFragments are all converted to lower-case. -- PiperOrigin-RevId: 149425977 MOS_MIGRATED_REVID=149425977
* Select the good guava jars for JDK7 buildGravatar Damien Martin-Guillerez2017-03-07
| | | | | | | | | | Manually tested with ./compile.sh and JAVA_VERSION=1.7 Fixes #2644. -- PiperOrigin-RevId: 149422627 MOS_MIGRATED_REVID=149422627
* Don't update the action locality for actions with a null ownerGravatar Ulf Adams2017-03-07
| | | | | | -- PiperOrigin-RevId: 149418372 MOS_MIGRATED_REVID=149418372
* Fix calling of test Gravatar Klaus Aehlig2017-03-07
| | | | | | | | | | | For test (a.k.a '[') the closing bracket has to be a separate argument. Fix this by adding the missing space. -- Change-Id: Ie1d64bc1fa37f85ee0c7b5520b2ba12a30c9f635 Reviewed-on: https://cr.bazel.build/9290 PiperOrigin-RevId: 149418360 MOS_MIGRATED_REVID=149418360
* Typo fixGravatar Jon Brandvein2017-03-07
| | | | | | -- PiperOrigin-RevId: 149418254 MOS_MIGRATED_REVID=149418254
* Rollback of commit 94d8f4e9c8c8757aa7ab7c1a7c3e9afb34039127.Gravatar Klaus Aehlig2017-03-07
| | | | | | | | | | | | | | | | | | | | | | | | *** Reason for rollback *** broke //src/test/shell/bazel:bazel_bootstrap_distfile_test *** Original change description *** Env.vars: server won't ignore the client env Make the --ignore_client_env flag a no-op. The client will pass --client_env flags to the server even in --batch mode. This simplifies the code as well as ensuring that the server always uses the up-do-date client environment. We'll gradually get rid of all System.getenv calls in the server, because the server should always respect the client env. -- PiperOrigin-RevId: 149416602 MOS_MIGRATED_REVID=149416602
* Initialize the mutex in JNIEventsDiffAwareness Gravatar Julio Merino2017-03-07
| | | | | | | | | | | | | | | | | | | | | | | | pthread mutexes must be initialized with pthread_mutex_init and cleaned up with pthread_mutex_destroy. This seems to fix a race where poll() would access invalid array indexes on an array constructed based on the size of a shared list protected by the mutex. This is understandable because the mutex may not have been doing anything due to the lack of its proper initialization -- and, if so, I'm surprised the consequences were not more catastrophic. As with any race condition, it is hard to confirm that this fixes the observed problem, but I could trivially reproduce this issue earlier and now I cannot with this fix after tens of runs. See reproduction code in the referenced bug for details on how to expose the issue. Fixes #1676. -- Change-Id: Ia5a4a8f12da7c3780f33266b9922eeba7645b3a4 Reviewed-on: https://cr.bazel.build/9230 PiperOrigin-RevId: 149414125 MOS_MIGRATED_REVID=149414125
* Env.vars: server won't ignore the client envGravatar Laszlo Csomor2017-03-07
| | | | | | | | | | | | | | | | Make the --ignore_client_env flag a no-op. The client will pass --client_env flags to the server even in --batch mode. This simplifies the code as well as ensuring that the server always uses the up-do-date client environment. We'll gradually get rid of all System.getenv calls in the server, because the server should always respect the client env. -- PiperOrigin-RevId: 149403129 MOS_MIGRATED_REVID=149403129
* Windows, JNI: allow empty cwd for processesGravatar Laszlo Csomor2017-03-07
| | | | | | | | | | | | | | | | More specifically, change windows_util.AsShortPath to accept empty inputs, as well as paths with forward slashes. Also output more accurate error messages for bad input paths than before. This fixes //src/test/java/com/google/devtools/build/lib:windows-tests but not //src/test/java/com/google/devtools/build/lib:standalone-tests -- PiperOrigin-RevId: 149399449 MOS_MIGRATED_REVID=149399449
* Use the correct path when generating the command-line on Windows.Gravatar Philipp Wollermann2017-03-07
| | | | | | | | We already constructed it in the code via blaze_util::AsShortWindowsPath, but accidentally didn't use the results. -- PiperOrigin-RevId: 149398556 MOS_MIGRATED_REVID=149398556
* StandaloneTestStrategy sets the full list of outputs on the test spawnGravatar Ulf Adams2017-03-07
| | | | | | | | | | | | | | | | | | | All spawn strategies already treat all normal outputs as optional. Bazel checks at the action level whether all action outputs are created, but does not check at the spawn level. Spawn.getOptionalOutputs is therefore unnecessary, and removed in this change. The only place where this was set was in StandaloneTestStrategy, which now specifies the full set of outputs, which is now computed by TestRunnerAction. The internal test strategy implementations are also updated in this change. While I'm at it, also remove the use of BaseSpawn and use SimpleSpawn instead. This may go some way towards fixing #1413 and #942. -- PiperOrigin-RevId: 149397100 MOS_MIGRATED_REVID=149397100
* Bazel client, Windows/MSVC: fix path handling bugsGravatar Laszlo Csomor2017-03-07
| | | | | | | | | | | | | | | | | | | | Fix blaze_util_windows.ConvertPath: in the MSVC version this is using the actual %PATH% value, we don't need to convert it. Fix blaze_util_windows.PathAsJvmFlag: shorten the path so we can pass it to the JVM process (long paths aren't understood by the shell), but also converrt backslashes to forward slashes so the JVM won't believe we are passing paths with escaped characters. See https://github.com/bazelbuild/bazel/issues/2107 See https://github.com/bazelbuild/bazel/issues/2181 -- PiperOrigin-RevId: 149396971 MOS_MIGRATED_REVID=149396971
* Fix NPE in Android{S,N}dkRepositoryFunction.Gravatar Adam Michael2017-03-07
| | | | | | | | | | | | | | | If neither the path attribute or the $ANDROID_HOME/$ANDROID_NDK_HOME environment variable is set, we should report a helpful error message. A previous change switched the lookup for the environment variable from the client environment map to the skyframe environment map. However in the skyframe action environment map, environment variables that are requested but not set in the environment have null values. Followup to change needed for #2621. -- PiperOrigin-RevId: 149369076 MOS_MIGRATED_REVID=149369076
* AndroidResourceProcessor: sort files before writing zipsGravatar Googler2017-03-07
| | | | | | | | | | | | walkFileTree can be non-determinisitic, so the zip entries can be listed in a different order: "A file tree is walked depth first, but you cannot make any assumptions about the iteration order that subdirectories are visited." -- PiperOrigin-RevId: 149345145 MOS_MIGRATED_REVID=149345145
* Update android tutorial to clarify android sdk path options Gravatar Iain McGinniss2017-03-07
| | | | | | | | | | | The android_sdk_repository path parameter is now optional, and for most setups it is easier to omit it and rely on the `ANDROID_HOME` environment variable. Updated this part of the tutorial to clarify this. Closes #2632. -- Reviewed-on: https://github.com/bazelbuild/bazel/pull/2632 PiperOrigin-RevId: 149337570 MOS_MIGRATED_REVID=149337570
* Add the label_keyed_string_dict design doc to Bazel's site.Gravatar Michael Staib2017-03-07
| | | | | | -- PiperOrigin-RevId: 149319159 MOS_MIGRATED_REVID=149319159
generated by cgit v1.2.3 (git 2.39.1) at 2024-07-03 01:46:33 +0000