| Commit message (Collapse) | Author | Age |
... | |
|
|
|
|
| |
--
MOS_MIGRATED_REVID=106838787
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=106836859
|
|
|
|
|
|
|
|
|
|
| |
The only documentation about usable tags values was in a weird place,
along with duplicated information about flaky tests.
--
Change-Id: Ib98a0a5c582890512161ecf9f5d89c8e78d9ad68
Reviewed-on: https://bazel-review.googlesource.com/#/c/2220
MOS_MIGRATED_REVID=106832660
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=106826084
|
|
|
|
|
|
|
|
| |
This only affects tests that previously set a Reporter on the BlazeRuntime;
the production code is already using the per-command Reporter in all cases.
--
MOS_MIGRATED_REVID=106820846
|
|
|
|
|
|
|
|
|
|
| |
Changes the AbstractQueueVisitor strategy for varying its response to
unhandled exceptions from inheritance to composition. This will help
with a forthcoming switch from inheritance to delegation for
ValueVisitor's use of AbstractQueueVisitor.
--
MOS_MIGRATED_REVID=106730708
|
|
|
|
|
|
|
|
|
|
|
|
| |
This interface (mostly) encapsulates what the ValueVisitor expects
from the AbstractQueueVisitor class it currently inherits from. This
makes it easier for a future CL to change ValueVisitor's strategy of
code reuse from inheritance to composition.
RELNOTES:
--
MOS_MIGRATED_REVID=106728863
|
|
|
|
|
|
|
|
|
| |
"xcrun simctl" instead of iossim to launch the app when we invoke "blaze run".
The next CL is to use it in ios_runner.sh.mac_template after new bazle is released.
--
MOS_MIGRATED_REVID=106725049
|
|
|
|
|
|
|
| |
into a new .apple package, as it is not relevant for solely objc rules.
--
MOS_MIGRATED_REVID=106709486
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=106694515
|
|
|
|
|
|
|
|
|
| |
environment variable.
RELNOTES:none
--
MOS_MIGRATED_REVID=106694003
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, if the first run failed (in iteration order, which I don't
think is necessarily execution order) then
--runs_per_test_detects_flakes would report FAILED instead of FLAKY.
--
Change-Id: Ice7889d46203e1598d94a4e3c0bcbe13a45b0fe1
Reviewed-on: https://bazel-review.googlesource.com/#/c/2210/
MOS_MIGRATED_REVID=106693725
|
|
|
|
|
|
|
| |
build.lib.
--
MOS_MIGRATED_REVID=106689603
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=106683157
|
|
|
|
|
|
|
| |
Fixes #538.
--
MOS_MIGRATED_REVID=106674650
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=106634616
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=106613927
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=106605940
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=106605250
|
|
|
|
|
|
|
|
|
|
|
| |
If the proguard configuration itself contains -printmapping, this will override
the -printmapping specified on the command line (by virtue of coming later).
Putting it last means that this -printmapping will take precedence over any others,
meaning that Proguard will always generate the correct mapping, preventing an action
failure from not producing the correct output files.
--
MOS_MIGRATED_REVID=106601595
|
|
|
|
|
|
|
| |
Convert to Skylark values when destructuring a sequence or map.
--
MOS_MIGRATED_REVID=106591523
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=106588003
|
|
|
|
|
|
|
| |
Progress towards #445.
--
MOS_MIGRATED_REVID=106585570
|
|
|
|
|
|
|
|
|
|
|
| |
attributes that would otherwise be skipped by
default policy.
This is the simplistic start to a user-controllable
enforcement policy API.
--
MOS_MIGRATED_REVID=106530210
|
|
|
|
|
|
|
| |
Makes the the inevitable null pointer from unboxing null easier to diagnose.
--
MOS_MIGRATED_REVID=106525458
|
|
|
|
|
|
|
| |
the BUILD documentation.
--
MOS_MIGRATED_REVID=106515647
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=106515187
|
|
|
|
|
|
|
| |
again on OS X.
--
MOS_MIGRATED_REVID=106498988
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=106493557
|
|
|
|
|
|
|
| |
Special-case the return statement to avoid throwing an exception.
--
MOS_MIGRATED_REVID=106488391
|
|
|
|
|
|
|
| |
e.g. for i in list: pass
--
MOS_MIGRATED_REVID=106488146
|
|
|
|
|
|
|
|
| |
There's no timeline right now, but it's unusable on OSX and Oracle has no
plans of fixing it.
--
MOS_MIGRATED_REVID=106486015
|
|
|
|
|
|
|
| |
--
Change-Id: Ic5b08394e042fee48bf079620ecb18426455d838
Reviewed-on: https://bazel-review.googlesource.com/2230
MOS_MIGRATED_REVID=106480667
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
RuleContext returned fragments for the target configuration, even when Skylark requested fragments for the host configuration.
This Cl solves this bug. Since injecting a custom BuildConfiguration into out tests is surprisingly difficult, I tested this fix manually:
I wrote a custom bzl file with
def custom_rule_impl(ctx):
print("target = {}, host = {}".format(ctx.fragments.cpp.cpu, ctx.host_fragments.cpp.cpu))
and built the rule with --cpu ppc.
Output before the fix: target = ppc, host = ppc.
Output after the fix: target = ppc, host = k8.
--
MOS_MIGRATED_REVID=106479714
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=106444993
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Breaking O(150) tests on the blaze-2015.10.27-1 nightly TGP []
*** Original change description ***
Make -DNS_BLOCK_ASSERTIONS=1 by default when c=opt on objc builds.
--
MOS_MIGRATED_REVID=106435189
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
declare required configuration fragments: from
*everything* to *nothing*.
Now that all builtin rules properly declare their fragments,
the "backwards compatibility" concern that inspired the
original behavior is no longer needed.
This impacts, for example, filegroup rules, which have
nothing to declare.
--
MOS_MIGRATED_REVID=106433791
|
|
|
|
|
|
| |
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/524
MOS_MIGRATED_REVID=106431355
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=106418732
|
|
|
|
|
|
|
| |
RELNOTES: Bazel does strict validation of include files now to ensure correct incremental builds. If you see compilation errors when building C++ code, please make sure that you explicitly declare all header files in the srcs or hdrs attribute of your cc_* targets and that your cc_* targets have correct "deps" on cc_library's that they use.
--
MOS_MIGRATED_REVID=106410969
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=106410161
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=106409855
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=106407898
|
|
|
|
|
|
|
|
|
|
| |
philwo@philwo:/tmp/bazel$ ./output/bazel query 'labels(srcs, @androidndk//:arm-linux-androideabi-4.9-v7a-gnu-libstdcpp-toolchain_files)'
INFO: Empty results
This caused compiliation failures when building //examples/android/java/bazel:hello_world with sandboxing enabled.
--
MOS_MIGRATED_REVID=106405986
|
|
|
|
|
|
|
|
|
|
|
|
| |
//examples/android/java/bazel:hello_world with sandboxing enabled.
external/androidndk/ndk/toolchains/arm-linux-androideabi-4.9/prebuilt/linux-x86_64/bin/../lib/gcc/arm-linux-androideabi/4.9/../../../../arm-linux-androideabi/bin/ld: error: cannot open crtbegin_so.o: No such file or directory
external/androidndk/ndk/toolchains/arm-linux-androideabi-4.9/prebuilt/linux-x86_64/bin/../lib/gcc/arm-linux-androideabi/4.9/../../../../arm-linux-androideabi/bin/ld: error: cannot open crtend_so.o: No such file or directory
external/androidndk/ndk/toolchains/arm-linux-androideabi-4.9/prebuilt/linux-x86_64/bin/../lib/gcc/arm-linux-androideabi/4.9/../../../../arm-linux-androideabi/bin/ld: error: cannot find -lc
external/androidndk/ndk/toolchains/arm-linux-androideabi-4.9/prebuilt/linux-x86_64/bin/../lib/gcc/arm-linux-androideabi/4.9/../../../../arm-linux-androideabi/bin/ld: error: cannot find -ldl
--
MOS_MIGRATED_REVID=106405880
|
|
|
|
|
|
|
| |
aar does not contain the transitive closure of the target, as this is a common misconception.
--
MOS_MIGRATED_REVID=106396742
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=106389517
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=106382513
|
|
|
|
|
|
|
|
|
| |
Constants.ANDROID_DEP_PREFIX.
This regrettably entails adding the options parser to the embedded tools in the Bazel binary, but that's only a temporary measure until the embedded binaries are compiled (and not provided in source from)
--
MOS_MIGRATED_REVID=106379028
|
|
|
|
|
|
|
| |
($python_precompile, etc.)
--
MOS_MIGRATED_REVID=106352835
|