| Commit message (Collapse) | Author | Age |
|
|
|
| |
PiperOrigin-RevId: 171013687
|
| |
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
PiperOrigin-RevId: 170960535
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 170955877
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 170899433
|
|
|
|
|
|
| |
RELNOTES: none
PiperOrigin-RevId: 170893783
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 170886429
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
When --define EXECUTOR=remote is specified in bazel command, embedded
tool zipper will be compiled remotely from source.
PiperOrigin-RevId: 170874829
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 170814591
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
correctness of default and static interface desugaring.
RELNOTES: none
PiperOrigin-RevId: 170779637
|
|
|
|
| |
PiperOrigin-RevId: 170752570
|
|
|
|
|
|
|
|
| |
Adding unit tests.
TESTED=unit tests
RELNOTES: None
PiperOrigin-RevId: 170750220
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 170722989
|
|
|
|
|
|
|
| |
For consistency with compile actions.
RELNOTES: None
PiperOrigin-RevId: 170702636
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
Change-Id: I830f42ad0fce63df504618e333a77f9cca15b7d5
|
|
|
|
|
|
|
|
| |
...so that bazel does not complain about internal files when
run with --all_incompatible_changes.
Change-Id: I9a12a7ab0cd6a92351fe17addd601d531f203aff
PiperOrigin-RevId: 170694212
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
| |
- 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
|
|
|
|
|
|
|
|
|
| |
Also update CommandHelper to split the heuristic label expansion code path from
the normal code path.
Progress on #2475.
PiperOrigin-RevId: 170675702
|
|
|
|
|
|
| |
Progress on #2475.
PiperOrigin-RevId: 170671644
|
|
|
|
|
|
| |
RELNOTES: none
PiperOrigin-RevId: 170553034
|
|
|
|
|
|
|
| |
HostTransition.
RELNOTES: None.
PiperOrigin-RevId: 170549656
|
| |
|
|
|
|
|
|
|
| |
linking. Also include assets in the aapt2 packaging action.
RELNOTES: none
PiperOrigin-RevId: 170532322
|
|
|
|
|
|
| |
Previously we'd do this on demand. This simplifies a bit.
PiperOrigin-RevId: 170526646
|
|
|
|
|
|
|
| |
resource library APK's.
RELNOTES: none
PiperOrigin-RevId: 170517806
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
PiperOrigin-RevId: 170503143
|
|
|
|
| |
PiperOrigin-RevId: 170500919
|
|
|
|
| |
PiperOrigin-RevId: 170494940
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
Temporary workaround for #3795.
PiperOrigin-RevId: 170473363
|
|
|
|
|
|
| |
Progress on #2475.
PiperOrigin-RevId: 170473111
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
The same binary is *outside* of the zip so there is no point in repeating it.
RELNOTES: None.
PiperOrigin-RevId: 170461181
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
Fixes https://github.com/bazelbuild/bazel/issues/3618
Change-Id: I1533088d4d51dc0510de5cd5b392edec95458057
PiperOrigin-RevId: 170458069
|
|
|
|
|
|
|
|
| |
https://cloud.google.com/pubsub/docs/reference/error-codes
TESTED=not really
RELNOTES: None
PiperOrigin-RevId: 170455553
|
|
|
|
|
|
|
|
|
| |
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
|