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

We keep seeing this failure in the bots: src/libdispatch.so: error: undefined reference to ‘_T0s17_assertionFailures5NeverOs12StaticStringV_SSAE4fileSu4lines6UInt32V5flagstFTfq4nxnnn_n' A clean build fixes it. However, it comes back, because if the bot builds the 4.0 branch and then goes and bu

Re: [swift-dev] Exclusivity checker hacking?

> On Oct 5, 2017, at 20:28, John McCall wrote: > > >> On Oct 5, 2017, at 6:34 PM, Jordan Rose via swift-dev > > wrote: >> >> >> >>> On Oct 5, 2017, at 15:23, David Zarzycki mailto:d...@znu.io>> >>> wrote: >>> >>> >>> On Oct 5, 2017, at 18:08, Jordan Rose

Re: [swift-dev] Exclusivity checker hacking?

> On Oct 5, 2017, at 6:34 PM, Jordan Rose via swift-dev > wrote: > > > >> On Oct 5, 2017, at 15:23, David Zarzycki mailto:d...@znu.io>> >> wrote: >> >> >> >>> On Oct 5, 2017, at 18:08, Jordan Rose >> > wrote: >>> >>> >>> On Oct 5, 2017, at 13:42, Davi

[swift-dev] [Swift CI] Build Failure: OSS - Swift Package - OS X (master) #423

Title: Report [FAILURE] oss-swift-package-osx [#423] Build URL:https://ci.swift.org/job/oss-swift-package-osx/423/ Project:oss-swift-package-osx Date of build:Thu, 05 Oct 2017 13:16:44 -0500 Build duration:5 hr 10 min Changes Commit ce8be93248910e

Re: [swift-dev] Exclusivity checker hacking?

> On Oct 5, 2017, at 15:44, David Zarzycki wrote: > > > >> On Oct 5, 2017, at 18:34, Jordan Rose > > wrote: >> >> >> >>> On Oct 5, 2017, at 15:23, David Zarzycki mailto:d...@znu.io>> >>> wrote: >>> >>> >>> On Oct 5, 2017, at 18:08, Jordan Rose >>>

Re: [swift-dev] Exclusivity checker hacking?

> On Oct 5, 2017, at 18:34, Jordan Rose wrote: > > > >> On Oct 5, 2017, at 15:23, David Zarzycki mailto:d...@znu.io>> >> wrote: >> >> >> >>> On Oct 5, 2017, at 18:08, Jordan Rose >> > wrote: >>> >>> >>> On Oct 5, 2017, at 13:42, David Zarzycki via swi

Re: [swift-dev] Exclusivity checker hacking?

> On Oct 5, 2017, at 15:23, David Zarzycki wrote: > > > >> On Oct 5, 2017, at 18:08, Jordan Rose > > wrote: >> >> >> >>> On Oct 5, 2017, at 13:42, David Zarzycki via swift-dev >> > wrote: >>> >>> Hello, >>> >>> As an experiment, I

Re: [swift-dev] Exclusivity checker hacking?

> On Oct 5, 2017, at 18:08, Jordan Rose wrote: > > > >> On Oct 5, 2017, at 13:42, David Zarzycki via swift-dev > > wrote: >> >> Hello, >> >> As an experiment, I’d like to force the exclusivity checking logic to always >> error at compile time, rather than a mix

Re: [swift-dev] Exclusivity checker hacking?

> On Oct 5, 2017, at 13:42, David Zarzycki via swift-dev > wrote: > > Hello, > > As an experiment, I’d like to force the exclusivity checking logic to always > error at compile time, rather than a mix of compile time and run time. Near > as I can tell, there is no built in debugging logic t

Re: [swift-dev] Exclusivity checker hacking?

> On Oct 5, 2017, at 16:50, Michael Gottesman via swift-dev > wrote: > > >> On Oct 5, 2017, at 1:42 PM, David Zarzycki via swift-dev >> wrote: >> >> Hello, >> >> As an experiment, I’d like to force the exclusivity checking logic to always >> error at compile time, rather than a mix of co

Re: [swift-dev] Exclusivity checker hacking?

> On Oct 5, 2017, at 1:42 PM, David Zarzycki via swift-dev > wrote: > > Hello, > > As an experiment, I’d like to force the exclusivity checking logic to always > error at compile time, rather than a mix of compile time and run time. Near > as I can tell, there is no built in debugging logic

[swift-dev] Exclusivity checker hacking?

Hello, As an experiment, I’d like to force the exclusivity checking logic to always error at compile time, rather than a mix of compile time and run time. Near as I can tell, there is no built in debugging logic to do this (not even to warn when dynamic checks are added). Am I missing something

Re: [swift-dev] Fuzzer tests failing?

> On Oct 5, 2017, at 14:19, David Zarzycki via swift-dev > wrote: > > > >> On Oct 5, 2017, at 14:06, Mark Lacey wrote: >> >> >> >>> On Oct 5, 2017, at 10:48 AM, David Zarzycki wrote: >>> >>> Hi Mark, >>> >>> Yes, Xcode 9.0 (9A235). I just did a clean build using >>> “./utils/build-sc

Re: [swift-dev] Fuzzer tests failing?

> On Oct 5, 2017, at 14:06, Mark Lacey wrote: > > > >> On Oct 5, 2017, at 10:48 AM, David Zarzycki wrote: >> >> Hi Mark, >> >> Yes, Xcode 9.0 (9A235). I just did a clean build using “./utils/build-script >> -r -t” and it still fails. What should I try next? > > Interesting. Are you updat

Re: [swift-dev] Fuzzer tests failing?

> On Oct 5, 2017, at 10:48 AM, David Zarzycki wrote: > > Hi Mark, > > Yes, Xcode 9.0 (9A235). I just did a clean build using “./utils/build-script > -r -t” and it still fails. What should I try next? Interesting. Are you updating with update-script, and building everything (including compil

Re: [swift-dev] Fuzzer tests failing?

Hi Mark, Yes, Xcode 9.0 (9A235). I just did a clean build using “./utils/build-script -r -t” and it still fails. What should I try next? Dave > On Oct 5, 2017, at 12:55, Mark Lacey via swift-dev > wrote: > > Are you building with Xcode 9.0? > > Did you try reconfiguring, e.g. > build-scr

Re: [swift-dev] Fuzzer tests failing?

Are you building with Xcode 9.0? Did you try reconfiguring, e.g. build-script all-your-options -- --reconfigure ? If those do not resolve the issue, I would suggest removing the swift-macosx-x86_64 directory in your build destination, and see if that helps. Mark > On Oct 5, 2017, at 7:51 AM

[swift-dev] Fuzzer tests failing?

So the following tests have been failing for a long time now on my macOS 10.13 system: Failing Tests (2): Swift(macosx-x86_64) :: Fuzzing/fuzzer_test.swift Swift(macosx-x86_64) :: Fuzzing/fuzzer_test_simpler.swift Due to a missing file: …/swift-macosx-x86_64/lib/swift/clang/lib/darw

[swift-dev] No rule to make swift_sections.S.o on Ubuntu 16.04?

Hi, I am building swift on Power8/LE (after making appropriate changes for ppc64le) and getting following error while building swift/stdlib make[2]: Entering directory '/root/swift-source/build/Unix_Makefiles-ReleaseAssert/swift-linux-powerpc64le' make[2]: *** No rule to make target 'stdlib/publi