[swift-dev] [Swift CI] Build Still Failing: 1. OSS - Swift (Tools Opt+Assert, Stdlib Opt+DebInfo+Assert, Resilience) - macOS (master) #209

2017-05-24 Thread no-reply--- via swift-dev
New issue found!Title: Report [FAILURE] oss-swift_tools-RA_stdlib-RDA_test-macos-resilience [#209] Build URL:https://ci.swift.org/job/oss-swift_tools-RA_stdlib-RDA_test-macos-resilience/209/ Project:oss-swift_tools-RA_stdlib-RDA_test-macos-resilience Date of build:Wed, 24 May

Re: [swift-dev] [Swift CI] Build Failure: OSS - Swift Package - Ubuntu 16.04 (swift 3.1) #584

2017-05-24 Thread Joe Shajrawi via swift-dev
Test time out: TestFoundation/TestProgress.swift:374: error: TestProgress.test_handlers : XCTAssertEqual failed: ("success") is not equal to ("timedOut") - TestFoundation/TestProgress.swift:375: error: TestProgress.test_handlers : XCTAssertEqual failed: ("success") is not equal to ("timedOut") -

Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift Incremental RA - Ubuntu 16.10 (master) #3881

2017-05-24 Thread Joe Shajrawi via swift-dev
terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc Regards, —Joe |  | 📧 shajr...@apple.com | 📱(+1) 408-930-5203 > On May 24, 2017, at 19:50, no-re...@swift.org wrote: > > [FAILURE] oss-swift-incremental-RA-linux-ubuntu-16_1

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

2017-05-24 Thread Joe Shajrawi via swift-dev
Dave, this appears to have been caused by your commit: /Users/buildnode/jenkins/workspace/oss-swift-incremental-RA-osx/swift/benchmark/utils/main.swift:233:69: error: use of unresolved identifier 'run_EqualStringSubstringGenericStringProtocol' Regards, —Joe |  | 📧 shajr...@apple.com

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

2017-05-24 Thread Joe Shajrawi via swift-dev
Reverted https://github.com/apple/swift/pull/9922 Regards, —Joe |  | 📧 shajr...@apple.com | 📱(+1) 408-930-5203 > On May 24, 2017, at 20:09, Joe Shajrawi wrote: > > Dave, this appears to have been caused by your commit