[swift-dev] Turns out Incremental builds were not actually incremental
mgottesman at apple.com
Thu Jul 21 17:06:30 CDT 2016
> On Jul 21, 2016, at 2:54 PM, Jordan Rose <jordan_rose at apple.com> wrote:
> IIRC this was deliberate because of some past issues with things not getting rebuilt. In particular, even an incremental build should trash the module cache folder every build, and I don’t think we do this. Nicole, do you remember specifically why this was changed? (Or Mishal, when back from vacation?)
The problem IIRC actually had to do with cloning ninja without checking if we had already checked it out. I updated the bots to do a check if the directory exists before attempting to clone it.
>> On Jul 19, 2016, at 09:32, Michael Gottesman via swift-dev <swift-dev at swift.org> wrote:
>> Given the backup in the CI, I started looking at what was going on there and I found that the following incremental bots were actually /NOT/ incremental:
>> 1. OS X Swift incremental.
>> 2. 14.04 Linux Swift incremental.
>> 3. 15.10 Linux Swift incremental.
>> 4. OSX LLDB incremental
>> This is in addition to the smoke test bot which was also made non-incremental (I fixed it yesterday).
>> These are now incremental as they should be. This should reduce the load on the CI system.
>> swift-dev mailing list
>> swift-dev at swift.org
More information about the swift-dev