| Commit message (Collapse) | Author | Age |
... | |
|
|
|
|
| |
--
MOS_MIGRATED_REVID=102835622
|
|
|
|
|
|
|
|
|
|
|
|
| |
They're actually in the volatile status file, which is where it seems
like they belong.
Fixes #216.
--
Change-Id: Ibec7737538ff5c1003b61d1bd3396948c61886de
Reviewed-on: https://bazel-review.googlesource.com/1950
MOS_MIGRATED_REVID=102791996
|
|
|
|
|
|
|
| |
Now that we don't clean the graph during catastrophes, we should be crashing hard in these cases.
--
MOS_MIGRATED_REVID=102785226
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Make Environment-s freezable: Introduce a class Mutability
as a revokable capability to mutate objects in an Environment.
For now, only Environment-s carry this capability.
Make sure that every Mutability is revoked in the same function that create...
This reinstates a change that previously rolled-back because it broke the
serializability of SkylarkLookupValue. Bad news: serializing it succeeds for the
wrong reason, because a SkylarkEnvironment was stored as a result (now an
Environment.Extension) that was Serializable but inherited its bindings from an Environment (now an Environment.BaseExtension) which wasn't Serializable.
Apparently, Java doesn't try to serialize the bindings then (or at least doesn't
error out when it fails), because these bindings map variable names to pretty
arbitrary objects, and a lot of those we find in practice aren't Serializable.
Thus the current code passes the same tests as the previous code, but obviously
the serialization is just as ineffective as it used to be.
--
MOS_MIGRATED_REVID=102776694
|
|
|
|
|
|
|
| |
objc_libraries.
--
MOS_MIGRATED_REVID=102775222
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=102770538
|
|
|
|
|
|
|
| |
depend on.
--
MOS_MIGRATED_REVID=102763340
|
|
|
|
|
|
|
|
|
|
|
|
| |
They're not cheap to serialize or reconstitute and we don't really need them.
This does leave some odd ends around, in particular i decided to keep deserialization context around as i can picture use for it soon. Also return non-null values from all
of EmptyLocation's method since while the javadocs declare that LineAndColumn and Path
can be null, there does exist code which does not take this into account, this is for
another change.
--
MOS_MIGRATED_REVID=102758810
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=102744198
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=102743954
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=102743729
|
|
|
|
|
|
|
| |
Some cosmetic changes with EnumSets.
--
MOS_MIGRATED_REVID=102742596
|
|
|
|
|
|
|
| |
NAME>" in the stub application.
--
MOS_MIGRATED_REVID=102733123
|
|
|
|
|
|
|
|
|
| |
to interrupt evaluation in constant time.
Some ParallelEvaluator tests that implicitly relied on cleaning happening before the next evaluation were moved into MemoizingEvaluatorTest as a result.
--
MOS_MIGRATED_REVID=102696653
|
|
|
|
|
|
|
|
|
| |
section in the AndroidManifest.xml when it already contains a <screen> tag for each density specified in the densities attribute.
RELNOTES: The <compatible-screens> section of the AndroidManifest.xml will not be overwritten if it already contains a <screen> tag for each of the densities specified on the android_binary rule.
--
MOS_MIGRATED_REVID=102691148
|
|
|
|
|
|
|
|
| |
Old message was e.g.
"No matching method found for $index(int) in set"
--
MOS_MIGRATED_REVID=102685114
|
|
|
|
|
|
|
|
|
| |
instrumentation/coverage purposes.
This is easier by grouping together all assembly files in a file set, thus justifying a simultaneous cleanup of the redundant usage of the assembler-with-cpp flag
--
MOS_MIGRATED_REVID=102671848
|
|
|
|
|
|
|
| |
of function calls in HTML output
--
MOS_MIGRATED_REVID=102663672
|
|
|
|
|
|
|
| |
subincludes of files in subdirectories of a package.
--
MOS_MIGRATED_REVID=102659838
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=102658808
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This was printing:
src/main/cpp/blaze_util.cc: In function 'bool blaze::WriteFile(const string&, const string&)':
src/main/cpp/blaze_util.cc:211:28: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
return r == content.size();
^
src/main/cpp/blaze_util.cc: In function 'bool blaze::CheckJavaVersionIsAtLeast(const string&, const string&)':
src/main/cpp/blaze_util.cc:334:41: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
for (i = 0; i < jvm_version_vect.size() && i < version_spec_vect.size();
^
src/main/cpp/blaze_util.cc:334:73: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
for (i = 0; i < jvm_version_vect.size() && i < version_spec_vect.size();
^
src/main/cpp/blaze_util.cc:344:34: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
if (i < version_spec_vect.size()) {
^
src/main/cpp/blaze_util.cc:345:39: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
for (; i < version_spec_vect.size(); i++) {
This also fixes that we weren't checking write()'s return code.
--
MOS_MIGRATED_REVID=102656105
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=102651489
|
|
|
|
|
|
|
| |
implemented timeout support.
--
MOS_MIGRATED_REVID=102651003
|
|
|
|
|
|
|
| |
a test. Fixes #431.
--
MOS_MIGRATED_REVID=102650964
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=102648848
|
|
|
|
|
|
|
|
| |
It's probably easier for users if all available rules are listed in the
same place. It also makes the left menu cleaner.
--
MOS_MIGRATED_REVID=102647614
|
|
|
|
|
|
|
| |
AspectValue.
--
MOS_MIGRATED_REVID=102643564
|
|
|
|
|
|
|
| |
NotifyingInMemoryGraph in tests.
--
MOS_MIGRATED_REVID=102616906
|
|
|
|
|
|
|
|
|
| |
opposed to treating the label name as a file (which the extension is stripped from).
This prevents this functionality from breaking if the target contains what looks like an extension (e.g. test.foo)
--
MOS_MIGRATED_REVID=102600479
|
|
|
|
|
|
|
| |
to roll our own for no reason.
--
MOS_MIGRATED_REVID=102597506
|
|
|
|
|
|
|
| |
actions.
--
MOS_MIGRATED_REVID=102592965
|
|
|
|
|
|
|
| |
Tracking issue: #432
--
MOS_MIGRATED_REVID=102592907
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
--
MOS_MIGRATED_REVID=102590114
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=102584924
|
|
|
|
|
|
|
| |
error.
--
MOS_MIGRATED_REVID=102582717
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=102570037
|
|
|
|
|
|
|
| |
Improvement for #424.
--
MOS_MIGRATED_REVID=102566748
|
|
|
|
|
|
|
|
|
| |
namespace-runner now have to be explicitly activated via --sandbox_debug.
Fixes #424.
--
MOS_MIGRATED_REVID=102566625
|
|
|
|
|
|
|
| |
tests that can only run under certain operating systems (e.g. Linux sandboxing tests can only run under Linux) into separate suites.
--
MOS_MIGRATED_REVID=102566414
|
|
|
|
|
|
|
| |
parts that can run via remote execution and those that can only run on the local machine (e.g. due to needing extended permissione).
--
MOS_MIGRATED_REVID=102565161
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=102565057
|
|
|
|
|
|
|
| |
necessary tools for integration tests.
--
MOS_MIGRATED_REVID=102564985
|
|
|
|
|
|
|
| |
Fix for a part of bug #397.
--
MOS_MIGRATED_REVID=102564902
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=102559969
|
|
|
|
|
|
|
|
|
| |
The lipo dependency is artificial; it's an artifact of how LIPO is implemented
in Bazel. Running these checks doesn't make sense; they unnecessarily
disallow perfectly valid scenarios.
--
MOS_MIGRATED_REVID=102550286
|
|
|
|
|
|
|
| |
They were broken by commit 05e2c5b4e0da2f88e12d95adbc63cc3d46a6fca6.
--
MOS_MIGRATED_REVID=102546907
|
|
|
|
|
|
|
| |
pipe2() does not exists on Darwin.
--
MOS_MIGRATED_REVID=102544058
|
|
|
|
|
|
|
|
| |
This is intended to make it easier to reimplement this in Skyframe, in order
to merge loading and analysis phases.
--
MOS_MIGRATED_REVID=102536532
|
|
|
|
|
|
|
|
| |
I had to comment out a couple of tests, I don't know why they're not passing
right now.
--
MOS_MIGRATED_REVID=102535967
|
|
|
|
|
|
|
|
|
| |
Previously the timing out information wasn't propagated to the
user, leading to a wrong FAILED message whereas the test was
timing out.
--
MOS_MIGRATED_REVID=102535481
|