| Commit message (Collapse) | Author | Age |
|
|
|
|
|
| |
Fixes #5260
PiperOrigin-RevId: 198110476
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 198107604
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 198103940
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 198095817
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 198094324
|
|
|
|
|
|
|
| |
This is no longer meaningful with the turndown of
(C++) LIPO.
PiperOrigin-RevId: 198092974
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 198086078
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a precursor to removing the DATA transition outright.
While we could also have changed the Mode.DATA instances to
Mode.TARGET (which would declare that we expect the attribute not
to apply any transition), that would break existing definitions and
make depot cleanup more delicate. Plus, these checks weren't being
consistently applied across attributes anyway so they don't really
offer much. A lot of this logic is really just leftover legacy
from the pre-dynamic configuration days.
PiperOrigin-RevId: 198085059
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Roll forward after fixing and rolling forward culprit CL. No changes besides rolling forward (masked by diffbase)
RELNOTES: none
PiperOrigin-RevId: 198084160
|
|
|
|
| |
PiperOrigin-RevId: 198081030
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Roll forward with fix:
I was assuming that R.txt and symbols files are always set, but they can be
null in some cases (especially in the old data processing pipeline). Properly
handle them here.
RELNOTES: none
PiperOrigin-RevId: 198075743
|
|
|
|
| |
PiperOrigin-RevId: 198074986
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 198071932
|
|
|
|
|
|
|
|
|
|
| |
This is a rollforward of CL/197725926 after depot fix.
NEW: Additional deletions of unused providers (no constructor call references).
NEW[last rollforward]: Allow java_* rules to depend on proto_libraries via runtime_deps and exports. This should avoid the breakage that caused the original rollback. The edges are no-ops and could be removed.
PiperOrigin-RevId: 198060345
|
|
|
|
|
|
|
|
| |
This is part of a chain of CLs that will pull initialization of
CcCompilationContext from CcCompilationHelper.
RELNOTES:none
PiperOrigin-RevId: 198060027
|
|
|
|
|
|
|
|
| |
Fixes #5263
RELNOTES: execution strategies line no longer handles differently the case
where all processes have the same strategy.
PiperOrigin-RevId: 198057496
|
|
|
|
| |
PiperOrigin-RevId: 198053509
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Crashes lots of targets in nightly blaze-2018.05.24-1:
PiperOrigin-RevId: 198049395
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
https://github.com/bazelbuild/bazel/commit/56d1b1c3122a3d1ec111baab339631b8c42c2c31 changed the signature of SandboxfsProcess#mount() to take a
PathFragment instead of a Path, and this broke the build of the test above.
Given that the test is marked as manual, this was not caught by CI.
Further, the test was failing to link in the test runner class, so it
would not execute properly. The missing dependency was incorrectly removed
by unknown commit because it had been specified as a deps instead of a
runtime_deps.
RELNOTES: None.
PiperOrigin-RevId: 198048748
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This expands on https://github.com/bazelbuild/bazel/commit/33f08e75fa4e7480f8d46b8305ce03a171adefa0 to ensure list-like behavior of range for the following operations
- str/repr/type
- equality and ordering
- append / augmented assignment
- concatenation
- all of the above with slices
This is a prerequisite to both optimizing range() while preserving its current API, as well as changing its API via an incompatible change flag.
RELNOTES: None
PiperOrigin-RevId: 198046941
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Crashes lots of targets in nightly blaze-2018.05.24-1:
PiperOrigin-RevId: 198041861
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 198036365
|
|
|
|
|
| |
RELNOTES:none
PiperOrigin-RevId: 198025150
|
|
|
|
|
|
|
| |
Instead,defer to ActionFS regarding the choice about delegation to top-level Filesystem.
RELNOTES: None
PiperOrigin-RevId: 197960416
|
|
|
|
|
|
|
| |
Also refactor away SkylarkModule.Resolver.
RELNOTES: None
PiperOrigin-RevId: 197955164
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 197949354
|
|
|
|
|
|
|
|
|
| |
well-defined.
Moving forward, if a class not already annotated with @SkylarkModule has SkylarkModule supertypes A and B, then it must be the case that A is a type of B, or B is a type of A. The skylark type of a given class is dictated by the *most specific* superclass annotated with @SkylarkModule.
RELNOTES: None.
PiperOrigin-RevId: 197946898
|
|
|
|
| |
PiperOrigin-RevId: 197946783
|
|
|
|
|
|
|
|
|
|
|
|
| |
It's more efficient to use properly sized array builders to avoid having
a need to dynamically adjust the size of the underlying array. The result
is improved performance (no need to copy elements to newly created array)
and better memory efficiency - no need to re-allocate and no extra space
is wasted.
Closes #5241.
PiperOrigin-RevId: 197946723
|
|
|
|
|
|
|
| |
This is useful before we optimize range() to return a lazy object that appears like a list to the user.
RELNOTES: None
PiperOrigin-RevId: 197944773
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 197941930
|
|
|
|
|
|
|
| |
wherever shell=True is set.
RELNOTES: None
PiperOrigin-RevId: 197939143
|
|
|
|
|
|
|
| |
with generic parameters
RELNOTES: None.
PiperOrigin-RevId: 197932265
|
|
|
|
| |
PiperOrigin-RevId: 197924560
|
|
|
|
|
| |
RELNOTES:none.
PiperOrigin-RevId: 197923013
|
|
|
|
|
|
| |
Closes #5257.
PiperOrigin-RevId: 197915412
|
|
|
|
|
|
| |
diagnosing of bloat.
PiperOrigin-RevId: 197915327
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 197915097
|
|
|
|
|
|
|
| |
and [AndroidResourcesInfo].r_txt to Skylark.
RELNOTES: none
PiperOrigin-RevId: 197902129
|
|
|
|
|
|
| |
should not exist.
PiperOrigin-RevId: 197895718
|
|
|
|
|
|
| |
Part of https://docs.google.com/document/d/1_UJKmAQ9EE8i3Pl0il3YLTYr-Q9EKYYyLatt2zohfyM/edit#
PiperOrigin-RevId: 197890685
|
|
|
|
|
|
|
|
|
|
|
|
| |
A bug in the lexer ignored indentation on the first line of a file. This now
causes an error.
Also, remove the COMMENT token from the lexer. Comments are now accessed separately. This will allow further optimizations in the lexer. It also aligns the code a bit more with the Go implementation.
RELNOTES[INC]:
Indentation on the first line of a file was previously ignored. This is now fixed.
PiperOrigin-RevId: 197889775
|
|
|
|
|
|
|
|
| |
Netty's HttpClientCodec always emits a LastHttpContent event and so we don't need to track the received bytes manually to know when we are done reading. The HttpBlobStore compares the hashes of the received bytes to give us confidence that what we received is correct.
Closes #5244.
PiperOrigin-RevId: 197887877
|
|
|
|
|
|
|
|
|
|
|
| |
The Android data Skylark API includes references to FileProvider. To move that
API to the skylarkbuildapi, we must first move this provider.
For more information about this migration, see
https://docs.google.com/document/d/1UDEpjP_qWQRYsPRvx7TOsdB8J4o5khfhzGcWplW7zzI/
RELNOTES: none
PiperOrigin-RevId: 197882296
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 197881012
|
|
|
|
|
|
|
|
|
|
|
|
| |
This changeset introduces tests for the `shallow_since` functionality that was introduced in 6496b1d1d25025f33406b1eaf9949cab126f08bd.
We test that if the user specifies a tag as well as a `shallow_since` that it fails since they are incompatible. We also verify that specifying a commit before the `shallow_since` date causes the clone to fail (albeit currently with a non-useful error message; perhaps that could be improved at a later date).
It also documents more clearly how to use the feature by explaining the format of the 'since' string.
Closes #5183.
PiperOrigin-RevId: 197875727
|
|
|
|
|
|
|
|
|
|
|
|
| |
...and point --experimental_distdir there, so that offline builds
are again possible out of the distribution archive.
Related #5175.
Fixes #5202.
To be cherry-picked for #5056.
Change-Id: I634296e9d83e4e18ed966b42f35acc63061259d9
PiperOrigin-RevId: 197866998
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Merge the manifest- and directory-based runfiles
strategies into the Runfiles class. The resulting
Runfiles object can look up runfiles from the
manifest or from the filesystem, as needed.
Change-Id: Ifff4b76849ce67248bb9152901024e241aaea800
Closes #5251.
Change-Id: Ifff4b76849ce67248bb9152901024e241aaea800
PiperOrigin-RevId: 197863872
|
|
|
|
|
|
|
|
|
|
| |
The `--shallow-since` option of git was introduced only in version 2.11 of git. However,
some widely used distributions ship older versions of git. So fall back to fully cloning
or fetching a repository if the respective shallow option is not know to the ambient git
command used.
Change-Id: I8f0aa0a12e294ff9cc8325975bd9333f6bf50939
PiperOrigin-RevId: 197863797
|
|
|
|
|
|
|
|
|
|
| |
If ${JAVABASE} is a relative path prefix it with ${PWD}
but if it's an absolute path just use that i.e. when
specified via --javabase.
Closes #5238.
PiperOrigin-RevId: 197863163
|