At this point I believe merging corelibs-foundation#464 <https://github.com/apple/swift-corelibs-foundation/pull/464> is the last change remaining for swift#3637 <https://github.com/apple/swift/pull/3637> to build/test/merge successfully.
Jacob On Thu, Jul 21, 2016 at 4:16 PM, Jacob Bandes-Storch <jtban...@gmail.com> wrote: > Next, could someone take care of > https://github.com/apple/swift-package-manager/pull/519 ? > > Thanks in advance, > Jacob > > On Thu, Jul 21, 2016 at 2:47 PM, Jacob Bandes-Storch <jtban...@gmail.com> > wrote: > >> Just kidding, this is another instance of the same error. Will require a >> separate fix. >> >> On Thu, Jul 21, 2016 at 2:45 PM, Jacob Bandes-Storch <jtban...@gmail.com> >> wrote: >> >>> Is there something special I need to do to make CI automatically use the >>> latest commits from swift-package-manager and swift-corelibs-foundation? >>> The SwiftPM build seemed to fail again with the same error it had the first >>> time: https://ci.swift.org/job/swift-PR-osx/2642/console But I >>> already fixed this in >>> https://github.com/apple/swift-package-manager/pull/515 >>> >>> Jacob >>> >>> On Thu, Jul 21, 2016 at 1:15 PM, Tony Parker <anthony.par...@apple.com> >>> wrote: >>> >>>> I kicked it off. >>>> >>>> - Tony >>>> >>>> On Jul 21, 2016, at 1:08 PM, Jacob Bandes-Storch via swift-dev < >>>> swift-dev@swift.org> wrote: >>>> >>>> Could someone kindly trigger CI again for me? >>>> https://github.com/apple/swift/pull/3637 >>>> >>>> Jacob >>>> _______________________________________________ >>>> swift-dev mailing list >>>> swift-dev@swift.org >>>> https://lists.swift.org/mailman/listinfo/swift-dev >>>> >>>> >>>> >>> >> >
_______________________________________________ swift-dev mailing list swift-dev@swift.org https://lists.swift.org/mailman/listinfo/swift-dev
