Re: [swift-corelibs-dev] I ve found a serious Bug in JSONEncoder (SR-6131) and would like to fix it.

(moving to more relevant list) > On Dec 18, 2017, at 08:51, Benoit Pereira da silva via swift-users > wrote: > > Dear all > > I've found a serious Bug in JSONEncoder SR-6131 > and would like to fix it. > This bug cause JSON

Re: [swift-corelibs-dev] [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift Incremental RA - Ubuntu 16.04 - Long Test (master) #485

> On Oct 24, 2017, at 16:30, Slava Pestov via swift-dev > wrote: > > >> On Oct 24, 2017, at 4:26 PM, Xi Ge via swift-dev > > wrote: >> >> This could be due to one of the following commit. Could someone shed some >>

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

Foundation folks, have you seen this before? TestFoundation/TestNSAffineTransform.swift:187: error: TestNSAffineTransform.test_Rotation_Radians : XCTAssertEqualWithAccuracy failed: ("10.0") is not equal to ("-10.0") +/- ("0.001") - y (expected: -10.0, was: 10.0): Jordan > On Feb 20, 2017,

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

None of these changes would have affected the failing XCTest test. Adding swift-corelibs-dev. https://ci.swift.org//job/oss-swift-incremental-RA-linux-ubuntu-14_04/775/consoleFull#-936285465fca400bf-2f4a-462e-b517-e058d770b2d7 > *** Error in >

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

Adding swift-corelibs-dev, since that’s where the Dispatch folks hang out. > On Nov 2, 2016, at 10:44, Doug Coleman via swift-dev > wrote: > > https://bugs.swift.org/browse/SR-2931 > > >> On Nov 2, 2016, at 10:43 AM,

Re: [swift-corelibs-dev] [swift-dev] Swift Class Encoding Standard?

This is somewhat intentional. While simple names can be encoded hierarchically like this, generics make everything more tricky. Consider a demangled name "Contacts.Person.Address.PostCode"—in this case not only is splitting on "." is no longer a reasonable thing to do, but there's not

Re: [swift-corelibs-dev] [swift-dev] Swift CI PR builder dispatch linux failure

Oh, I didn’t realize we had a separate copy of the overlay code (almost certainly the right thing to do at this point). But in that case, why are we seeing any of these errors? Jordan > On Sep 25, 2016, at 11:38, David P Grove wrote: > > The order may need to vary by

[swift-corelibs-dev] Flaky NSOperationQueue test

Anyone know what’s up with this one? We get it every few builds or so. 17:15:39 TestFoundation/TestNSOperationQueue.swift:63: error: TestNSOperationQueue.test_OperationPriorities : XCTAssertEqual failed: ("Operation1 executed") is not equal to ("Operation3 executed") - 17:15:39

[swift-corelibs-dev] Mailing list flakiness

Hey, all. You might have noticed messages being dropped or taking a long time to get through on the swift.org mailing lists. The story is that the configuration for our outbound mail server changed on Tuesday, but we didn't get around to updating it until Wednesday. We think the system is just

[swift-corelibs-dev] Fwd: [swift-users] [swift-dev] New Swift Snapshots Available!

> Begin forwarded message: > > From: Michael Ferenduros via swift-users > Subject: Re: [swift-users] [swift-dev] New Swift Snapshots Available! > Date: August 26, 2016 at 08:00:55 PDT > To: swift-us...@swift.org > Reply-To: Michael Ferenduros

Re: [swift-corelibs-dev] [Swift CI] Build Failure: 0. OSS - Swift libdispatch Incremental RA - Ubuntu 14.04 (master) #183

Not it. Dispatch folks, any idea what's up? > On Aug 24, 2016, at 16:04, no-re...@swift.org wrote: > > [FAILURE] oss-swift-incremental-RA-libdispatch-linux-ubuntu-14_04 [#183] > > Build URL: > https://ci.swift.org/job/oss-swift-incremental-RA-libdispatch-linux-ubuntu-14_04/183/ > >

Re: [swift-corelibs-dev] [swift-build-dev] JIRA workflow: "Resolved" -> "Verify"?

It hasn’t been used so much so far, but on the bugs where it has I like being able to tell the difference. I don’t think we’d poke people about verification like we do with Radar, though, so we will (and have) end up with a lot of bugs left in Resolved/Verify. Jordan > On Aug 15, 2016, at

[swift-corelibs-dev] JIRA workflow: "Resolved" -> "Verify"?

Hi, swift-dev et al (but especially Ted). I’ve recently noticed that our JIRA workflow has been a bit confusing. We currently have five “statuses": 1. Opened: This bug has been filed. 2. In Progress: Someone is actively working on this bug. (Not everyone has been bothering to set this, but it

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

[+swift-corelibs-dev] I don't think Foundation even tries to do incremental builds. I wonder if XCTest.so needs to be marked as a dependency somewhere in the higher-level build system. Jordan > On May 12, 2016, at 15:52, Brian Croom wrote: > > I'm not sure where the

Re: [swift-corelibs-dev] Foundation and explicit pointer nullability (CI edition)

tomorrow with any new developments. Jordan > On Apr 11, 2016, at 12:23 , Jordan Rose via swift-corelibs-dev > <swift-corelibs-dev@swift.org> wrote: > > Hi, swift-corelibs-dev. I'm planning to land the changes for SE-0055: Making > pointer nullability explicit > <htt

Re: [swift-corelibs-dev] [swift-users] build libdispatch failed in ubuntu 14.04

(adding swift-corelibs-dev for additional eyes) > On Mar 29, 2016, at 7:25 , qibo via swift-users wrote: > > Hi, everyone > I follow the command written in INSTALL in > https://github.com/apple/swift-corelibs-libdispatch/blob/master/INSTALL >

Re: [swift-corelibs-dev] Defining _GNU_SOURCE for module-map-included headers

Hm. If this is the right setting to set on everybody's system, we could add it as part of Clang initialization (for the Clang inside Swift). Otherwise, you can use "-Xcc" to pass extra flags to Clang, in this case "-Xcc -D_GNU_SOURCE=1". Hope that helps, Jordan > On Dec 20, 2015, at 2:29 ,