| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
| |
We wind up combining them anyway in the manifest file and it seems that
this is consistent with how we read them back. Return them all at once
to avoid tedious duplication in handling of them.
--
MOS_MIGRATED_REVID=93058482
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=93051778
|
|
|
|
|
|
|
| |
/bin/bash clobbers euid with uid, which is undesirable when process-wrapper is a setuid binary being used for isolation.
--
MOS_MIGRATED_REVID=93051178
|
|
|
|
|
|
|
| |
Better fix for #174.
--
MOS_MIGRATED_REVID=93045666
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The stat struct's size field is off_t, which varies in size between 32- and
64-bit systems. The size field in FileStatus.java is a long (which in Java
is always 64 bits) so the size is getting initialized incorrectly.
I can't think of a good way to add this to our integration tests, but I've
tested in manually on a VM.
Fixes #174.
--
MOS_MIGRATED_REVID=93038537
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=93026026
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=93025992
|
|
|
|
|
|
|
|
| |
s/seperated/separated.
--
Change-Id: I303e4ff20b241c2c58fe00ad0a5e340b5bff54d9
MOS_MIGRATED_REVID=93025985
|
|
|
|
|
|
|
| |
Fixes #164.
--
MOS_MIGRATED_REVID=93025634
|
|
|
|
|
|
|
| |
defaults package.
--
MOS_MIGRATED_REVID=93023029
|
|
|
|
|
|
|
|
| |
There is no implementation and thus nobody is calling/using it.
--
Change-Id: I2cf184e3d80eb0ef2b04ea4617697e8426cc7a58
MOS_MIGRATED_REVID=93018104
|
|
|
|
|
|
|
|
|
| |
Since we are now in C++11, this comment about C++03 and ARRAYSIZE()
macro (which we don't even have) does not apply and thus we can just remove it.
--
Change-Id: Id0c0c59eab5b90ff5f70d5078caa2c8e618d787a
MOS_MIGRATED_REVID=93017596
|
|
|
|
|
|
|
|
|
| |
This helps introduce new default options as we increase the number
of integration tests in Bazel.
--
Change-Id: I3cec89054c603c1b5ba0134227b6e9d5fc8029f1
MOS_MIGRATED_REVID=93016923
|
|
|
|
|
|
|
|
|
|
|
|
| |
The command used to compile storyboards for iOS targets was
leaving off the --target-device options, which would result
in an empty compiled storyboard. This commit updates the
command constructed so that it does pass those options and
builds non-empty storyboards.
--
Change-Id: Ief6aed6f61099fa19ec7846d2321b40f8fce1ab2
MOS_MIGRATED_REVID=93016471
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=93014182
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=93012735
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=92949679
|
|
|
|
|
|
|
|
|
|
| |
If the set_up method fails then the start timestamp file is not created and
the start timestamp argument to in the timestamp computation function will
be undefined leading to an unwanted error if set -u is activated.
--
Change-Id: I188e9302bbdb1049dc317765eaa653bafc5a51de
MOS_MIGRATED_REVID=92946436
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=92944321
|
|
|
|
|
|
|
|
| |
getPackageFragment() only returns the relative path within a repository,
getPathFragment() is needed to return the external path.
--
MOS_MIGRATED_REVID=92941601
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=92934993
|
|
|
|
|
|
|
| |
It's undocumented, but it can be used for experimentation.
--
MOS_MIGRATED_REVID=92928896
|
|
|
|
|
|
|
|
|
|
|
|
| |
Instead of updating the file size cache as a side effect of updating
the digest cache we combine them into one cache to make it harder for
them to fall out of sync (mainly by way of programmer error). This
should also have a smaller memory footprint.
Also fixes a bug around cached exceptions.
--
MOS_MIGRATED_REVID=92928216
|
|
|
|
|
|
|
|
| |
I noticed, while writing http://bazel.io/docs/cpp.html#including-external-libraries-an-example,
that the BUILD file didn't get reparsed when it changed. This fixes that.
--
MOS_MIGRATED_REVID=92921670
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=92920724
|
|
|
|
|
|
|
|
|
| |
execution phase.
Commands which do not perform execution would otherwise over-invalidate nodes.
--
MOS_MIGRATED_REVID=92864280
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=92843582
|
|
|
|
|
|
|
|
|
| |
Now that our toolchain supports stdint.h, we don't need to provide our
custom types ourselves through numbers.h.
--
Change-Id: I01de083e735e5cd64bcca723b19c55b9429632b7
MOS_MIGRATED_REVID=92840495
|
|
|
|
|
|
|
|
|
|
| |
when resolving source artifacts.
Fixes #152.
--
Change-Id: I16e711b77374ecdf07a014935fca39acadaa2081
MOS_MIGRATED_REVID=92838655
|
|
|
|
|
|
| |
--
Change-Id: Ib8b9d2e14481aadd5548fb20cd38695e6f489217
MOS_MIGRATED_REVID=92835475
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=92818911
|
|
|
|
|
|
| |
--
Change-Id: I9968c3da2210b630502b47b7ed96acd71c7d7349
MOS_MIGRATED_REVID=92749744
|
|
|
|
|
|
|
| |
MD5 error more informative so we can try to understand what's going on.
--
MOS_MIGRATED_REVID=92734374
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=92727637
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently the "families" attribute is defined on the ReleaseBundlingRule.
Due to the relationships between the iOS rule classes, this leaves some
rules that need to know the device family they are building for without
that knowledge. Specifically, objc_bundle_library() can build storyboards
outside of any app or extension, and thus needs to know the target device
families to use during compilation. For reference, this was discussed at
https://groups.google.com/d/msg/bazel-discuss/c-2nwFiqhWo/puESbFNGAYMJ
This commit moves the "families" attribute from ReleaseBundlingRule to
BundlingRule to accomplish this.
--
Change-Id: Ia0d146e85f1c2cdb13bd74aef4a57de1ad537e0f
MOS_MIGRATED_REVID=92725861
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=92725547
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=92716023
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=92715161
|
|
|
|
|
|
| |
--
Change-Id: I46b327ce0f4eae47e9663843382697c2224e0b09
MOS_MIGRATED_REVID=92565524
|
|
|
|
|
|
|
|
|
| |
encounters a node with an error.
We were doing this in most cases, but not if the error was in a node that was already done or was revalidated during change pruning.
--
MOS_MIGRATED_REVID=92521223
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=92474815
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=92472728
|
|
|
|
|
|
|
|
|
| |
the extra action.
This meant that the action was potentially being mutated on two threads, which was bad.
--
MOS_MIGRATED_REVID=92469122
|
|
|
|
|
|
|
| |
Further improvements on #167.
--
MOS_MIGRATED_REVID=92459390
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
features.
Features on the rule level modify features that are enabled at the package
level. Note that this behavior is different from how the current command line /
package level interaction is, but we probably want to change the command line
behavior.
Alternative implementations considered:
a) using package-level features as default value for the rule attribute; this
would make it hard for future transitions; adding a completely new feature
to a package should not require updating all rules that have overrides
b) putting all positive features and all negative features from command-line,
package, and rule attribute into a positive and negative set, and subtract
the negative from the positive set; this is how the command-line features
worked previously, but it makes it impossible to enable a features that
is disabled at the package level just for one rule.
RELNOTES: Add 'features' attribute on the rule level.
--
MOS_MIGRATED_REVID=92448449
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=92407038
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=92398218
|
|
|
|
|
|
|
| |
needed. Also clean up some lint warnings/unresolved references.
--
MOS_MIGRATED_REVID=92380618
|
|
|
|
|
|
|
|
|
| |
plist file.
RELNOTES: Set the bundle id on plist files referenced by XCode application target.
--
MOS_MIGRATED_REVID=92378112
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=92366919
|