aboutsummaryrefslogtreecommitdiffhomepage
Commit message (Collapse)AuthorAge
...
* openjdk: update macOS openjdk image. Fixes #5532Gravatar buchgr2018-07-09
| | | | | | | | | | | I missed the java.instrument module when building the smaller openjdk. I have updated the jdk to include this module. This was the cause for #5532. The image was created by https://buildkite.com/bazel/build-embedded-jdk/builds/23 RELNOTES: None PiperOrigin-RevId: 203797576
* Adds interning to CcToolchainVariablesGravatar shahan2018-07-09
| | | | | | This entails adding equality to all VariableValue subclasses. PiperOrigin-RevId: 203796225
* Simple Markdown rendering for skydocGravatar cparsons2018-07-09
| | | | | | | This uses apache velocity engine templates to create markdown-HTML. There are other alternatives, but there is already precedent for depending on this library from docgen. RELNOTES: None. PiperOrigin-RevId: 203795431
* Allow rules to define an implicit "$toolchains" attribute which can be used toGravatar jcater2018-07-09
| | | | | | contribute Make variables. PiperOrigin-RevId: 203789736
* Bazel server, tools: ensure Readers are closedGravatar laszlocsomor2018-07-09
| | | | | | | | | | | | | | | | | | | | Follow-up to commit 59f17d6e0550bf63a0b6ef182e2d63474e058ede. Use try-with-resources to ensure Reader objects are closed eagerly. Eagerly closing Readers avoids hanging on to file handles until the garbage collector finalizes the object, meaning Bazel on Windows (and other processes) can delete or mutate these files. Hopefully this avoids intermittent file deletion errors that sometimes occur on Windows. See https://github.com/bazelbuild/bazel/issues/5512 RELNOTES: none PiperOrigin-RevId: 203771262
* Add more profiling information to better understand what's happening in ↵Gravatar twerth2018-07-09
| | | | | | | analysis phase. RELNOTES: None PiperOrigin-RevId: 203771085
* Revert "Update protobuf to 3.6.0. Fixes #5439"Gravatar Jakob Buchgraber2018-07-09
| | | | This reverts commit 6fd4e0edd4de22dec9eda13dc0b29214f2ca117e.
* Sync jmmv@'s table styles for the docs.bazel.build site.Gravatar jingwen2018-07-09
| | | | | | | | | | Sources: https://github.com/bazelbuild/bazel-blog/commit/846478d6943162f4c4d7d50001069e0ca7b2ec28 https://github.com/bazelbuild/bazel-blog/commit/aacaa25314678c08772372b3d46697f7963bb201 RELNOTES: None. PiperOrigin-RevId: 203763253
* Update protobuf to 3.6.0. Fixes #5439Gravatar Loo Rong Jie2018-07-09
|
* Revert "Update protobuf to 3.6.0. Fixes #5439"Gravatar Jakob Buchgraber2018-07-09
| | | | This reverts commit a2cac548616e6e6f433df27146c2971f352a4041.
* Update protobuf to 3.6.0. Fixes #5439Gravatar Loo Rong Jie2018-07-09
|
* Windows, CROSSTOOL: Fix feature for linking interface library and dynamic ↵Gravatar pcloudy2018-07-09
| | | | | | | | | | library 1. Do not apply /WHOLEARCHIVE to interface library 2. On Windows, we cannot link dll directly, so remove related flag_groups RELNOTES: None PiperOrigin-RevId: 203752406
* bep: introduce BuildEventArtifactUploaderFactoryGravatar buchgr2018-07-09
| | | | | | | | | | | | | | | | There can be multiple BuildEventTransports active at the same time and we need to ensure that each transport gets its own BuildEventArtifactUploader as these transports might have different lifecycles. We do that by introducing another level of indirection via the BuildEventArtifactUploaderFactory. BlazeModules now register a factory object instead of an uploader. In addition, the BuildEventArtifactUploader gets a shutdown() method that allows to free any resources associated with it. PiperOrigin-RevId: 203752092
* debian package: declare dependency on unzipGravatar Klaus Aehlig2018-07-09
| | | | | | | Fixes #5529 Change-Id: Ie3d45c4882355bd2f8b02c5afa1ad0248f28d505 PiperOrigin-RevId: 203751587
* buildkite: actually disable flaky testsGravatar buchgr2018-07-09
| | | | PiperOrigin-RevId: 203746935
* Windows,JNI: more robust nativeCreateJunctionGravatar Laszlo Csomor2018-07-09
| | | | | | | | | | | | | | | | | | | | | | | | Rewrite the CreateJunction function in the Windows JNI library. The new implementation's improvements: - succeeds if the junction already exists with the desired target; hopefully this will fix issue https://github.com/bazelbuild/bazel/issues/5433 - tolerant to concurrent filesystem modifications, e.g. if the junction's path suddenly disappears, the function reports the error correctly Fixes https://github.com/bazelbuild/bazel/issues/5433 Change-Id: I58a2314a00f6edaa7c36c35ba54616168b44eb7d Closes #5528. Change-Id: I9f5dc9237b70a433d0d8c2578a826de3d462d110 PiperOrigin-RevId: 203744515
* buildkite: disable flaky execution statistic tests on mac.Gravatar buchgr2018-07-09
| | | | | RELNOTES: None PiperOrigin-RevId: 203736658
* Improve logging for parsing skylark files.Gravatar twerth2018-07-09
| | | | | | | Also add preconditions check. RELNOTES: None. PiperOrigin-RevId: 203731929
* Delete UnionFileSystem.Gravatar lberki2018-07-09
| | | | | | | It was used in a single, Google-internal test which I cleaned up as pre-work for this change. RELNOTES: None. PiperOrigin-RevId: 203727293
* Make loading/analysis phase a lot faster.Gravatar Googler2018-07-09
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | There is a fundamental bottleneck in the way targets are currently configured: The ConfiguredTargetFunction needs to load all dependent targets before it can configure its own target. Now, outgoing deps of a target can be in three states: 1. Package of dependency target not yet loaded 2. Dependency target not configured, but package already loaded 3. Dependency target configured State #3 is good, we don't need to do any more work before we can configure the current target. Now, most targets will have a combination of deps in states #1 and #2. The current behavior is to schedule the target configuration of deps in state #2 and the package loading in state #1 (to get to state #3 and #2, respectively). Only after *all* of these are computed will the corresponding ConfiguredTargetFunction be rescheduled upon which the remaining deps that were in state #1 before are now in state #2 and the corresponding target configuration can be started. This creates a substantial parallelization bottleneck by artifically sync'ing the state transitions (#1->#2 and #2->#3) for all deps. In turn, this makes the critical path artifically long. Instead, settle for just loading dependent packages as long as there are any. This is a fast single-step operation. Postpone the configuration of dependent targets to later as it can require long dependency chains to be configured. In theory, a better solution would be to split the target configuration in a way so that it is possible to ask for configured targets without yet knowing their package. However, that would require pulling config transitions apart (as some of them happen because of the origin target/config and some of them happen because of the destination target. Thus we'd need to change the ConfiguredTargetKey so that the configuration stands for the configuration that we request the target in, with target-caused transitions already applied. Now that itself leads to inefficiencies. E.g. we would start requestiong InputFiles in several configurations just to underneath always load them with a null configuration. RELNOTES: Faster analysis by improved parallelization. PiperOrigin-RevId: 203725209
* Update Blaze user manual to mention the new blaze run behavior.Gravatar diamondm2018-07-09
| | | | | RELNOTES: None. PiperOrigin-RevId: 203723885
* vfs: fix race condition in JavaIoFileSystem.deleteGravatar Laszlo Csomor2018-07-09
| | | | | | | | | | | | | | | | | | | | | | | | | | | JavaIoFileSystem.delete() now uses Files.deleteIfExists() to delete files and empty directories. The old code used to have a race condition: a file could have been deleted or changed to a non-directory between checking it's a directory and listing its contents. WindowsFileSystem.delete() now uses the DeletePath JNI method (wrapped by WindowsFileOperations.deletePath) which is more robust than JavaIoFileSystem.delete(), because it can delete readonly files and can tolerate some concurrent filesystem modifications. Fixes https://github.com/bazelbuild/bazel/issues/5513 Change-Id: I5d2720afff8dfd3725880a6d7408d22de5935c3d Closes #5527. Change-Id: I5d2720afff8dfd3725880a6d7408d22de5935c3d PiperOrigin-RevId: 203720575
* Remove an unused method.Gravatar lberki2018-07-09
| | | | | | RELNOTES: None. PiperOrigin-RevId: 203720055
* PiperOrigin-RevId: 203687257Gravatar Googler2018-07-08
|
* Read proto javacopts directly in java_lite_proto_libraryGravatar cushon2018-07-06
| | | | | | instead of indirecting through the toolchain's compatible_javacopts. PiperOrigin-RevId: 203502116
* Update bazel toolchains to 0.15.0Gravatar hlopko2018-07-06
| | | | | | | Taken from releases.bazel.build/bazel-toolchains.html RELNOTES: None. PiperOrigin-RevId: 203494047
* Publish used_heap_size_post_build metric to BEP.Gravatar tomlu2018-07-06
| | | | | | | This metric measures the used heap size at the end of the build, after a GC. Because this is expensive it is only collected if a flag is passed. RELNOTES: PiperOrigin-RevId: 203492365
* Merge outputs in java_common.merge.Gravatar elenairina2018-07-06
| | | | | RELNOTES: [JavaInfo] Outputs are merged in java_common.merge(). PiperOrigin-RevId: 203474741
* Windows, CROSSTOOL: Remove MSVC wrapper scripts from Bazel completelyGravatar Yun Peng2018-07-06
| | | | | | | | | | | The only reason that those python wrapper scripts still exists is for TensorFlow's Windows GPU build. As we will create a custom GPU CROSSTOOL in TF repo, we can finally remove wrapper scripts from Bazel. Closes #5526. RELNOTES: Python wrapper scripts for MSVC are removed. PiperOrigin-RevId: 203472223
* Cleanup libs_to_link_dont_emit_objects_for_archiver build variableGravatar hlopko2018-07-06
| | | | | | | It's no longer needed. RELNOTES: None. PiperOrigin-RevId: 203469119
* Clarify documentation for implicit deps and default attr valuesGravatar brandjon2018-07-06
| | | | | RELNOTES: None PiperOrigin-RevId: 203466429
* Make skylark repository functions exportableGravatar Klaus Aehlig2018-07-06
| | | | | | | | | | In this way, their name is one they can actually be referred to by. This is necessary, as Skylark repository rules end up in the resolved file when freezing the versions of external dependencies---and the call to the repository function might be indirect. Change-Id: Ie1b5a28fac4f690c424de848b42d0c4a217d494d PiperOrigin-RevId: 203466286
* Don't unnecessarily create a NestedSet and remove a stale comment. We do ↵Gravatar Googler2018-07-06
| | | | | | | want to use input discovery when building modules for performance reasons. RELNOTES: None. PiperOrigin-RevId: 203463009
* Automatic code cleanup.Gravatar vladmos2018-07-06
| | | | PiperOrigin-RevId: 203461813
* Add an experimental option to disable .d-file scanning for modular builds. WhenGravatar Googler2018-07-06
| | | | | | | | | | | building with C++ modules, .d file scanning is not effective as Clang (only compiler supporting Bazel's version of C++ modules) reads all of the files passed in anyway. This is not meant to be activated yet, but for running experiments. RELNOTES: None. PiperOrigin-RevId: 203459168
* bep: guarantee event ordering in file transports.Gravatar buchgr2018-07-06
| | | | | | | | | | | Commit d3f7f7ae introduced a bug in the FileTransport implementations where events might not be written to file in the correct order. This change fixes this. Fixes #5515 RELNOTES: None PiperOrigin-RevId: 203457636
* Don't check if sandbox is supported over and over again.Gravatar twerth2018-07-06
| | | | | RELNOTES: None PiperOrigin-RevId: 203454741
* Make C++ extra action properly add module file flags for discovered C++Gravatar Googler2018-07-06
| | | | | | | modules. RELNOTES: None. PiperOrigin-RevId: 203454562
* Automatic code cleanup.Gravatar cushon2018-07-06
| | | | PiperOrigin-RevId: 203454459
* Create Bazel coverage report action.Gravatar elenairina2018-07-06
| | | | | | | Fixes #5246 RELNOTES: None. PiperOrigin-RevId: 203453340
* Fix autodetection of -z linker flagsGravatar hlopko2018-07-06
| | | | | | | | | | Clang reports missing -Wl,-z,relro as "ld: unknwon option: -z"). This cl fixes the autodetection to expect the short variant. Fixes #5468. RELNOTES: NONE. PiperOrigin-RevId: 203449206
* Windows,JNI: implement native DeletePath methodGravatar laszlocsomor2018-07-06
| | | | | | | | | | | | | | | | | | Implement a native DeletePath method that can delete files, directories, and junctions. The method should tolerate when concurrent processes delete the file. The new JNI function is more robust than Java IO file deletion function because it can also delete readonly files. See https://github.com/bazelbuild/bazel/issues/5513 Closes #5520. Change-Id: I21ea36dd64960b294e2b51600273bf4290ad7c0f PiperOrigin-RevId: 203448581
* windows,launcher: Rlocation function now handles absolute paths correctlyGravatar pcloudy2018-07-06
| | | | | | | Fix https://github.com/bazelbuild/bazel/issues/5516 RELNOTES: None PiperOrigin-RevId: 203448188
* blaze_util_freebsd.cc: include path.h explicitlyGravatar Klaus Aehlig2018-07-06
| | | | | | | | | | | ...as this file uses blaze_util::JoinPath. Apparently, until recently, that header file was pulled in indirectly, so that this wasn't detected until now. Nevertheless, the header files for functions used directly should also be included explicitly anyway. Change-Id: Id181480c6ec7fd146ce8b7b00980319f13c3f518 PiperOrigin-RevId: 203445044
* Remove stub toolchains for iosGravatar hlopko2018-07-05
| | | | | | | Should not be needed anymore since we have dynamic configurations for a while. RELNOTES: None. PiperOrigin-RevId: 203435557
* Replace instances of Blaze with Bazel.Gravatar Dan Fabulich2018-07-05
| | | | | | | PiperOrigin-RevId: 203300374 Change-Id: Iaa47f870ab2e0cad40a202aad2c7f9430f73c856 PiperOrigin-RevId: 203407392
* Reverse the order of java_toolchain.compatible_with and ↵Gravatar cushon2018-07-05
| | | | | | | | java_toolchain.package_configuration javacopts to allow package_configuration to override compatible_with javacopts. PiperOrigin-RevId: 203396587
* Remove support for java_runtime_suiteGravatar cushon2018-07-05
| | | | | RELNOTES: Remove support for java_runtime_suite; use alias() together with select() instead. PiperOrigin-RevId: 203393253
* bazel sync: better report errorsGravatar Klaus Aehlig2018-07-05
| | | | | | | | | | So far, bazel sync would only report error that happened during the actual fetch operation. However, errors can also happen earlier, e.g., when loading or parsing the WORKSPACE file. Report these errors as well. Change-Id: Ifa4961b0101f338d7618c52eb607951acba7ccdf PiperOrigin-RevId: 203359188
* PiperOrigin-RevId: 203352511Gravatar twerth2018-07-05
|
generated by cgit v1.2.3 (git 2.39.1) at 2024-07-09 09:14:41 +0000