I figured this was a 16.10 issue because PR bot (16.04) passed, however I wasn't able to reproduce this locally after installing 16.10, I pushed a commit to pin point the failure line but that integration went fine. I will keep an eye if this comes again.
···
Sent from my iPhone
On 17-Nov-2016, at 12:57 AM, Michael Gottesman <mgottesman@apple.com> wrote:
Question. How did this get through PR testing?
Sent from my iPhone
On Nov 16, 2016, at 6:01 AM, Ankit Aggarwal via swift-dev <swift-dev@swift.org> wrote:
This is mine, checking.
On 16-Nov-2016, at 6:12 PM, no-reply@swift.org wrote:
On Nov 16, 2016, at 12:02 PM, ankit_aggarwal@apple.com wrote:
I figured this was a 16.10 issue because PR bot (16.04) passed, however I wasn't able to reproduce this locally after installing 16.10, I pushed a commit to pin point the failure line but that integration went fine. I will keep an eye if this comes again.
Sent from my iPhone
On 17-Nov-2016, at 12:57 AM, Michael Gottesman <mgottesman@apple.com <mailto:mgottesman@apple.com>> wrote:
Question. How did this get through PR testing?
Sent from my iPhone
On Nov 16, 2016, at 6:01 AM, Ankit Aggarwal via swift-dev <swift-dev@swift.org <mailto:swift-dev@swift.org>> wrote:
This is mine, checking.
On 16-Nov-2016, at 6:12 PM, no-reply@swift.org <mailto:no-reply@swift.org> wrote: