[swift-dev] [Swift CI] Build Failure: OSS - Swift Package - OS X (swift 4.1) #477

Title: Report [FAILURE] oss-swift-4.1-package-osx [#477] Build URL:https://ci.swift.org/job/oss-swift-4.1-package-osx/477/ Project:oss-swift-4.1-package-osx Date of build:Wed, 03 Jan 2018 11:59:16 -0600 Build duration:4 hr 18 min Changes Commit 08

Re: [swift-dev] [Swift CI] Build Failure: 2. Swift Source Compatibility Suite (master) #1014

Vedant, this appears to be a result of your changes. I’ve opened https://github.com/apple/swift/pull/13709 to revert the later clean-up change which appears to be required before it will be possible to revert the change below. Mark > On Jan 3, 2018,

Re: [swift-dev] [Swift CI] Build Failure: 2. Swift Source Compatibility Suite (master) #1014

This is a bit surprising, since I wouldn't expect this suite of tests to stress the code coverage logic. How were you able to determine that the #13597 caused the break? I'm having a hard time understanding what the logs mean. For example, I see this failure, but I'm not sure how my change rela

Re: [swift-dev] [Swift CI] Build Failure: 2. Swift Source Compatibility Suite (master) #1014

> On Jan 3, 2018, at 7:18 PM, Vedant Kumar wrote: > > This is a bit surprising, since I wouldn't expect this suite of tests to > stress the code coverage logic. > > How were you able to determine that the #13597 caused the break? I’m seeing this in the failing builds: Assertion failed: (std

Re: [swift-dev] [Swift CI] Build Failure: 2. Swift Source Compatibility Suite (master) #1014

> On Jan 3, 2018, at 7:23 PM, Mark Lacey wrote: > > > >> On Jan 3, 2018, at 7:18 PM, Vedant Kumar > > wrote: >> >> This is a bit surprising, since I wouldn't expect this suite of tests to >> stress the code coverage logic. >> >> How were you able to determine that the

Re: [swift-dev] [Swift CI] Build Failure: 2. Swift Source Compatibility Suite (master) #1014

> On Jan 3, 2018, at 7:31 PM, Vedant Kumar wrote: > >> >> On Jan 3, 2018, at 7:23 PM, Mark Lacey > > wrote: >> >> >> >>> On Jan 3, 2018, at 7:18 PM, Vedant Kumar >> > wrote: >>> >>> This is a bit surprising, since I wouldn't expect this s

Re: [swift-dev] [Swift CI] Build Failure: 2. Swift Source Compatibility Suite (master) #1014

> On Jan 3, 2018, at 7:34 PM, Mark Lacey wrote: > > > >> On Jan 3, 2018, at 7:31 PM, Vedant Kumar > > wrote: >> >>> >>> On Jan 3, 2018, at 7:23 PM, Mark Lacey >> > wrote: >>> >>> >>> On Jan 3, 2018, at 7:18 PM, Vedant Kumar >>>

Re: [swift-dev] [Swift CI] Build Failure: 2. Swift Source Compatibility Suite (master) #1014

> On Jan 3, 2018, at 7:36 PM, Vedant Kumar wrote: > >> >> On Jan 3, 2018, at 7:34 PM, Mark Lacey > > wrote: >> >> >> >>> On Jan 3, 2018, at 7:31 PM, Vedant Kumar >> > wrote: >>> On Jan 3, 2018, at 7:23 PM, Mark Lacey >>>

Re: [swift-dev] [Swift CI] Build Failure: 2. Swift Source Compatibility Suite (master) #1014

> On Jan 3, 2018, at 7:46 PM, Slava Pestov wrote: > > > >> On Jan 3, 2018, at 7:36 PM, Vedant Kumar > > wrote: >> >>> >>> On Jan 3, 2018, at 7:34 PM, Mark Lacey >> > wrote: >>> >>> >>> On Jan 3, 2018, at 7:31 PM, Vedant Kumar >>>

Re: [swift-dev] [swift-lldb-dev] Switching swift to C++14

I’m pinging some folks, but not everybody is back yet. I hope to resolve this ASAP. > On Jan 2, 2018, at 11:33 AM, Saleem Abdulrasool wrote: > >> On Wed, Dec 20, 2017 at 4:26 PM, Ted Kremenek wrote: >> >>> On Dec 19, 2017, 8:33 PM -0800, Ted Kremenek via swift-dev >>> , wrote: >>> >>> >>>