aboutsummaryrefslogtreecommitdiffhomepage
Commit message (Collapse)AuthorAge
* Remove support for ProtocolBuffers2.Gravatar kaipi2017-10-06
| | | | PiperOrigin-RevId: 171013687
* PiperOrigin-RevId: 170990066Gravatar fwe2017-10-06
|
* Only make files writable before processing on Windows.Gravatar ajmichael2017-10-06
| | | | | | | | | Prior to https://github.com/bazelbuild/bazel/commit/560b0ae4701dd2084160c45bb772396535b31f47, this was only done on Windows. This is super slow on mac for libraries with thousands of resources. RELNOTES: None PiperOrigin-RevId: 170964688
* Add an explicit dependency on jsr250_annotationsGravatar cushon2017-10-06
| | | | PiperOrigin-RevId: 170960535
* Fix more linter errorsGravatar ruperts2017-10-06
| | | | | RELNOTES: None. PiperOrigin-RevId: 170955877
* Remove dead code.Gravatar ajmichael2017-10-06
| | | | | RELNOTES: None PiperOrigin-RevId: 170899433
* tests for new desugar packageGravatar kmb2017-10-06
| | | | | | RELNOTES: none PiperOrigin-RevId: 170893783
* Fix the R.txt to generate a transitive closure instead of the current resources.Gravatar corysmith2017-10-06
| | | | | RELNOTES: None PiperOrigin-RevId: 170886429
* Bugfix: some clients are passing invalid UUIDs as ↵Gravatar olaola2017-10-06
| | | | | | | | | | BAZEL_INTERNAL_BUILD_REQUEST_ID. I added a check for build request id to be a valid UUID, and it broke them. TESTED=tap RELNOTES: None PiperOrigin-RevId: 170886183
* Enable switching embedded tools target for remote execution.Gravatar xingao2017-10-06
| | | | | | | When --define EXECUTOR=remote is specified in bazel command, embedded tool zipper will be compiled remotely from source. PiperOrigin-RevId: 170874829
* Fix example in backward compatibility page.Gravatar laurentlb2017-10-06
| | | | | RELNOTES: None. PiperOrigin-RevId: 170814591
* Use releases.bazel.build instead of googleapis.comGravatar Damien Martin-Guillerez2017-10-06
| | | | | | | | This URL works everywhere in the world and is easier to remember. It also allow us to change the backend transparently. Change-Id: I25ed753e5a4c27f26a8a1a86266cc06a3cf22744 PiperOrigin-RevId: 170789151
* add flags to desugar to emit metadata that can be used for double-checking ↵Gravatar kmb2017-10-06
| | | | | | | | correctness of default and static interface desugaring. RELNOTES: none PiperOrigin-RevId: 170779637
* Ignore unpopular deferred diagnostics in VanillaJavaBuilderGravatar cushon2017-10-06
| | | | PiperOrigin-RevId: 170752570
* Fixing displayed retry attempts one-off error, when the error is non-retriable.Gravatar olaola2017-10-06
| | | | | | | | Adding unit tests. TESTED=unit tests RELNOTES: None PiperOrigin-RevId: 170750220
* In apple integration tests, for fat simulator builds, specify a ↵Gravatar cparsons2017-10-06
| | | | | | | | | minimum_os_version < 11.0, as they are unsupported at 11.0. Fixes https://github.com/bazelbuild/bazel/issues/3841. RELNOTES: None. PiperOrigin-RevId: 170731919
* Skylark parser: make the end position of location ranges inclusive.Gravatar fzaiser2017-10-06
| | | | | | | | | Previously, the end line and column of a location were the position past the actual end of a location. This makes sense for the end offset, because one can use `input.substring(startOffset, endOffset)` to get the string belonging to an ASTNode. However the line and column (as opposed to the offset) aren't used for that. Therefore I made the change that the end line and column now point to the last character in the location. This is also they way every compiler I know does it. RELNOTES: none PiperOrigin-RevId: 170723732
* Documentation fix for 'minimum_os_version' attributeGravatar cparsons2017-10-06
| | | | | RELNOTES: None. PiperOrigin-RevId: 170722989
* Put feature arguments after command line options for LTOBackendActionGravatar Googler2017-10-06
| | | | | | | For consistency with compile actions. RELNOTES: None PiperOrigin-RevId: 170702636
* Attempting to fix an occasionally missing stdout from test.xml.Gravatar olaola2017-10-06
| | | | | | | | | | In hello-world_test, when executed inside a docker container, for about 2% of the runs the test.xml has an empty CDATA, instead of the expected "Hello, world!". I'm not sure still what exactly was the bug, but in any case this change simplifies the test execution code line, so if this doesn't fix it, at least further debugging will be easier. I ran the test in a loop 1360 times, and the error did not reproduce once, which hints towards this fixing it, since for an unpatched Bazel it reproduced 7 times out of 293 runs. TESTED=ran Bazel test in a loop RELNOTES: None PiperOrigin-RevId: 170702015
* Release 0.6.1 (2017-10-05)Gravatar Bazel Release System2017-10-05
| | | | | | | | | | | | | | | | | | | | | | | Baseline: 87cc92e5df35d02a7c9bc50b229c513563dc1689 Cherry picks: + a615d288b008c36c659fdc17965207bb62d95d8d: Rollback context.actions.args() functionality. + 7b091c1397a82258e26ab5336df6c8dae1d97384: Add a global failure when a test is interrupted/cancelled. + 95b0467e3eb42a8ce8d1179c0c7e1aab040e8120: Cleanups for Skylark tracebacks + cc9c2f07127a832a88f27f5d72e5508000b53429: Remove the status xml attribute from AntXmlResultWriter + 471c0e1678d0471961f1dc467666991e4cce3846: Release 0.6.0 (2017-09-28) + 8bdd409f4900d4574667fed83d86b494debef467: Only compute hostname once per server lifetime + 0bc9b3e14f305706d72180371f73a98d6bfcdf35: Fix bug in NetUtil caching. Important changes: - Only compute hostname once per server lifetime
* Add proguard 5.3.3 to third_party.Gravatar Adam Michael2017-10-05
| | | | | | | | | | See https://github.com/bazelbuild/bazel/issues/3777 The Android SDK provides a very old proguard and will be removing it soon, so we need to bundle our own. Change-Id: I054c54130bef1befc8591598768184fe23f76161 RELNOTES: None
* Add a bootstrap tomcat_annotations_api targetGravatar Liam Miller-Cushon2017-10-03
| | | | Change-Id: I830f42ad0fce63df504618e333a77f9cca15b7d5
* tools/build_defs/pkg/pkg.bzl: move load statement to the beginningGravatar Klaus Aehlig2017-10-02
| | | | | | | | ...so that bazel does not complain about internal files when run with --all_incompatible_changes. Change-Id: I9a12a7ab0cd6a92351fe17addd601d531f203aff PiperOrigin-RevId: 170694212
* Rewrite LocationExpanderGravatar ulfjack2017-10-02
| | | | | | | | | | | | | | | Split up the functionality into separate classes, and test each independently. (Keep one integration test to make sure it still works together.) This is in preparation for adding another location function for runfiles paths. Currently we have to decide ahead of time whether to expand artifacts as exec paths or root-relative (runfiles) paths, but there are cases where we can't make that decision ahead of time and / or need both to coexist, even in the same attribute. Progress on #2475. PiperOrigin-RevId: 170691666
* Extract Fileset manifest parsing out of SpawnInputExpanderGravatar ulfjack2017-10-02
| | | | | | | | | | - add a mode to control how to handle relative symlinks - if set, attempt to resolve relative symlinks in manifests by looking for another entry that defines a file with the intended symlink target (we don't do recursive resolution for now) - add more test coverage; fix a bug in handling empty target locations PiperOrigin-RevId: 170691492
* LocationExpander: always require options to be passed inGravatar ulfjack2017-10-02
| | | | | | | | | Also update CommandHelper to split the heuristic label expansion code path from the normal code path. Progress on #2475. PiperOrigin-RevId: 170675702
* Make JavaToolchain use the new Expander APIGravatar ulfjack2017-10-02
| | | | | | Progress on #2475. PiperOrigin-RevId: 170671644
* Add proto to encode desugaring metadataGravatar kmb2017-10-02
| | | | | | RELNOTES: none PiperOrigin-RevId: 170553034
* Prevent overriding android_library srcless deps configuration value from ↵Gravatar jingwen2017-10-02
| | | | | | | HostTransition. RELNOTES: None. PiperOrigin-RevId: 170549656
* PiperOrigin-RevId: 170539405Gravatar Googler2017-10-02
|
* Fix aapt2 actions to use the compiled intermediate resource files for ↵Gravatar Googler2017-10-02
| | | | | | | linking. Also include assets in the aapt2 packaging action. RELNOTES: none PiperOrigin-RevId: 170532322
* Only create builtins for rules once per PackageFactoryGravatar michajlo2017-10-02
| | | | | | Previously we'd do this on demand. This simplifies a bit. PiperOrigin-RevId: 170526646
* Use intermediate compiled resource symbols for linking rather than static ↵Gravatar Googler2017-10-02
| | | | | | | resource library APK's. RELNOTES: none PiperOrigin-RevId: 170517806
* Don't symlink into the execroot if possible in SymlinkAction: instead, ↵Gravatar janakr2017-10-02
| | | | | | symlink directly to the target artifact. Also offer the option to not provide the package roots to create the execroot: we would like to avoid the execroot if possible. PiperOrigin-RevId: 170515263
* build_event_stream_test: fix usage of ed(1)Gravatar Klaus Aehlig2017-09-29
| | | | | | | | | | | | | | Unfortunately the various ed(1)s are different in subtle ways. The difference that hit us here is the different treatment of the implicit 'e' command when ed is started with a file as argument; GNU ed writes the answer of that command (i.e., the number of bytes read) on stderr, whereas ed on FreeBSD writes it on stdout. So, let's merge the two output channels and throw away the first answer explicitly. Fixes #3842. Change-Id: I4ef394957cdc316f896b54ca218d4f118465caff PiperOrigin-RevId: 170506490
* Automatic code cleanup.Gravatar cushon2017-09-29
| | | | PiperOrigin-RevId: 170503143
* Clarify steps for introduction of backward incompatible changes.Gravatar michelleirvine2017-09-29
| | | | PiperOrigin-RevId: 170500919
* Switch ExtraActionFactory over to the new Expander interfaceGravatar ulfjack2017-09-29
| | | | PiperOrigin-RevId: 170494940
* Using only one GetMissingBlobs RPC per action instead of two.Gravatar olaola2017-09-29
| | | | | | | | This reduces the # of round-trips, improving overall latency, although I didn't profile by how much. TESTED=with remote execution RELNOTES: None PiperOrigin-RevId: 170484009
* Disable testCommandHonorsEnvironment on MacOS for nowGravatar ulfjack2017-09-29
| | | | | | Temporary workaround for #3795. PiperOrigin-RevId: 170473363
* Move expansion functionality to a new classGravatar ulfjack2017-09-29
| | | | | | Progress on #2475. PiperOrigin-RevId: 170473111
* Fix flakiness of BuildEventServiceTestsGravatar ulfjack2017-09-29
| | | | | | | | | | The flakiness was caused by waiting for the server to receive the second life-cycle event, but not waiting for the ack to get to the client. In that case, the interruption would happen before the life-cycle call returned, in which case it threw the InterruptedException, and then the stream doesn't exist yet, and so there's no mechanism to send anything to the server. PiperOrigin-RevId: 170472383
* Pass CppSemantics down to the CppLinkActionBuilderGravatar hlopko2017-09-29
| | | | | | | | | Currently CppLinkActionBuilder is not using CppSemantics, but it will when we use full CppCompileAction for linkstamp compiles. This cl is a preparation for that. RELNOTES: None. PiperOrigin-RevId: 170467826
* BEP: correctly report AliasConfiguredTargetsGravatar Klaus Aehlig2017-09-29
| | | | | | | | | When reporting the completion of a target specified by an alias, report the label of the alias, not that of the target being aliased to. Change-Id: If8416ceef73b01b7531ffa0012251f25a4e9f062 PiperOrigin-RevId: 170466076
* Remove client (or client.exe) from the Bazel self-extracting zip.Gravatar lberki2017-09-29
| | | | | | | The same binary is *outside* of the zip so there is no point in repeating it. RELNOTES: None. PiperOrigin-RevId: 170461181
* Windows CROSSTOOL: remove c++-link-executable from ↵Gravatar pcloudy2017-09-29
| | | | | | | | | interface_library_output_path flag set We shouldn't apply this flag set to c++-link-executable action, it will only add a /IMPLIB:ignore option. RELNOTES: None. PiperOrigin-RevId: 170459781
* Windows, sh tests: fix corrupt installation errorGravatar Laszlo Csomor2017-09-29
| | | | | | | Fixes https://github.com/bazelbuild/bazel/issues/3618 Change-Id: I1533088d4d51dc0510de5cd5b392edec95458057 PiperOrigin-RevId: 170458069
* Making RESOURCE_EXHAUSTED a retriable error, per guideine in: ↵Gravatar olaola2017-09-29
| | | | | | | | https://cloud.google.com/pubsub/docs/reference/error-codes TESTED=not really RELNOTES: None PiperOrigin-RevId: 170455553
* Move serialization test utilities from test/ to main/Gravatar brandjon2017-09-29
| | | | | | | | | This is so other packages can depend on them without violating our style guide. (Dependencies on test/ packages should be limited to aggregating test suites.) The target is also renamed from ".../serialization:serialization-test-base" to a new subpackage, ".../serialization/testutils:testutils". RELNOTES: None PiperOrigin-RevId: 170426906