[swift-dev] Initial smoke test PR message confusion

Hey everyone. >From talking with various people I think there is some confusion around the >initial message shown in the PR test state when one creates a PR. >Specifically, initially the PR test state says something like this: This does not mean that tests have started to be run automatically

Re: [swift-dev] [Swift CI] Build Failure: OSS - Swift Package - Ubuntu 14.04 (master) #1804

Sorry for the delay. I can't see in the log what's causing the test command to fail (stdout and stderr are empty), so will need to get to the bottom of it before I reenable. Anders > On 2016-07-28, at 22.01, Michael Gottesman wrote: > > Thanks! I really appreciate it = ). > > Michael > >>

Re: [swift-dev] [Swift CI] Build Failure: OSS - Swift Package - Ubuntu 14.04 (master) #1804

Thanks! I really appreciate it = ). Michael > On Jul 28, 2016, at 9:51 PM, Anders Bertelrud wrote: > > Pushed a revert until I can figure out why it isn't working. > > Anders > >> On 2016-07-28, at 21.42, Michael Gottesman > > wrote: >> >> Can you revert? This is

Re: [swift-dev] [Swift CI] Build Failure: OSS - Swift Package - Ubuntu 14.04 (master) #1804

Pushed a revert until I can figure out why it isn't working. Anders > On 2016-07-28, at 21.42, Michael Gottesman wrote: > > Can you revert? This is making the linux smoke tests fail. > > Michael > >> On Jul 28, 2016, at 6:58 PM, Anders Bertelrud via swift-dev >> mailto:swift-dev@swift.org>>

Re: [swift-dev] [Swift CI] Build Failure: OSS - Swift Package - Ubuntu 14.04 (master) #1804

Can you revert? This is making the linux smoke tests fail. Michael > On Jul 28, 2016, at 6:58 PM, Anders Bertelrud via swift-dev > wrote: > > I am investigating why 6f0b1047d51e6260967ad06e9ded1fa905d508f4 doesn't seem > to have fixed this. > > Anders > > On Jul 28, 2016, at 18:30, no-re...

[swift-dev] Anyone fixing TestNSJSONSerialization?

Is anyone looking at this failure that’s blocking CI? https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-14_04/6576/ TestFoundation/TestNSJSONSerialization.swift:301: error: TestNSJSONSerialization.test_deserialize_unicodeEscapeSequence : XCTAssertEqual failed: ("Optional("✨")") i

Re: [swift-dev] [Swift CI] Build Failure: OSS - Swift Package - Ubuntu 14.04 (master) #1804

I am investigating why 6f0b1047d51e6260967ad06e9ded1fa905d508f4 doesn't seem to have fixed this. Anders > On Jul 28, 2016, at 18:30, no-re...@swift.org wrote: > > [FAILURE] oss-swift-package-linux-ubuntu-14_04 [#1804] > > Build URL: > https://ci.swift.org/job/oss-swift-package-linux-ubuntu

Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift Incremental RA - OS X (master) #5558

Cool, thanks for confirming! Anders > On Jul 28, 2016, at 17:34, Mishal Shah wrote: > > Yes, next build should pick up the changes from > https://github.com/apple/swift-xcode-playground-support/pull/6 > > Thanks, > Mishal Shah >> On Jul 28, 2016, at 5:32 PM, Anders Bertelrud wrote: >> >> T

Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift Incremental RA - OS X (master) #5558

Yes, next build should pick up the changes from https://github.com/apple/swift-xcode-playground-support/pull/6 Thanks, Mishal Shah > On Jul 28, 2016, at 5:32 PM, Anders Bertelrud wrote: > > This fails due to the updates for SE-0089. Perhaps the necessary support has > not yet been merged int

Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift Incremental RA - OS X (master) #5558

This fails due to the updates for SE-0089. Perhaps the necessary support has not yet been merged into the compiler? Anders > On 2016-07-28, at 17.27, no-re...@swift.org wrote: > > [FAILURE] oss-swift-incremental-RA-osx [#5558] > > Build URL:https://ci.swift.org/job/oss-swift-incremental-R

Re: [swift-dev] [Swift CI] Build Failure: OSS - Swift Package - Ubuntu 15.10 (master) #1793

This has already been fixed in: https://github.com/apple/swift-integration-tests/commit/6f0b1047d51e6260967ad06e9ded1fa905d508f4 Anders > On 2016-07-28, at 16.41, no-re...@swift.org wrote: > > [FAILURE] oss-swift-package-linux-ubuntu-15_10 [#1793] > > Build URL: > https://ci.swift.org/job/

[swift-dev] SE-0042: Flattening the function type of unapplied method references

Hi everyone, I have an implementation for SE-0042 ready: https://github.com/apple/swift/pull/3836 . Janek signature.asc Description: Message signed with OpenPGP using GPGMail ___ swift-dev mailing list swift-dev@swift.org https://lists.swift.org/mail

Re: [swift-dev] Anyone running build-toolchain on linux?

Thanks Ben. Daniel’s command works for me: build-script -R --llbuild --foundation --xctest -t But doesn’t build all the projects. -Andy > On Jul 28, 2016, at 9:39 AM, Ben Langmuir wrote: > > That error indicates some kind of filesystem issue in the module cache > directory - no permissions,

Re: [swift-dev] Anyone running build-toolchain on linux?

That error indicates some kind of filesystem issue in the module cache directory - no permissions, out of space, the directory has been removed by some other process, etc. +Bruno who was looking at making this error more specific. Ben > On Jul 28, 2016, at 9:29 AM, Daniel Dunbar wrote: > >

Re: [swift-dev] Anyone running build-toolchain on linux?

I don't run build toolchain myself (I have my own scripts for assembling one), but I run `build-script -R --llbuild --foundation --xctest -t` without issue. +Jordan, Ben for what situations could cause the actual error we are hitting there. - Daniel > On Jul 28, 2016, at 9:27 AM, Andrew Trick

[swift-dev] Anyone running build-toolchain on linux?

I need to push corelibs changes in today but I’m running into problems testing the full Swift toolchain on linux. build-toolchain stops after attempting to run swiftpm tests and hitting the failure shown below. Anyone else seeing issues running build-toolchain? As of: commit cb0b4588a6a8bf80dc

[swift-dev] [SE-0134] Source-breaking proposal implementation

PRs: apple/swift#3816 and apple/swift-corelibs-foundation#486 Thanks, Xiaodi ___ swift-dev mailing list swift-dev@swift.org https://lists.swift.org/mailman/listinfo/swift-dev

[swift-dev] CI Update: Bots are blue, master is unlocked!

Hello All- I am happy to announce that all CI failures on master have been resolved, and we have unlocked master. In order to keep master healthy in this critical time as the last few source-breaking changes land, we’re going to require that changes be landed via pull request for the next 24 h