Build Failures for Swift Repos

New failures in trying to build Swift from the repos:

TestFoundation/TestNSAffineTransform.swift:26:7: error: type
'TestNSAffineTransform' does not conform to protocol 'XCTestCaseProvider'
class TestNSAffineTransform : XCTestCase {
      ^
XCTest.XCTestCaseProvider:2:16: note: protocol requires property 'allTests'
with type '[(String, () throws -> Void)]'
    public var allTests: [(String, () throws -> Void)] { get }
               ^
TestFoundation/TestNSAffineTransform.swift:29:9: note: candidate has
non-matching type '[(String, () -> Void)]'
    var allTests : [(String, () -> Void)] {
        ^
TestFoundation/TestNSArray.swift:22:7: error: type 'TestNSArray' does not
conform to protocol 'XCTestCaseProvider'
class TestNSArray : XCTestCase {

swift swiftrevs.swift
swift:52a46d036d
llvm:3ebdbb2c7e
clang:f66c5bb67b
lldb:e6ab0bee64
cmark:5af77f3c1d
llbuild:97311cc774
swiftpm:fe7a21c459
swift-corelibs-xctest:01315bcfe2
swift-corelibs-foundation:1ae52803eb
swift-integration-tests:bade6e5395

So, I don't want to spam the mailing list if its inappropriate, and there's
no expectation that the system always builds, so if this is noise please
let me know. I'm just raising it because I'd like to build everything to
create Ubuntu packages. I can always go off of a tag if folks think that
would be a better approach.

Joe

···

--
---

@iachievedit

Feel free to continue reporting problems on this list. We have automated builders internally, but problems uncovered there aren't always addressed promptly. You will need to specify the OS version that you are trying to build for, though.

For building packages you may want to stick with the "snapshot" tags. Those tags are used to build the packages at swift.org/download/. They are known to build cleanly and run the automated tests on the supported OS versions so they ought to be more likely to work.

···

On Jan 15, 2016, at 5:18 PM, Joseph Bell via swift-dev <swift-dev@swift.org> wrote:

So, I don't want to spam the mailing list if its inappropriate, and there's no expectation that the system always builds, so if this is noise please let me know. I'm just raising it because I'd like to build everything to create Ubuntu packages. I can always go off of a tag if folks think that would be a better approach.

--
Greg Parker gparker@apple.com Runtime Wrangler

Thanks Greg. I am building for Ubuntu 14.04 at the moment and typically
have identical trees checked out for 14.04, 15.10, and another tree for
building 2.2 on a BeagleBoard X15 for the ARM packages. The ARM tree
contains repos from hpux735 while work is being done there for ARMv7.

I try to keep all 3 aligned as much as possible so frequently just try to
build against HEAD on all repos.

I understand things are being churned at the moment so will keep updating
until I get a good state or catch the edge of a snapshot tag being released.

Joe

···

On Fri, Jan 15, 2016 at 10:00 PM, Greg Parker <gparker@apple.com> wrote:

> On Jan 15, 2016, at 5:18 PM, Joseph Bell via swift-dev < > swift-dev@swift.org> wrote:
>
> So, I don't want to spam the mailing list if its inappropriate, and
there's no expectation that the system always builds, so if this is noise
please let me know. I'm just raising it because I'd like to build
everything to create Ubuntu packages. I can always go off of a tag if
folks think that would be a better approach.

Feel free to continue reporting problems on this list. We have automated
builders internally, but problems uncovered there aren't always addressed
promptly. You will need to specify the OS version that you are trying to
build for, though.

For building packages you may want to stick with the "snapshot" tags.
Those tags are used to build the packages at swift.org/download/. They
are known to build cleanly and run the automated tests on the supported OS
versions so they ought to be more likely to work.

--
Greg Parker gparker@apple.com Runtime Wrangler

--
---
http://dev.iachieved.it/iachievedit/
@iachievedit