These are failing in SwiftPM; and not related to these commits. Did our Foundation get out of sync from SwiftPM?
/Users/buildnode/jenkins/workspace/oss-swift-incremental-RA-osx/swiftpm/Sources/Basic/Lock.swift:11:14: error: no such decl in module
import class Foundation.Lock
^ ~~~~
···
On Jul 15, 2016, at 10:28 AM, no-reply@swift.org wrote:
That's a surprising failure. The renaming of NSLock to Lock happened some time ago, and AFAIK the SwiftPM side of this code hasn't changed for a long time.
Because of the other CI problems, many of them haven't been able to progress as far as SwiftPM, so I don't know if this is a new issue. But since it is OS X, it should be using the Darwin Foundation and not the open source one, correct?
Anders
···
On 2016-07-15, at 10.31, Ben Langmuir <blangmuir@apple.com> wrote:
These are failing in SwiftPM; and not related to these commits. Did our Foundation get out of sync from SwiftPM?
/Users/buildnode/jenkins/workspace/oss-swift-incremental-RA-osx/swiftpm/Sources/Basic/Lock.swift:11:14: error: no such decl in module
import class Foundation.Lock
^ ~~~~
On Jul 15, 2016, at 10:28 AM, no-reply@swift.org <mailto:no-reply@swift.org> wrote:
On Jul 15, 2016, at 10:31 AM, Ben Langmuir via swift-dev <swift-dev@swift.org> wrote:
These are failing in SwiftPM; and not related to these commits. Did our Foundation get out of sync from SwiftPM?
/Users/buildnode/jenkins/workspace/oss-swift-incremental-RA-osx/swiftpm/Sources/Basic/Lock.swift:11:14: error: no such decl in module
import class Foundation.Lock
^ ~~~~
On Jul 15, 2016, at 10:28 AM, no-reply@swift.org <mailto:no-reply@swift.org> wrote:
On Jul 15, 2016, at 10:34 AM, Anders Bertelrud via swift-dev <swift-dev@swift.org> wrote:
That's a surprising failure. The renaming of NSLock to Lock happened some time ago, and AFAIK the SwiftPM side of this code hasn't changed for a long time.
Because of the other CI problems, many of them haven't been able to progress as far as SwiftPM, so I don't know if this is a new issue. But since it is OS X, it should be using the Darwin Foundation and not the open source one, correct?
Anders
On 2016-07-15, at 10.31, Ben Langmuir <blangmuir@apple.com <mailto:blangmuir@apple.com>> wrote:
These are failing in SwiftPM; and not related to these commits. Did our Foundation get out of sync from SwiftPM?
/Users/buildnode/jenkins/workspace/oss-swift-incremental-RA-osx/swiftpm/Sources/Basic/Lock.swift:11:14: error: no such decl in module
import class Foundation.Lock
^ ~~~~
On Jul 15, 2016, at 10:28 AM, no-reply@swift.org <mailto:no-reply@swift.org> wrote:
Is there a reason why a full toolchain build didn’t pick this up? It seems that when I built locally everything built just fine and tested ok. My configuration that I use to test is a build bot preset that I have modified to have specific destinations such that I can automate installing it.
I was under the impression that it built swiftpm by default.
···
On Jul 15, 2016, at 4:06 PM, Philippe Hausler via swift-dev <swift-dev@swift.org> wrote:
NSLock got renamed back to include it’s NS.
On Jul 15, 2016, at 10:31 AM, Ben Langmuir via swift-dev <swift-dev@swift.org <mailto:swift-dev@swift.org>> wrote:
These are failing in SwiftPM; and not related to these commits. Did our Foundation get out of sync from SwiftPM?
/Users/buildnode/jenkins/workspace/oss-swift-incremental-RA-osx/swiftpm/Sources/Basic/Lock.swift:11:14: error: no such decl in module
import class Foundation.Lock
^ ~~~~
On Jul 15, 2016, at 10:28 AM, no-reply@swift.org <mailto:no-reply@swift.org> wrote:
On Jul 15, 2016, at 10:35 AM, Daniel Dunbar <daniel_dunbar@apple.com> wrote:
Some of the prefixes are coming back.
- Daniel
On Jul 15, 2016, at 10:34 AM, Anders Bertelrud via swift-dev <swift-dev@swift.org <mailto:swift-dev@swift.org>> wrote:
That's a surprising failure. The renaming of NSLock to Lock happened some time ago, and AFAIK the SwiftPM side of this code hasn't changed for a long time.
Because of the other CI problems, many of them haven't been able to progress as far as SwiftPM, so I don't know if this is a new issue. But since it is OS X, it should be using the Darwin Foundation and not the open source one, correct?
Anders
On 2016-07-15, at 10.31, Ben Langmuir <blangmuir@apple.com <mailto:blangmuir@apple.com>> wrote:
These are failing in SwiftPM; and not related to these commits. Did our Foundation get out of sync from SwiftPM?
/Users/buildnode/jenkins/workspace/oss-swift-incremental-RA-osx/swiftpm/Sources/Basic/Lock.swift:11:14: error: no such decl in module
import class Foundation.Lock
^ ~~~~
On Jul 15, 2016, at 10:28 AM, no-reply@swift.org <mailto:no-reply@swift.org> wrote:
Is there a reason why a full toolchain build didn’t pick this up? It seems that when I built locally everything built just fine and tested ok. My configuration that I use to test is a build bot preset that I have modified to have specific destinations such that I can automate installing it.
I was under the impression that it built swiftpm by default.
I would have expected the buildbot config to, but I don't use the presets myself. Passing `--swiftpm` to the build script definitely should.
On a related topic, it would be *very* helpful to us if changes like this could land concurrently with the matching support going in on the Linux side, to avoid having to add platform specific shims.
- Daniel
···
On Jul 15, 2016, at 4:10 PM, Philippe Hausler via swift-dev <swift-dev@swift.org> wrote:
On Jul 15, 2016, at 4:06 PM, Philippe Hausler via swift-dev <swift-dev@swift.org <mailto:swift-dev@swift.org>> wrote:
NSLock got renamed back to include it’s NS.
On Jul 15, 2016, at 10:31 AM, Ben Langmuir via swift-dev <swift-dev@swift.org <mailto:swift-dev@swift.org>> wrote:
These are failing in SwiftPM; and not related to these commits. Did our Foundation get out of sync from SwiftPM?
/Users/buildnode/jenkins/workspace/oss-swift-incremental-RA-osx/swiftpm/Sources/Basic/Lock.swift:11:14: error: no such decl in module
import class Foundation.Lock
^ ~~~~
On Jul 15, 2016, at 10:28 AM, no-reply@swift.org <mailto:no-reply@swift.org> wrote:
On Jul 15, 2016, at 10:35 AM, Daniel Dunbar <daniel_dunbar@apple.com <mailto:daniel_dunbar@apple.com>> wrote:
Some of the prefixes are coming back.
- Daniel
On Jul 15, 2016, at 10:34 AM, Anders Bertelrud via swift-dev <swift-dev@swift.org <mailto:swift-dev@swift.org>> wrote:
That's a surprising failure. The renaming of NSLock to Lock happened some time ago, and AFAIK the SwiftPM side of this code hasn't changed for a long time.
Because of the other CI problems, many of them haven't been able to progress as far as SwiftPM, so I don't know if this is a new issue. But since it is OS X, it should be using the Darwin Foundation and not the open source one, correct?
Anders
On 2016-07-15, at 10.31, Ben Langmuir <blangmuir@apple.com <mailto:blangmuir@apple.com>> wrote:
These are failing in SwiftPM; and not related to these commits. Did our Foundation get out of sync from SwiftPM?
/Users/buildnode/jenkins/workspace/oss-swift-incremental-RA-osx/swiftpm/Sources/Basic/Lock.swift:11:14: error: no such decl in module
import class Foundation.Lock
^ ~~~~
On Jul 15, 2016, at 10:28 AM, no-reply@swift.org <mailto:no-reply@swift.org> wrote:
On Jul 15, 2016, at 10:35 AM, Daniel Dunbar <daniel_dunbar@apple.com <mailto:daniel_dunbar@apple.com>> wrote:
Some of the prefixes are coming back.
- Daniel
On Jul 15, 2016, at 10:34 AM, Anders Bertelrud via swift-dev <swift-dev@swift.org <mailto:swift-dev@swift.org>> wrote:
That's a surprising failure. The renaming of NSLock to Lock happened some time ago, and AFAIK the SwiftPM side of this code hasn't changed for a long time.
Because of the other CI problems, many of them haven't been able to progress as far as SwiftPM, so I don't know if this is a new issue. But since it is OS X, it should be using the Darwin Foundation and not the open source one, correct?
Anders
On 2016-07-15, at 10.31, Ben Langmuir <blangmuir@apple.com <mailto:blangmuir@apple.com>> wrote:
These are failing in SwiftPM; and not related to these commits. Did our Foundation get out of sync from SwiftPM?
/Users/buildnode/jenkins/workspace/oss-swift-incremental-RA-osx/swiftpm/Sources/Basic/Lock.swift:11:14: error: no such decl in module
import class Foundation.Lock
^ ~~~~
On Jul 15, 2016, at 10:28 AM, no-reply@swift.org <mailto:no-reply@swift.org> wrote:
I am working on getting those changes in today for swift-corelibs-foundation, along with some of the new value types.
···
On Jul 18, 2016, at 10:42 AM, Daniel Dunbar <daniel_dunbar@apple.com> wrote:
On Jul 15, 2016, at 4:10 PM, Philippe Hausler via swift-dev <swift-dev@swift.org <mailto:swift-dev@swift.org>> wrote:
Hmm that was incomplete:
Is there a reason why a full toolchain build didn’t pick this up? It seems that when I built locally everything built just fine and tested ok. My configuration that I use to test is a build bot preset that I have modified to have specific destinations such that I can automate installing it.
I was under the impression that it built swiftpm by default.
I would have expected the buildbot config to, but I don't use the presets myself. Passing `--swiftpm` to the build script definitely should.
On a related topic, it would be *very* helpful to us if changes like this could land concurrently with the matching support going in on the Linux side, to avoid having to add platform specific shims.
- Daniel
On Jul 15, 2016, at 4:06 PM, Philippe Hausler via swift-dev <swift-dev@swift.org <mailto:swift-dev@swift.org>> wrote:
NSLock got renamed back to include it’s NS.
On Jul 15, 2016, at 10:31 AM, Ben Langmuir via swift-dev <swift-dev@swift.org <mailto:swift-dev@swift.org>> wrote:
These are failing in SwiftPM; and not related to these commits. Did our Foundation get out of sync from SwiftPM?
/Users/buildnode/jenkins/workspace/oss-swift-incremental-RA-osx/swiftpm/Sources/Basic/Lock.swift:11:14: error: no such decl in module
import class Foundation.Lock
^ ~~~~
On Jul 15, 2016, at 10:28 AM, no-reply@swift.org <mailto:no-reply@swift.org> wrote:
On Jul 15, 2016, at 10:35 AM, Daniel Dunbar <daniel_dunbar@apple.com <mailto:daniel_dunbar@apple.com>> wrote:
Some of the prefixes are coming back.
- Daniel
On Jul 15, 2016, at 10:34 AM, Anders Bertelrud via swift-dev <swift-dev@swift.org <mailto:swift-dev@swift.org>> wrote:
That's a surprising failure. The renaming of NSLock to Lock happened some time ago, and AFAIK the SwiftPM side of this code hasn't changed for a long time.
Because of the other CI problems, many of them haven't been able to progress as far as SwiftPM, so I don't know if this is a new issue. But since it is OS X, it should be using the Darwin Foundation and not the open source one, correct?
Anders
On 2016-07-15, at 10.31, Ben Langmuir <blangmuir@apple.com <mailto:blangmuir@apple.com>> wrote:
These are failing in SwiftPM; and not related to these commits. Did our Foundation get out of sync from SwiftPM?
/Users/buildnode/jenkins/workspace/oss-swift-incremental-RA-osx/swiftpm/Sources/Basic/Lock.swift:11:14: error: no such decl in module
import class Foundation.Lock
^ ~~~~
On Jul 15, 2016, at 10:28 AM, no-reply@swift.org <mailto:no-reply@swift.org> wrote: