| Commit message (Collapse) | Author | Age |
... | |
|
|
|
|
|
|
| |
build.lib.
--
MOS_MIGRATED_REVID=106689603
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=106683157
|
|
|
|
|
|
|
|
|
| |
of vars.
RELNOTES: [jsonnet] Fix jsonnet_to_json rule to read code_vars from code_vars instead of vars.
--
MOS_MIGRATED_REVID=106678289
|
|
|
|
|
|
|
| |
Fixes #538.
--
MOS_MIGRATED_REVID=106674650
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=106634616
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=106613927
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=106613660
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=106607501
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=106605940
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=106605250
|
|
|
|
|
|
|
|
|
|
| |
maven_test on my 2010 Mac Mini:
Stats over 20 runs: max = 117.0s, min = 71.7s, avg = 82.6s, dev = 12.1s
so the 300s timeout should suffice.
--
MOS_MIGRATED_REVID=106604843
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=106604357
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
Follow-up to
--
MOS_MIGRATED_REVID=106600502
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=106597904
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=106584736
|
|
|
|
|
|
|
| |
location. Then, if unavailable, look relative to the workspace.
--
MOS_MIGRATED_REVID=106536282
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=106533345
|
|
|
|
|
|
|
|
|
| |
This was using -i to replace WORKSPACE in-place, but OS X requires -i to take an
argument ('' in this case) and Linux expects `sed -i''` and OS X expects
`sed -i ''`.
--
MOS_MIGRATED_REVID=106530804
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=106504113
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=106499960
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=106487671
|
|
|
|
|
|
|
|
| |
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=106459854
|
|
|
|
|
|
|
| |
created for flags that were renamed, but which were specified on the command line using their new name.
--
MOS_MIGRATED_REVID=106458953
|
|
|
|
|
| |
--
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
|
|
|
|
|
|
|
|
|
| |
that we don't abort evaluation until badly behaved builder has started.
Also fix the same race in MemoizingEvaluatorTest#interruptAfterFailFails (although that race would lead to spurious passes not fails).
--
MOS_MIGRATED_REVID=106427172
|
|
|
|
|
|
|
| |
sandboxing.
--
MOS_MIGRATED_REVID=106426071
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=106418732
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=106418596
|
|
|
|
|
|
|
| |
Should fix build on OSX.
--
MOS_MIGRATED_REVID=106415882
|
|
|
|
|
|
|
| |
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=106410378
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=106410161
|