| Commit message (Collapse) | Author | Age |
|
|
|
|
|
| |
--
PiperOrigin-RevId: 141904124
MOS_MIGRATED_REVID=141904124
|
|
|
|
|
|
|
|
|
|
|
| |
The actual issue is with the code that calls this method by way
of reflection. This is a temporary work around to fix #2232.
RELNOTES: An IE bug was fixed in repository_ctx.download_and_extract
--
PiperOrigin-RevId: 141899395
MOS_MIGRATED_REVID=141899395
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 141896569
MOS_MIGRATED_REVID=141896569
|
|
|
|
| |
Change-Id: I4e99ca21c95a1f6a4f46885adbee560f2a08ef17
|
|
|
|
|
|
|
|
|
|
|
| |
Getting back to the previous branch was confusing for users and
not really useful.
--
Change-Id: Icc3d4b30ab7d75de73fcb5885a215a08b96dfeb3
Reviewed-on: https://cr.bazel.build/7593
PiperOrigin-RevId: 141892852
MOS_MIGRATED_REVID=141892852
|
|
|
|
|
|
|
|
|
|
|
| |
This will silence the problems in #2227 and #2228 until the actual
underlying issues can be fixed.
--
Change-Id: Id2bc062104b4111bbcde8455f30059b3cb04eff6
Reviewed-on: https://cr.bazel.build/7870
PiperOrigin-RevId: 141892371
MOS_MIGRATED_REVID=141892371
|
|
|
|
|
|
|
|
|
|
|
|
| |
When these rules were originally written, I'd wanted the repository names embeded in the tarball to have a similar shape to Blaze's output trees, but unfortunately multi-level names were not yet supported. Support for multiple levels was introduced as part of the v2 registry specification, which is now all DockerHub supports, and the vast majority of clients in circulation support multi-level names. This change implements my original intention, which is to name the resulting image: bazel/{target}.
To get the legacy naming system use the attribute: embed_flat_names=True.
RELNOTES[INC]: docker_build: change the repository names embedded by docker_build. You can revert to the old behavior by setting legacy_repository_naming=True.
--
PiperOrigin-RevId: 141886976
MOS_MIGRATED_REVID=141886976
|
|
|
|
|
|
|
|
|
|
| |
Fixes https://github.com/bazelbuild/bazel/issues/564.
RELNOTES: aar_import rule is now documented.
--
PiperOrigin-RevId: 141843994
MOS_MIGRATED_REVID=141843994
|
|
|
|
|
|
|
|
|
|
|
| |
NDK12 removed the thumb and hard armeabi cpu variants, but
android_integration_test.sh still tried to build with them.
Fixes https://github.com/bazelbuild/bazel/issues/2184.
--
PiperOrigin-RevId: 141843012
MOS_MIGRATED_REVID=141843012
|
|
|
|
|
|
|
|
| |
0 is not a valid DOS timestamp, days and months start at 1.
--
PiperOrigin-RevId: 141818782
MOS_MIGRATED_REVID=141818782
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 141817345
MOS_MIGRATED_REVID=141817345
|
|
|
|
|
|
|
|
| |
execution cache.
--
PiperOrigin-RevId: 141807596
MOS_MIGRATED_REVID=141807596
|
|
|
|
|
|
|
|
| |
Helps debugging.
--
PiperOrigin-RevId: 141802189
MOS_MIGRATED_REVID=141802189
|
|
|
|
|
|
|
|
| |
Previously, at least one critical provider was not propagated (CppCompilationContext) which resulted in cc_library's being unable to find the generated headers.
--
PiperOrigin-RevId: 141800408
MOS_MIGRATED_REVID=141800408
|
|
|
|
|
|
| |
These are just bloating the git repository size.
Change-Id: I734cf6282eb6853217f68f0b33109b16424bde50
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 141784902
MOS_MIGRATED_REVID=141784902
|
|
|
|
|
|
|
|
| |
This method coerces any collection to a Skylark tuple, analogous to list() or set().
--
PiperOrigin-RevId: 141779268
MOS_MIGRATED_REVID=141779268
|
|
|
|
|
|
|
|
| |
API. This enables creating a TestEnvironmentProvider from Skylark.
--
PiperOrigin-RevId: 141775285
MOS_MIGRATED_REVID=141775285
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Turns out that ForkJoinTask#adapt(Callable) returns a ForkJoinTask whose Future#get on error throws a ExecutionException wrapping a RuntimeException wrapping the thrown checked exception from the callable. This is documented behavior [1] that I incorrectly didn't know about.
The additional level of wrapping meant that the catch-block of the parallel implementation of BinaryOperatorExpression wasn't rethrowing the InterruptedException/QueryException that the parallel task threw.
The subtly in this bug is that the query expression being evaluated needs to be of the form "e1 + e2", where evaluation of "e1" throws a QueryException even in keepGoing mode (note that most of the query errors actually go through AbstractBlazeQueryEnvironment#reportBuildFileError). The test I wrote picks on LetExpression's evaluation-time (rather than e.g. parsing time) validation of the variable name.
[1] https://docs.oracle.com/javase/7/docs/api/java/util/concurrent/ForkJoinTask.html#adapt(java.util.concurrent.Callable)
--
PiperOrigin-RevId: 141772584
MOS_MIGRATED_REVID=141772584
|
|
|
|
|
|
|
|
| |
--
Change-Id: Iedbdf32a80e0a4390ff8084a67eba191f544517f
Reviewed-on: https://cr.bazel.build/7770
PiperOrigin-RevId: 141771456
MOS_MIGRATED_REVID=141771456
|
|
|
|
|
|
|
|
|
|
|
|
| |
loading external repositories.
Fixes #2198.
--
Change-Id: Ife0232f8e4652a90bc3b7dceec6e67312a142879
Reviewed-on: https://cr.bazel.build/7691
PiperOrigin-RevId: 141771126
MOS_MIGRATED_REVID=141771126
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 141769552
MOS_MIGRATED_REVID=141769552
|
|
|
|
|
|
|
|
|
|
| |
Signed-off-by: David Pursehouse <dpursehouse@collab.net>
--
Change-Id: Ie8dc3a42fee8958e0bde66f35806d390e68d757e
Reviewed-on: https://cr.bazel.build/7750
PiperOrigin-RevId: 141743112
MOS_MIGRATED_REVID=141743112
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Commit 645dbc4 moved the file stating logic to
platform_utils.cc into the `stat_file` method,
then commit 8d6da00 added error reporting to that
method so callers wouldn't need to report errors
on their own. Problem is, one of the callers was
using stat_file for simple file existence checking
so reporting an error there was spurious.
Fixes https://github.com/bazelbuild/bazel/issues/2201
--
Change-Id: I40d1ee2bad8f3d03627c0b5c0bfd593bb5289d23
Reviewed-on: https://cr.bazel.build/7810
PiperOrigin-RevId: 141739581
MOS_MIGRATED_REVID=141739581
|
|
|
|
|
|
|
|
| |
the same srcs as they are.
--
PiperOrigin-RevId: 141604925
MOS_MIGRATED_REVID=141604925
|
|
|
|
|
|
|
|
|
|
| |
Instead they mount the individual files. Currently, non-empty tree artifacts result in ERR_DIRECTORY_NOT_EMPTY because we attempt to mount both the directory and the files inside it.
Fixes https://github.com/bazelbuild/bazel/issues/1745.
--
PiperOrigin-RevId: 141599030
MOS_MIGRATED_REVID=141599030
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 141594768
MOS_MIGRATED_REVID=141594768
|
|
|
|
|
|
|
|
|
|
| |
That is, if an Aspect registered an action that an extra-action is shadowing, its name will be used when creating the extra-action's ID and name.
Without this change, it's impossible to analyze extra-actions when there's more than one aspected rule that acts on the same rule (e.g., java_proto_library and java_lite_proto_library on the same proto_library).
--
PiperOrigin-RevId: 141587608
MOS_MIGRATED_REVID=141587608
|
|
|
|
|
| |
PiperOrigin-RevId: 141567840
MOS_MIGRATED_REVID=141567840
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 141561079
MOS_MIGRATED_REVID=141561079
|
|
|
|
|
|
|
|
|
|
|
| |
This confused me every time I looked it up. Thought that was working through some magic shell alias tricks until I found the files on my hard drive.
Closes #2203.
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/2203
PiperOrigin-RevId: 141556677
MOS_MIGRATED_REVID=141556677
|
|
|
|
|
|
|
|
| |
individual --whole_archive/--no_whole_archive blocks.
--
PiperOrigin-RevId: 141555295
MOS_MIGRATED_REVID=141555295
|
|
|
|
|
|
|
|
| |
xcode/SDK pair is unavailble.
--
PiperOrigin-RevId: 141554441
MOS_MIGRATED_REVID=141554441
|
|
|
|
|
|
|
|
| |
It wrongly stated that this only affects the timeout, however it actually affects the resources required for a test to run.
--
PiperOrigin-RevId: 141546278
MOS_MIGRATED_REVID=141546278
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 141535067
MOS_MIGRATED_REVID=141535067
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 141483567
MOS_MIGRATED_REVID=141483567
|
|
|
|
|
|
|
|
|
|
| |
attribute
This prevents duplicate symbol errors for objects that would otherwise be linked both in the application binary and a dylib the binary is linked against.
--
PiperOrigin-RevId: 141478238
MOS_MIGRATED_REVID=141478238
|
|
|
|
|
|
|
|
|
|
|
|
| |
At this point this does nothing more than re-run the exact same test without having to re-start the test runner.
In future iterations the aim is to be able to re-run tests with modified code, without having to re-start the test runner.
To test out the WorkerTestStrategy simply use --test_strategy=experimental_worker for a test with bazel.
--
PiperOrigin-RevId: 141465929
MOS_MIGRATED_REVID=141465929
|
|
|
|
|
|
|
|
|
|
| |
When running ProGuard in multiple phases, Bazel was picking up an
erroneous 0-byte seeds artifact. ProGuard only generates a seeds
artifact during NORMAL and INITIAL runtypes.
--
PiperOrigin-RevId: 141463120
MOS_MIGRATED_REVID=141463120
|
|
|
|
|
|
|
|
| |
This document states that $(CC) is the "C compiler". This is incomplete and misleading; per comments at line 1799 of CppConfiguration.java, it is expected to be a binary that will compile both C and C++ code.
--
PiperOrigin-RevId: 141459615
MOS_MIGRATED_REVID=141459615
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 141455148
MOS_MIGRATED_REVID=141455148
|
|
|
|
|
|
|
|
|
|
|
|
| |
of the startup options.
This allows us to do the following:
- Avoid using the product name when reporting startup option parsing errors.
- Passing --bazelrc as a command argument throws an error (fix for issue #1659).
--
PiperOrigin-RevId: 141445030
MOS_MIGRATED_REVID=141445030
|
|
|
|
|
|
|
|
|
|
|
|
| |
This startup option was deprecated months ago, however it is
currently parsed if present in the command line and a warning is
shown. Now an error is thrown if it is passed in the command line.
RELNOTES[INC]: The deprecated -x startup option has been removed.
--
PiperOrigin-RevId: 141441381
MOS_MIGRATED_REVID=141441381
|
|
|
|
|
|
|
|
| |
This should save on heap space for actions with long strings.
--
PiperOrigin-RevId: 141440705
MOS_MIGRATED_REVID=141440705
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 141438562
MOS_MIGRATED_REVID=141438562
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
An asynchronous clean without a complete purge and daemon shutdown is
particularly useful when the daemon takes an inordinate amount of time
to read output files for md5sums. Incurs a garbage collector invocation
after cache cleanup in the interest of correct usage reporting.
Closes #2053.
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/2053
PiperOrigin-RevId: 141437418
MOS_MIGRATED_REVID=141437418
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 141396618
MOS_MIGRATED_REVID=141396618
|
|
|
|
|
|
|
|
| |
We are no longer using the checked-in apksigner jar, instead we are now reading this JAR from the Android build tools. A follow-up change will remove the actual JAR. One small step towards making the Bazel binary smaller :)
--
PiperOrigin-RevId: 141355143
MOS_MIGRATED_REVID=141355143
|
|
|
|
|
|
|
|
|
| |
This hardcodes usage of proto-toolchains, which triggers strict-proto-deps.
Since strict-proto-deps relies on a proto-compiler feature which doesn't exist yet, I've also changed the default of --strict_proto_deps to 'default', which won't trigger the check unless specifically requested.
--
PiperOrigin-RevId: 141347426
MOS_MIGRATED_REVID=141347426
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Under --experimental_objc_library, breaks objc_library targets with empty sources.
*** Original change description ***
Better error message for experimental_objc_library targets built with a
crosstool that does not support objc.
--
PiperOrigin-RevId: 141344598
MOS_MIGRATED_REVID=141344598
|