The test was added by PR #1186. Copying Johannes.Pushkar N Kulkarni,
IBM RuntimesSimplicity is prerequisite for reliability - Edsger W. Dijkstra
-swift-dev-boun...@swift.org wrote: -To: h...@bubski.plFrom: Michael Ilseman via swift-dev Sent by: swift-dev-boun...@swift.orgDate: 08/31/2017 03
,>> IBM Runtimes>> >> Simplicity is prerequisite for reliability - Edsger W. Dijkstra>> >> >> >> -swift-dev-boun...@swift.org wrote: ->> To: John McCall <rjmcc...@apple.com>>> From: Pushkar N Kulkarni via swift-dev >> Sent by: swif
Over the past few months, we've seen random and intermittent failures in the URLSession tests in TestFoundation in the CI builds running on Ubuntu 16.04. Surprisingly, these failures never occur on PR builds. We've tried to reproduce them locally (on matching Ubuntu levels) and fixed locally observ
Hi Michael,Mamatha and I had a look at the build log. The failure doesn't seem to be related to the URLSession changes. Pushkar N Kulkarni,
IBM RuntimesSimplicity is prerequisite for reliability - Edsger W. Dijkstra
-milse...@apple.com wrote: -To: swift-dev@swift.orgFrom: Michael Ilseman Se
ger W. Dijkstra
-swift-dev-boun...@swift.org wrote: -To: Michael Ilseman <milse...@apple.com>From: Pushkar N Kulkarni via swift-dev Sent by: swift-dev-boun...@swift.orgDate: 05/17/2017 04:02PMCc: swift-dev <swift-dev@swift.org>Subject: Re: [swift-dev] [Swift CI] Build Still Failin
We've never seen this failure, but I can't rule out the possibility of this originating in the URLSession tests. Though 2 out of 13 CI builds failed in URLSession yesterday, these failures are really intermittent. I am unable to reproduce them locally even after running TestFoundation in a loop for
. Dijkstra
-swift-dev-boun...@swift.org wrote: -To: Michael Ilseman <milse...@apple.com>From: Pushkar N Kulkarni via swift-dev Sent by: swift-dev-boun...@swift.orgDate: 05/17/2017 12:29AMCc: xe...@apache.org, swift-dev@swift.orgSubject: Re: [swift-dev] [Swift CI] Build Failure:
This is related to a4497372448ed388d507028b7d7a68fc333a491c on corelibs-foundation. We enabled the tests after a long time today, along with a work around that was expected to fix these problems. Looks like it hasn't. I am going to disable this particular test for now. If failures are seen in othe
ility - Edsger W. Dijkstra
-swift-dev-boun...@swift.org wrote: -To: John McCall <rjmcc...@apple.com>From: Pushkar N Kulkarni via swift-dev Sent by: swift-dev-boun...@swift.orgDate: 05/10/2017 06:00PMCc: swift-dev <swift-dev@swift.org>Subject: Re: [swift-dev] Property modifi
v@swift.org>Subject: Re: [swift-dev] Property modification not taking effectOn May 9, 2017, at 3:07 PM, Pushkar N Kulkarni via swift-dev <swift-dev@swift.org> wrote:In the process of debugging a bunch of consistent failures in TestFoundation/TestNSURLSession, I came across a weird problem
In the process of debugging a bunch of consistent failures in TestFoundation/TestNSURLSession, I came across a weird problem symptom in this line of code.internalState = .transferInProgress(transferState)I had a suspicion that the above modification is not taking effect, since, only based on this c
Hi there, I see a new warning message for switch statements on enums, like this one: enum Test { case one(Any) case two}let x: Test = .one("One")switch x { case .one(let s as String): print(s) case .one: break case .two: break}enum.swift:9:10: warning: case is already handled by prev
e for reliability - Edsger W. Dijkstra
-swift-dev-boun...@swift.org wrote: -To: "swift-dev" <swift-dev@swift.org>From: Pushkar N Kulkarni via swift-dev Sent by: swift-dev-boun...@swift.orgDate: 04/21/2017 05:34PMSubject: [swift-dev] Fw: [Swift CI] Build Failure: OSS - Swift P
TestNSURLSession seems to have become very brittle. This failure is different from https://bugs.swift.org/browse/SR-4647I've done basic analysis of SR-4647 and right now it is difficult to suspect any particular commit.I think we should disable NSURLSession tests for a while until we have some clue
This failure has been coming up very intermittently for a while when running TestFoundation locally.Though we have a new commit in URLSession (015ded4d70a7cf4b2741d7206fc60a3d1ceffe03), I don't think that change can trigger this failure. Nevertheless, I'll try to reproduce it locally and investigat
the other builds are using stable, rather than master, for the swift-lldb checkout.https://lists.swift.org/pipermail/swift-users/Week-of-Mon-20170220/004803.htmlAlexOn 21 Feb 2017, at 14:33, Pushkar N Kulkarni via swift-dev <swift-dev@swift.org> wrote:Hi there, Am I the only one seeing this b
Hi there, Am I the only one seeing this build error with all the repos on their latest masters? I tried doing a clean build too. Here's the error message: /home/pushkar/swift/lldb/source/Symbol/SwiftASTContext.cpp:3181:22: error: no viable conversion from 'swift::SearchPathOptions::FrameworkSearchP
Hello,A colleague of mine who's doing performance testing with some server-side Swift frameworks like Kitura, Perfect and Zewo found a 15-20% degradation with a simple "Hello World" benchmark, with the 3.0.1 previews on Linux. Analysis revealed it is related to the disabling of an optimisation arou
FYI. I came across this libkqueue test failure in a PR test today. https://ci.swift.org/job/swift-corelibs-foundation-PR-Linux/389/consoleFAIL: kqtest
bind-1: Address already in use
Running 1 iterations
1: test_peer_close_detection()
2: test_kqueue()
3: test_kevent()
Only the download task tests are disabled. And this is the second time we are seeing this data task test timing out. I'd be glad to get more reviews and suggestions on: https://github.com/apple/swift-corelibs-foundation/pull/613 to have loopback tests replace these tests with external URL. Thanks.P
I've just started working on loopback tests with a simple in-process http server, for URLSession. Pushkar N Kulkarni,
IBM RuntimesSimplicity is prerequisite for reliability - Edsger W. Dijkstra
-swift-dev-boun...@swift.org wrote: -To: Philippe Hausler From: Tony Parker v
Hello, I tried to implement NSOrderedSet.reversedOrderSet with this code:/*@NSCopying*/ public var reversedOrderedSet: NSOrderedSet { return NSOrderedSet.init(array: _orderedStorage.reversed())}I'm not sure about the correctness/performance of that implementation, but I see a crash while bui
22 matches
Mail list logo