Re: [swift-dev] [swift-lldb-dev] repl/test-repl-glibc.py Failure on Ubuntu

[Joseph Bell via swift-dev]

Hi all,

Has anyone looked further at getting the REPL working again on the master
branch builds?  Or for that matter installed pexpect on the CI server to
properly fail the build?

Joe


On Fri, Apr 15, 2016 at 10:13 PM, Ryan Lovelett 
wrote:

> Facepalm.
>
> On Fri, Apr 15, 2016, at 11:11 PM, Ryan Lovelett wrote:
> > Progress. Hat tip to William Dillon (@hpux735 on Twitter) for pointing
> > something out; `strace`
> >
> > Ran `strace` on the REPL while trying to import Glibc. Noticed that it
> > was looking for a file: /usr/lib/lldb/clang/linux/x86_64/glibc.modulemap
> > which does not exist. However,
> > /usr/lib/lldb/clang/linux/x86_64/glibc.modulemap does exist.
>
> /usr/lib/swift/linux/x86_64/glibc.modulemap
>
> >
> > Provided a symbolic link from
> > /usr/lib/lldb/clang/linux/x86_64/glibc.modulemap to
> > /usr/lib/lldb/clang/linux/x86_64/glibc.modulemap. Voila! It is importing
> > now.
>
> Provided a symbolic link from
> /usr/lib/swift/linux/x86_64/glibc.modulemap to
> /usr/lib/lldb/clang/linux/x86_64/glibc.modulemap. Voila! It is importing
> now.
>
> >
> > I'll start working on a patch in the morning (of course if someone beats
> > me to it I won't be mad; please). Just thought I'd update those
> > interested with a work around in the meantime.
>
> It is late. I'm clearly done for the day.
>



-- 
Joseph Bell
http://dev.iachieved.it/iachievedit/
@iachievedit
___
swift-dev mailing list
swift-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-dev

Re: [swift-dev] [swift-lldb-dev] repl/test-repl-glibc.py Failure on Ubuntu

[Todd Fiala via swift-dev]

Hi Joseph,

I'll poke around at this today and see if I can get this rolling forward
(or at least figure out what we're waiting on).

Thanks for your patience!

-Todd

On Tue, Apr 19, 2016 at 8:00 AM, Joseph Bell via swift-lldb-dev <
swift-lldb-...@swift.org> wrote:

> Hi all,
>
> Has anyone looked further at getting the REPL working again on the master
> branch builds?  Or for that matter installed pexpect on the CI server to
> properly fail the build?
>
> Joe
>
>
> On Fri, Apr 15, 2016 at 10:13 PM, Ryan Lovelett <
> swift-...@ryan.lovelett.me> wrote:
>
>> Facepalm.
>>
>> On Fri, Apr 15, 2016, at 11:11 PM, Ryan Lovelett wrote:
>> > Progress. Hat tip to William Dillon (@hpux735 on Twitter) for pointing
>> > something out; `strace`
>> >
>> > Ran `strace` on the REPL while trying to import Glibc. Noticed that it
>> > was looking for a file: /usr/lib/lldb/clang/linux/x86_64/glibc.modulemap
>> > which does not exist. However,
>> > /usr/lib/lldb/clang/linux/x86_64/glibc.modulemap does exist.
>>
>> /usr/lib/swift/linux/x86_64/glibc.modulemap
>>
>> >
>> > Provided a symbolic link from
>> > /usr/lib/lldb/clang/linux/x86_64/glibc.modulemap to
>> > /usr/lib/lldb/clang/linux/x86_64/glibc.modulemap. Voila! It is importing
>> > now.
>>
>> Provided a symbolic link from
>> /usr/lib/swift/linux/x86_64/glibc.modulemap to
>> /usr/lib/lldb/clang/linux/x86_64/glibc.modulemap. Voila! It is importing
>> now.
>>
>> >
>> > I'll start working on a patch in the morning (of course if someone beats
>> > me to it I won't be mad; please). Just thought I'd update those
>> > interested with a work around in the meantime.
>>
>> It is late. I'm clearly done for the day.
>>
>
>
>
> --
> Joseph Bell
> http://dev.iachieved.it/iachievedit/
> @iachievedit
>
> ___
> swift-lldb-dev mailing list
> swift-lldb-...@swift.org
> https://lists.swift.org/mailman/listinfo/swift-lldb-dev
>
>


-- 
-Todd
___
swift-dev mailing list
swift-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-dev

[swift-dev] Build failure for Linux: "No such module: SwiftGlibc"

[Karl Wagner via swift-dev]

I’m trying to cross-compile Swift for the Raspberry Pi. I’ve got the tools and 
most of the standard library compiling, but I’m getting stuck trying to build 
the platform components for Glibc. Swift is just complaining that the 
“SwiftGlibc” module doesn’t exist. I’d appreciate it if anybody could help 
trying to find out why.

I’ve been whittling down at the compile command, trying to figure out why it 
isn’t finding/building the module.

==
/build/Ninja-ReleaseAssert/swift-macosx-x86_64/bin/swiftc -c 
-target armv7-unknown-linux-gnueabihf 
-O -D INTERNAL_CHECKS_ENABLED 
-no-link-objc-runtime -autolink-force-load -emit-module -module-link-name 
swiftGlibc -force-single-frontend-invocation -parse-as-library 
-I 
/build/Ninja-ReleaseAssert/swift-linux-armv7/./lib/swift/linux/armv7
-module-cache-path 
/build/Ninja-ReleaseAssert/swift-linux-armv7/./module-cache
-emit-module-path 
/build/Ninja-ReleaseAssert/swift-linux-armv7/./lib/swift/linux/armv7/Glibc.swiftmodule
-o 
/build/Ninja-ReleaseAssert/swift-linux-armv7/stdlib/public/Platform/linux/armv7/Glibc.o
/swift/stdlib/public/Platform/Glibc.swift

/swift/stdlib/public/Platform/Glibc.swift:13:19: error: no such 
module 'SwiftGlibc'
@_exported import SwiftGlibc // Clang module
===

glibc.modulemap gets generated and copied in to the /lib/swift/linux/armv7 
build dir, and Glibc.swift looks like it just exports that out, so I’m guessing 
that Swift can’t find my modulemap - or what else does it need to build the 
SwiftGlibc module?

Many thanks
___
swift-dev mailing list
swift-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-dev

Re: [swift-dev] [swift-lldb-dev] repl/test-repl-glibc.py Failure on Ubuntu

[Mishal Shah via swift-dev]

Hi Joseph, 

We are currently reviewing pexpect module with security team, once we have an 
approval I will install it on swift-ci system. 

Thanks,
Mishal shah
> On Apr 19, 2016, at 8:23 AM, Todd Fiala via swift-lldb-dev 
>  wrote:
> 
> Hi Joseph,
> 
> I'll poke around at this today and see if I can get this rolling forward (or 
> at least figure out what we're waiting on).
> 
> Thanks for your patience!
> 
> -Todd
> 
> On Tue, Apr 19, 2016 at 8:00 AM, Joseph Bell via swift-lldb-dev 
> mailto:swift-lldb-...@swift.org>> wrote:
> Hi all,
> 
> Has anyone looked further at getting the REPL working again on the master 
> branch builds?  Or for that matter installed pexpect on the CI server to 
> properly fail the build?
> 
> Joe
> 
> 
> On Fri, Apr 15, 2016 at 10:13 PM, Ryan Lovelett  > wrote:
> Facepalm.
> 
> On Fri, Apr 15, 2016, at 11:11 PM, Ryan Lovelett wrote:
> > Progress. Hat tip to William Dillon (@hpux735 on Twitter) for pointing
> > something out; `strace`
> >
> > Ran `strace` on the REPL while trying to import Glibc. Noticed that it
> > was looking for a file: /usr/lib/lldb/clang/linux/x86_64/glibc.modulemap
> > which does not exist. However,
> > /usr/lib/lldb/clang/linux/x86_64/glibc.modulemap does exist.
> 
> /usr/lib/swift/linux/x86_64/glibc.modulemap
> 
> >
> > Provided a symbolic link from
> > /usr/lib/lldb/clang/linux/x86_64/glibc.modulemap to
> > /usr/lib/lldb/clang/linux/x86_64/glibc.modulemap. Voila! It is importing
> > now.
> 
> Provided a symbolic link from
> /usr/lib/swift/linux/x86_64/glibc.modulemap to
> /usr/lib/lldb/clang/linux/x86_64/glibc.modulemap. Voila! It is importing
> now.
> 
> >
> > I'll start working on a patch in the morning (of course if someone beats
> > me to it I won't be mad; please). Just thought I'd update those
> > interested with a work around in the meantime.
> 
> It is late. I'm clearly done for the day.
> 
> 
> 
> -- 
> Joseph Bell
> http://dev.iachieved.it/iachievedit/ 
> @iachievedit
> 
> ___
> swift-lldb-dev mailing list
> swift-lldb-...@swift.org 
> https://lists.swift.org/mailman/listinfo/swift-lldb-dev 
> 
> 
> 
> 
> 
> -- 
> -Todd
> ___
> swift-lldb-dev mailing list
> swift-lldb-...@swift.org 
> https://lists.swift.org/mailman/listinfo/swift-lldb-dev 
> 
___
swift-dev mailing list
swift-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-dev

Re: [swift-dev] [swift-lldb-dev] repl/test-repl-glibc.py Failure on Ubuntu

[Ryan Lovelett via swift-dev]

On Tue, Apr 19, 2016, at 11:00 AM, Joseph Bell wrote:
> Hi all,
>
> Has anyone looked further at getting the REPL working again on the
> master branch builds?  Or for that matter installed pexpect on the CI
> server to properly fail the build?
 
@Joe,
 
Out of curiosity, did the work-around I proposed on Friday work for you?
I've built from master and created the symbolic links and restored
functionality to lldb and the REPL.
 
If that does work I think that gives me something to work towards for
fixing it permanently.
 
>
> Joe
>
>
> On Fri, Apr 15, 2016 at 10:13 PM, Ryan Lovelett  d...@ryan.lovelett.me> wrote:
>> Facepalm.
>>
>>  On Fri, Apr 15, 2016, at 11:11 PM, Ryan Lovelett wrote:
>>  > Progress. Hat tip to William Dillon (@hpux735 on Twitter) for
>>  > pointing something out; `strace`
>>  >
>>  > Ran `strace` on the REPL while trying to import Glibc. Noticed
>>  > that it was looking for a file:
>>  > /usr/lib/lldb/clang/linux/x86_64/glibc.modulemap which does not
>>  > exist. However, /usr/lib/lldb/clang/linux/x86_64/glibc.modulemap
>>  > does exist.
>>
>> /usr/lib/swift/linux/x86_64/glibc.modulemap
>>
>>  >
>>  > Provided a symbolic link from
>>  > /usr/lib/lldb/clang/linux/x86_64/glibc.modulemap to
>>  > /usr/lib/lldb/clang/linux/x86_64/glibc.modulemap. Voila! It is
>>  > importing now.
>>
>>  Provided a symbolic link from
>>  /usr/lib/swift/linux/x86_64/glibc.modulemap to
>> /usr/lib/lldb/clang/linux/x86_64/glibc.modulemap. Voila! It is
>> importing now.
>>
>>  >
>>  > I'll start working on a patch in the morning (of course if someone
>>  > beats me to it I won't be mad; please). Just thought I'd update
>>  > those interested with a work around in the meantime.
>>
>> It is late. I'm clearly done for the day.
>
>
>
> --
> Joseph Bell
> http://dev.iachieved.it/iachievedit/
> @iachievedit
 
___
swift-dev mailing list
swift-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-dev

[swift-dev] CLion for Swift Compiler Development

[Ryan Lovelett via swift-dev]

I've been using CLion lately for C++ development on Linux. It uses CMake
for its integrated builds as does Swift. This seems, at least at first
glance, to make it possible to use CLion as an IDE on Linux to develop
the Swift toolchain.

I was just wondering if anyone has attempted to be able to use CLion for
developing the Swift language.

NOTE: I do not mean using CLion to write software that uses the Swift
language.
___
swift-dev mailing list
swift-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-dev

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

[Greg Parker via swift-dev]

Dmitri, your commit 265fa20c re-enabled tests that were previously not running, 
correct?


> On Apr 19, 2016, at 12:15 PM, no-re...@swift.org wrote:
> 
> [FAILURE] oss-swift-incremental-RA-linux-ubuntu-14_04 [#4226]
> 
> Build URL:
> https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-14_04/4226/ 
> 
> Project:  oss-swift-incremental-RA-linux-ubuntu-14_04
> Date of build:Tue, 19 Apr 2016 12:02:05 -0700
> Build duration:   13 min
> Identified problems:
> 
> Compile Error: This build failed because of a compile error. Below is a list 
> of all errors in the build log:
> Indication 1 
> 
> Regression test failed: This build failed because a regression test in the 
> test suite FAILed. Below is a list of all errors:
> Indication 1 
> 
> Tests:
> 
> Name: Swift
> Failed: 2 test(s), Passed: 7807 test(s), Total: 7809 test(s)
> Failed: Swift.1_stdlib.ArrayTraps.swift.gyb 
> 
> Failed: Swift.IRGen.module_hash.swift 
> 
> Name: Swift-Unit
> Failed: 0 test(s), Passed: 264 test(s), Total: 264 test(s)
> 
> Changes
> 
> Commit 265fa20ce1042f139fbd8647c4dda97e2805cfe3 by gribozavr:
> CMake: re-add primary testsuite to the validation target
> 
> edit: test/CMakeLists.txt

___
swift-dev mailing list
swift-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-dev

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

[Dmitri Gribenko via swift-dev]

Right.  The primary testsuite was not running since yesterday because of my
build-script changes.

Dmitri

On Tue, Apr 19, 2016 at 12:22 PM, Greg Parker  wrote:

> Dmitri, your commit 265fa20c re-enabled tests that were previously not
> running, correct?
>
>
> On Apr 19, 2016, at 12:15 PM, no-re...@swift.org wrote:
>
> [FAILURE] oss-swift-incremental-RA-linux-ubuntu-14_04 [#4226]
> Build URL:
> https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-14_04/4226/
> Project: oss-swift-incremental-RA-linux-ubuntu-14_04
> Date of build: Tue, 19 Apr 2016 12:02:05 -0700
> Build duration: 13 minIdentified problems:
>
>- Compile Error: This build failed because of a compile error. Below
>is a list of all errors in the build log:
>   - Indication 1
>   
> 
>- Regression test failed: This build failed because a regression test
>in the test suite FAILed. Below is a list of all errors:
>   - Indication 1
>   
> 
>
> Tests:
> Name: *Swift*
> Failed: 2 test(s), Passed: 7807 test(s), Total: 7809 test(s)
>
>
> * - Failed: Swift.1_stdlib.ArrayTraps.swift.gyb
> *
>
>
> * - Failed: Swift.IRGen.module_hash.swift
> *
> Name: *Swift-Unit*
> Failed: 0 test(s), Passed: 264 test(s), Total: 264 test(s)
>
> Changes
>
>- Commit *265fa20ce1042f139fbd8647c4dda97e2805cfe3* by *gribozavr:*
>
>CMake: re-add primary testsuite to the validation target
>- *edit*: test/CMakeLists.txt
>
>
>


-- 
main(i,j){for(i=2;;i++){for(j=2;j*/
___
swift-dev mailing list
swift-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-dev

Re: [swift-dev] [swift-lldb-dev] repl/test-repl-glibc.py Failure on Ubuntu

[Ryan Lovelett via swift-dev]

First I want to say wonderful help! Thank you.

On Fri, Apr 15, 2016, at 06:01 PM, Jim Ingham wrote:
> The REPL makes a swift compiler, in which it runs your code (obvious...) 
> So when you do "import " in the REPL, we need to load that
> module into our swift compiler. In the lldb REPL that is managed in
> SwiftExpressionParser::PerformAutoImport.  This will call lldb's
> SwiftASTContext::FindAndLoadModule -> SwiftASTContext::LoadModule, which
> will then do three things: find & tell the swift compiler about the
> .swiftmodule, dlopen any underlying libraries the .swiftmodule needs. 
> Finally, if the module imported C/ObjC code, the swift module doesn't
> describe the types coming from C but relies on types being in a clang
> module that can be imported into Swift.  That means that the REPL must
> rebuild a clang module which matches the one originally used to build the
> swift module.  
> 
> It's that final step that tends to be tricky, since Swift has to be
> convinced that the Clang module that the ClangImporter builds is
> compatible with the one that was originally used to build the swift
> module, and it is somewhat picky about this.  All that checking goes on
> in swift, not lldb, and I'm not very familiar with how this is done.
> 
> One difficulty that comes up often is figuring out where the module map &
> headers that were used to build the ClangImporter when the Swift module
> was originally constructed are on the current system.  On OS X the
> options that were used to build the ClangImporter are serialized in the
> swift module.  So we just grab that blob and use it to initialize the
> ClangImporter.  Construction this environment happens in
> SwiftASTContext::CreateInstance - for instance the call to
> loadFromSerializedAST is where we load the serialized options.  
>

Not sure if you'll find this interesting or not but
loadFromSerializedAST never actually gets reached when I'm debugging
(e.g., `b SwiftASTContext.cpp:1489` and `b SwiftASTContext.cpp:1809`)
based on what you've discussed here that seems to be counter to your
explanation.

I've devised a "work-around".

But I cannot seem to root out the code that is responsible for building
the path where it looks for the modulemap. Currently it is looking for
it in `/usr/lib/lldb/clang/linux/x86_64/glibc.modulemap`. Which is not
where it gets installed.

I could make a patch for Swift that copies the module map to that
location during install. But that feels like a hack. I'd rather get into
the logic of how that path is constructed and resolve it there.
 
> That wasn't the way it was done in the early Swift days, instead the
> DWARF for the swift module would have the compiler options used to create
> the swift compiler (including some that were for the importer) and lldb
> would try to parse them and extract whatever goodies it needed.  That was
> fragile, and we switched to the serialization approach, but the code to
> parse up the DWARF is still there, as well as a bunch of assist functions
> so that we could add any extra information we might know (like what SDK's
> are being used.)
> 
> If you poke around in this code you'll see that we log pretty extensively
> the options we are using to make up both our Swift compiler and the
> ClangImporter.  To see this in action in the REPL, turn on the "types"
> log:
> 
>  > :log enable -f /tmp/lldb-types-log.txt lldb type
> 
> Then do your import.  If this is getting auto-imported too early for you
> to turn on the log by hand, then just put the log command (without the
> ":") in your .lldbinit file, the REPL, being just a particular invocation
> of lldb, will read that file.
> 
> Hope this helps,
> 
> Jim
> 
> 
> 
> 
> > On Apr 15, 2016, at 8:19 AM, Ryan Lovelett via swift-lldb-dev 
> >  wrote:
> > 
> > I've tried reverting c6121d56b19305cf59148d46af54c06b771f3180 just to
> > see if doing that will restore functionality to lldb/repl.
> > 
> > Unfortunately too many things have changed in the build system since
> > that commit for a revert to make sense anymore
> > 
> > Can anyone provide documentation/explain the mechanics of what happens
> > when I type "import Glibc" into the REPL/lldb?
> > 
> > On Thu, Apr 14, 2016, at 05:47 PM, Dmitri Gribenko wrote:
> >> +Brian
> >> 
> >> On Thu, Apr 14, 2016 at 2:46 PM, Ryan Lovelett via swift-dev
> >>  wrote:
> >>> I've played around with `git bisect` and I think I've tracked it down to
> >>> this commit [1]. Which came from PR #1704 [2]. I've also updated the 
> >>> issue,
> >>> SR-1109, to include this information.
> >>> 
> >>> c6121d56b19305cf59148d46af54c06b771f3180 is the first bad commit
> >>> commit c6121d56b19305cf59148d46af54c06b771f3180
> >>> Author: Brian Gesiak 
> >>> Date:   Wed Mar 16 13:29:42 2016 -0400
> >>> 
> >>>[Un-revert][Glibc] Configure modulemap for target, not host
> >>> 
> >>>This reverts commit f2154ee94d, which reverted 04e1cd5bda. The original
> >>>commit needed to be reverted because of an issue in which install
>

Re: [swift-dev] R_ARM_GOT_PREL error when building Swift on Pi from source

[Timothy Wood via swift-dev]

> On Apr 17, 2016, at 11:33 PM, Timothy Wood via swift-dev 
>  wrote:
> 
> I might try again tomorrow updating to a newer clang build, or maybe I should 
> just wave the white flag and rewrite my tiny codebase in C++ instead of 
> trying to use Swift here, and wait for it to be a bit more stable/supported.


FWIW, last night I tried taking the current swift-llvm swift-2.2.branch and 
cherry picking your ARM_REL32/GOT_PREL patch atop it. This got *much* further 
through the build, but eventually failed while building the  Swift standard 
library:

swift: /home/pi/Source/Swift/llvm/include/llvm/ADT/PointerIntPair.h:114: void 
llvm::PointerIntPair 
>::setPointerAndInt(PointerTy, IntType) [PointerTy = swift::ProtocolConformance 
*, IntBits = 2, IntType = swift::ConformanceKind, PtrTraits = 
llvm::PointerLikeTypeTraits]: Assertion `(PtrWord 
& ~PointerBitMask) == 0 && "Pointer is not sufficiently aligned"' failed.
…
1.  While type-checking 'EnumerateSequence' at 
/home/pi/Source/Swift/swift/stdlib/public/core/Algorithm.swift:192:8
ninja: build stopped: subcommand failed.


-tim

___
swift-dev mailing list
swift-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-dev

Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift Incremental RA - OS X (master) #3504

[Greg Parker via swift-dev]

> On Apr 19, 2016, at 12:45 PM, no-re...@swift.org wrote:
> 
> [FAILURE] oss-swift-incremental-RA-osx [#3504]
> 
> Tests: 
> 
> Name: Swift
> Failed: 1 test(s), Passed: 7808 test(s), Total: 7809 test(s)
>   • Failed: Swift.IRGen.module_hash.swift
> 

This may be an older failure recently uncovered by changes to which tests get 
run. Jordan, Erik, any guesses of changes that might have broken it?

Errors and recorded output below:

/Volumes/precious/cvs/swift-github/swift/test/IRGen/module_hash.swift:49:15: 
error: expected string not found in input
// CHECK-DAG: test.o: MD5=[[TEST4_MD5]]
  ^
:21:1: note: scanning from here
thread 0: fetched 
/Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o
^
:21:1: note: with variable "TEST4_MD5" equal to 
"c32902f17598124702a017fac0e9b86d"
thread 0: fetched 
/Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o
^
:26:161: note: possible intended match here
/Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o:
 MD5=e888cbc861bdeaaf786df90c4e5a40da


^
/Volumes/precious/cvs/swift-github/swift/test/IRGen/module_hash.swift:59:15: 
error: expected string not found in input
// CHECK-DAG: test.o: prev MD5=[[TEST4_MD5]] skipping
  ^
:30:1: note: scanning from here
thread 0: fetched 
/Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o
^
:30:1: note: with variable "TEST4_MD5" equal to 
"c32902f17598124702a017fac0e9b86d"
thread 0: fetched 
/Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o
^
:35:161: note: possible intended match here
/Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o:
 prev MD5=e888cbc861bdeaaf786df90c4e5a40da recompiling


^



single-threaded initial
/Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o:
 MD5=bbfcd715eee1f17799113c1826dfe124
single-threaded same compilation
/Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o:
 MD5=bbfcd715eee1f17799113c1826dfe124
/Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o:
 prev MD5=bbfcd715eee1f17799113c1826dfe124 skipping
single-threaded file changed
/Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o:
 MD5=bd6e3d5aef7c83992235017dacea08a9
/Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o:
 prev MD5=bbfcd715eee1f17799113c1826dfe124 recompiling
single-threaded option changed
/Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o:
 MD5=d67d06dfe12e11f7a2e4403461c646cd
/Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o:
 prev MD5=bd6e3d5aef7c83992235017dacea08a9 recompiling
multi-threaded initial
thread 0: fetched 
/Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o
thread 1: fetched 
/Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/simple.o
/Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/simple.o:
 MD5=a3b21cc67542538560df721fd14c5797
/Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRG

Re: [swift-dev] [Swift CI] Build Still Failing: 0. OSS - Swift Incremental RA - Ubuntu 14.04 (master) #4239

[Greg Parker via swift-dev]

> On Apr 19, 2016, at 7:54 PM, no-re...@swift.org wrote:
> 
> New issue found!
> 
> [FAILURE] oss-swift-incremental-RA-linux-ubuntu-14_04 [#4239]
> 
> Build URL:
> https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-14_04/4239/
> Project:  oss-swift-incremental-RA-linux-ubuntu-14_04
> Date of build:Tue, 19 Apr 2016 19:42:23 -0700
> 
>   • Failed: Swift.1_stdlib.ArrayTraps.swift.gyb

This may be an older failure that was uncovered by changes to which tests get 
run where. 

The failures (excerpted below) all look like assertions in nonatomic 
refcounting. Roman, did you test fa0d270a on Linux? What other recent commits 
affected non-atomic refcounting?


[ RUN  ] ArrayTraps.sliceBounds1/read
stderr>>> a.out_Release: 
/home/buildnode/jenkins/workspace/oss-swift-incremental-RA-linux-ubuntu-14_04/swift/include/swift/Runtime/../../../stdlib/public/SwiftShims/RefCount.h:198:
 void StrongRefCount::decrementFromOneAndDeallocateNonAtomic(): Assertion 
`refCount == RC_ONE && "Expect a count of 1"' failed.
stderr>>> CRASHED: SIGABRT
the test crashed unexpectedly
[ FAIL ] ArrayTraps.sliceBounds1/read

[ RUN  ] ArrayTraps.sliceBounds1/write
stderr>>> a.out_Release: 
/home/buildnode/jenkins/workspace/oss-swift-incremental-RA-linux-ubuntu-14_04/swift/include/swift/Runtime/../../../stdlib/public/SwiftShims/RefCount.h:198:
 void StrongRefCount::decrementFromOneAndDeallocateNonAtomic(): Assertion 
`refCount == RC_ONE && "Expect a count of 1"' failed.
stderr>>> CRASHED: SIGABRT
the test crashed unexpectedly
[ FAIL ] ArrayTraps.sliceBounds1/write

[ RUN  ] ArrayTraps.insert(_:at:)/-1
stderr>>> a.out_Release: 
/home/buildnode/jenkins/workspace/oss-swift-incremental-RA-linux-ubuntu-14_04/swift/include/swift/Runtime/../../../stdlib/public/SwiftShims/RefCount.h:198:
 void StrongRefCount::decrementFromOneAndDeallocateNonAtomic(): Assertion 
`refCount == RC_ONE && "Expect a count of 1"' failed.
stderr>>> CRASHED: SIGABRT
the test crashed unexpectedly
[ FAIL ] ArrayTraps.insert(_:at:)/-1

[ RUN  ] ArrayTraps.remove(at:)/-1
stderr>>> a.out_Release: 
/home/buildnode/jenkins/workspace/oss-swift-incremental-RA-linux-ubuntu-14_04/swift/include/swift/Runtime/../../../stdlib/public/SwiftShims/RefCount.h:198:
 void StrongRefCount::decrementFromOneAndDeallocateNonAtomic(): Assertion 
`refCount == RC_ONE && "Expect a count of 1"' failed.
stderr>>> CRASHED: SIGABRT
the test crashed unexpectedly
[ FAIL ] ArrayTraps.remove(at:)/-1


-- 
Greg Parker gpar...@apple.com Runtime Wrangler


___
swift-dev mailing list
swift-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-dev

Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift Incremental RA - OS X (master) #3504

[Erik Eckstein via swift-dev]

This looks like there is some kind of non-determinism in the compilation.

> On Apr 19, 2016, at 8:14 PM, Greg Parker  wrote:
> 
> 
>> On Apr 19, 2016, at 12:45 PM, no-re...@swift.org wrote:
>> 
>> [FAILURE] oss-swift-incremental-RA-osx [#3504]
>> 
>> Tests: 
>> 
>> Name: Swift
>> Failed: 1 test(s), Passed: 7808 test(s), Total: 7809 test(s)
>>  • Failed: Swift.IRGen.module_hash.swift
>> 
> 
> This may be an older failure recently uncovered by changes to which tests get 
> run. Jordan, Erik, any guesses of changes that might have broken it?
> 
> Errors and recorded output below:
> 
> /Volumes/precious/cvs/swift-github/swift/test/IRGen/module_hash.swift:49:15: 
> error: expected string not found in input
> // CHECK-DAG: test.o: MD5=[[TEST4_MD5]]
>  ^
> :21:1: note: scanning from here
> thread 0: fetched 
> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o
> ^
> :21:1: note: with variable "TEST4_MD5" equal to 
> "c32902f17598124702a017fac0e9b86d"
> thread 0: fetched 
> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o
> ^
> :26:161: note: possible intended match here
> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o:
>  MD5=e888cbc861bdeaaf786df90c4e5a40da
>   
>   
>^
> /Volumes/precious/cvs/swift-github/swift/test/IRGen/module_hash.swift:59:15: 
> error: expected string not found in input
> // CHECK-DAG: test.o: prev MD5=[[TEST4_MD5]] skipping
>  ^
> :30:1: note: scanning from here
> thread 0: fetched 
> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o
> ^
> :30:1: note: with variable "TEST4_MD5" equal to 
> "c32902f17598124702a017fac0e9b86d"
> thread 0: fetched 
> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o
> ^
> :35:161: note: possible intended match here
> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o:
>  prev MD5=e888cbc861bdeaaf786df90c4e5a40da recompiling
>   
>   
>^
> 
> 
> 
> single-threaded initial
> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o:
>  MD5=bbfcd715eee1f17799113c1826dfe124
> single-threaded same compilation
> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o:
>  MD5=bbfcd715eee1f17799113c1826dfe124
> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o:
>  prev MD5=bbfcd715eee1f17799113c1826dfe124 skipping
> single-threaded file changed
> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o:
>  MD5=bd6e3d5aef7c83992235017dacea08a9
> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o:
>  prev MD5=bbfcd715eee1f17799113c1826dfe124 recompiling
> single-threaded option changed
> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o:
>  MD5=d67d06dfe12e11f7a2e4403461c646cd
> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o:
>  prev MD5=bd6e3d5aef7c83992235017dacea08a9 recompiling
> multi-threaded initial
> thread 0: fetched 
> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o
> thread 1: fetched 
> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/simple.o
> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInf

Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift Incremental RA - OS X (master) #3504

[Greg Parker via swift-dev]

Looks like it was caused by the RR code motion merge 
(https://github.com/apple/swift/pull/2064). 

Xin, I'm planning to revert 49f1c66d7b20b29097d7aec99835c5a42a2048bf and 
3824a9479ed2df701d4a0c9467495a4c37f0 once my tests finish, unless you have 
a fix in the next few minutes.


> On Apr 19, 2016, at 8:50 PM, Erik Eckstein  wrote:
> 
> This looks like there is some kind of non-determinism in the compilation.
> 
>> On Apr 19, 2016, at 8:14 PM, Greg Parker  wrote:
>> 
>> 
>>> On Apr 19, 2016, at 12:45 PM, no-re...@swift.org wrote:
>>> 
>>> [FAILURE] oss-swift-incremental-RA-osx [#3504]
>>> 
>>> Tests: 
>>> 
>>> Name: Swift
>>> Failed: 1 test(s), Passed: 7808 test(s), Total: 7809 test(s)
>>> • Failed: Swift.IRGen.module_hash.swift
>>> 
>> 
>> This may be an older failure recently uncovered by changes to which tests 
>> get run. Jordan, Erik, any guesses of changes that might have broken it?
>> 
>> Errors and recorded output below:
>> 
>> /Volumes/precious/cvs/swift-github/swift/test/IRGen/module_hash.swift:49:15: 
>> error: expected string not found in input
>> // CHECK-DAG: test.o: MD5=[[TEST4_MD5]]
>> ^
>> :21:1: note: scanning from here
>> thread 0: fetched 
>> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o
>> ^
>> :21:1: note: with variable "TEST4_MD5" equal to 
>> "c32902f17598124702a017fac0e9b86d"
>> thread 0: fetched 
>> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o
>> ^
>> :26:161: note: possible intended match here
>> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o:
>>  MD5=e888cbc861bdeaaf786df90c4e5a40da
>>  
>>  
>> ^
>> /Volumes/precious/cvs/swift-github/swift/test/IRGen/module_hash.swift:59:15: 
>> error: expected string not found in input
>> // CHECK-DAG: test.o: prev MD5=[[TEST4_MD5]] skipping
>> ^
>> :30:1: note: scanning from here
>> thread 0: fetched 
>> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o
>> ^
>> :30:1: note: with variable "TEST4_MD5" equal to 
>> "c32902f17598124702a017fac0e9b86d"
>> thread 0: fetched 
>> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o
>> ^
>> :35:161: note: possible intended match here
>> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o:
>>  prev MD5=e888cbc861bdeaaf786df90c4e5a40da recompiling
>>  
>>  
>> ^
>> 
>> 
>> 
>> single-threaded initial
>> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o:
>>  MD5=bbfcd715eee1f17799113c1826dfe124
>> single-threaded same compilation
>> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o:
>>  MD5=bbfcd715eee1f17799113c1826dfe124
>> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o:
>>  prev MD5=bbfcd715eee1f17799113c1826dfe124 skipping
>> single-threaded file changed
>> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o:
>>  MD5=bd6e3d5aef7c83992235017dacea08a9
>> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o:
>>  prev MD5=bbfcd715eee1f17799113c1826dfe124 recompiling
>> single-threaded option changed
>> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o:
>>  MD5=d67d06dfe12e11f7a2e4403461c646cd
>> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o:
>>  prev MD5=bd6e3d5aef7c83992235017dacea08a9 recompiling
>> multi-threaded initial
>> thread 0: fetched 
>> 

Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift Incremental RA - OS X (master) #3504

[Xin Tong via swift-dev]

I will check in something to disable the pass.

-Xin



> On Apr 19, 2016, at 9:34 PM, Greg Parker  wrote:
> 
> Looks like it was caused by the RR code motion merge 
> (https://github.com/apple/swift/pull/2064). 
> 
> Xin, I'm planning to revert 49f1c66d7b20b29097d7aec99835c5a42a2048bf and 
> 3824a9479ed2df701d4a0c9467495a4c37f0 once my tests finish, unless you 
> have a fix in the next few minutes.
> 
> 
>> On Apr 19, 2016, at 8:50 PM, Erik Eckstein  wrote:
>> 
>> This looks like there is some kind of non-determinism in the compilation.
>> 
>>> On Apr 19, 2016, at 8:14 PM, Greg Parker  wrote:
>>> 
>>> 
 On Apr 19, 2016, at 12:45 PM, no-re...@swift.org wrote:
 
 [FAILURE] oss-swift-incremental-RA-osx [#3504]
 
 Tests: 
 
 Name: Swift
 Failed: 1 test(s), Passed: 7808 test(s), Total: 7809 test(s)
• Failed: Swift.IRGen.module_hash.swift
 
>>> 
>>> This may be an older failure recently uncovered by changes to which tests 
>>> get run. Jordan, Erik, any guesses of changes that might have broken it?
>>> 
>>> Errors and recorded output below:
>>> 
>>> /Volumes/precious/cvs/swift-github/swift/test/IRGen/module_hash.swift:49:15:
>>>  error: expected string not found in input
>>> // CHECK-DAG: test.o: MD5=[[TEST4_MD5]]
>>>^
>>> :21:1: note: scanning from here
>>> thread 0: fetched 
>>> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o
>>> ^
>>> :21:1: note: with variable "TEST4_MD5" equal to 
>>> "c32902f17598124702a017fac0e9b86d"
>>> thread 0: fetched 
>>> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o
>>> ^
>>> :26:161: note: possible intended match here
>>> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o:
>>>  MD5=e888cbc861bdeaaf786df90c4e5a40da
>>> 
>>> 
>>>  ^
>>> /Volumes/precious/cvs/swift-github/swift/test/IRGen/module_hash.swift:59:15:
>>>  error: expected string not found in input
>>> // CHECK-DAG: test.o: prev MD5=[[TEST4_MD5]] skipping
>>>^
>>> :30:1: note: scanning from here
>>> thread 0: fetched 
>>> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o
>>> ^
>>> :30:1: note: with variable "TEST4_MD5" equal to 
>>> "c32902f17598124702a017fac0e9b86d"
>>> thread 0: fetched 
>>> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o
>>> ^
>>> :35:161: note: possible intended match here
>>> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o:
>>>  prev MD5=e888cbc861bdeaaf786df90c4e5a40da recompiling
>>> 
>>> 
>>>  ^
>>> 
>>> 
>>> 
>>> single-threaded initial
>>> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o:
>>>  MD5=bbfcd715eee1f17799113c1826dfe124
>>> single-threaded same compilation
>>> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o:
>>>  MD5=bbfcd715eee1f17799113c1826dfe124
>>> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o:
>>>  prev MD5=bbfcd715eee1f17799113c1826dfe124 skipping
>>> single-threaded file changed
>>> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o:
>>>  MD5=bd6e3d5aef7c83992235017dacea08a9
>>> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o:
>>>  prev MD5=bbfcd715eee1f17799113c1826dfe124 recompiling
>>> single-threaded option changed
>>> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o:
>>>  MD5=d67d06dfe12e11f7a2e4403461c646cd
>>> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-D

Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift Incremental RA - OS X (master) #3504

[Greg Parker via swift-dev]

Thanks. I'll try that.


> On Apr 19, 2016, at 9:35 PM, Xin Tong  wrote:
> 
> I will check in something to disable the pass.
> 
> -Xin
> 
> 
> 
>> On Apr 19, 2016, at 9:34 PM, Greg Parker  wrote:
>> 
>> Looks like it was caused by the RR code motion merge 
>> (https://github.com/apple/swift/pull/2064). 
>> 
>> Xin, I'm planning to revert 49f1c66d7b20b29097d7aec99835c5a42a2048bf and 
>> 3824a9479ed2df701d4a0c9467495a4c37f0 once my tests finish, unless you 
>> have a fix in the next few minutes.
>> 
>> 
>>> On Apr 19, 2016, at 8:50 PM, Erik Eckstein  wrote:
>>> 
>>> This looks like there is some kind of non-determinism in the compilation.
>>> 
 On Apr 19, 2016, at 8:14 PM, Greg Parker  wrote:
 
 
> On Apr 19, 2016, at 12:45 PM, no-re...@swift.org wrote:
> 
> [FAILURE] oss-swift-incremental-RA-osx [#3504]
> 
> Tests: 
> 
> Name: Swift
> Failed: 1 test(s), Passed: 7808 test(s), Total: 7809 test(s)
>   • Failed: Swift.IRGen.module_hash.swift
> 
 
 This may be an older failure recently uncovered by changes to which tests 
 get run. Jordan, Erik, any guesses of changes that might have broken it?
 
 Errors and recorded output below:
 
 /Volumes/precious/cvs/swift-github/swift/test/IRGen/module_hash.swift:49:15:
  error: expected string not found in input
 // CHECK-DAG: test.o: MD5=[[TEST4_MD5]]
   ^
 :21:1: note: scanning from here
 thread 0: fetched 
 /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o
 ^
 :21:1: note: with variable "TEST4_MD5" equal to 
 "c32902f17598124702a017fac0e9b86d"
 thread 0: fetched 
 /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o
 ^
 :26:161: note: possible intended match here
 /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o:
  MD5=e888cbc861bdeaaf786df90c4e5a40da


   ^
 /Volumes/precious/cvs/swift-github/swift/test/IRGen/module_hash.swift:59:15:
  error: expected string not found in input
 // CHECK-DAG: test.o: prev MD5=[[TEST4_MD5]] skipping
   ^
 :30:1: note: scanning from here
 thread 0: fetched 
 /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o
 ^
 :30:1: note: with variable "TEST4_MD5" equal to 
 "c32902f17598124702a017fac0e9b86d"
 thread 0: fetched 
 /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o
 ^
 :35:161: note: possible intended match here
 /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o:
  prev MD5=e888cbc861bdeaaf786df90c4e5a40da recompiling


   ^
 
 
 
 single-threaded initial
 /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o:
  MD5=bbfcd715eee1f17799113c1826dfe124
 single-threaded same compilation
 /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o:
  MD5=bbfcd715eee1f17799113c1826dfe124
 /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o:
  prev MD5=bbfcd715eee1f17799113c1826dfe124 skipping
 single-threaded file changed
 /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o:
  MD5=bd6e3d5aef7c83992235017dacea08a9
 /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o:
  prev MD5=bbfcd715eee1f17799113c1826dfe124 recompiling
 single-threaded option changed
 /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-

Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift Incremental RA - OS X (master) #3504

[Xin Tong via swift-dev]

Done in commit c2e8c81227263c9947f0ee0b8f9f6689d5e7bd21 , I have some commit on 
top of this one, so reverting is not very easy.
-Xin

> On Apr 19, 2016, at 9:40 PM, Greg Parker  wrote:
> 
> Thanks. I'll try that.
> 
> 
>> On Apr 19, 2016, at 9:35 PM, Xin Tong  wrote:
>> 
>> I will check in something to disable the pass.
>> 
>> -Xin
>> 
>> 
>> 
>>> On Apr 19, 2016, at 9:34 PM, Greg Parker  wrote:
>>> 
>>> Looks like it was caused by the RR code motion merge 
>>> (https://github.com/apple/swift/pull/2064). 
>>> 
>>> Xin, I'm planning to revert 49f1c66d7b20b29097d7aec99835c5a42a2048bf and 
>>> 3824a9479ed2df701d4a0c9467495a4c37f0 once my tests finish, unless you 
>>> have a fix in the next few minutes.
>>> 
>>> 
 On Apr 19, 2016, at 8:50 PM, Erik Eckstein  wrote:
 
 This looks like there is some kind of non-determinism in the compilation.
 
> On Apr 19, 2016, at 8:14 PM, Greg Parker  wrote:
> 
> 
>> On Apr 19, 2016, at 12:45 PM, no-re...@swift.org wrote:
>> 
>> [FAILURE] oss-swift-incremental-RA-osx [#3504]
>> 
>> Tests: 
>> 
>> Name: Swift
>> Failed: 1 test(s), Passed: 7808 test(s), Total: 7809 test(s)
>>  • Failed: Swift.IRGen.module_hash.swift
>> 
> 
> This may be an older failure recently uncovered by changes to which tests 
> get run. Jordan, Erik, any guesses of changes that might have broken it?
> 
> Errors and recorded output below:
> 
> /Volumes/precious/cvs/swift-github/swift/test/IRGen/module_hash.swift:49:15:
>  error: expected string not found in input
> // CHECK-DAG: test.o: MD5=[[TEST4_MD5]]
>  ^
> :21:1: note: scanning from here
> thread 0: fetched 
> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o
> ^
> :21:1: note: with variable "TEST4_MD5" equal to 
> "c32902f17598124702a017fac0e9b86d"
> thread 0: fetched 
> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o
> ^
> :26:161: note: possible intended match here
> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o:
>  MD5=e888cbc861bdeaaf786df90c4e5a40da
>   
>   
>^
> /Volumes/precious/cvs/swift-github/swift/test/IRGen/module_hash.swift:59:15:
>  error: expected string not found in input
> // CHECK-DAG: test.o: prev MD5=[[TEST4_MD5]] skipping
>  ^
> :30:1: note: scanning from here
> thread 0: fetched 
> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o
> ^
> :30:1: note: with variable "TEST4_MD5" equal to 
> "c32902f17598124702a017fac0e9b86d"
> thread 0: fetched 
> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o
> ^
> :35:161: note: possible intended match here
> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o:
>  prev MD5=e888cbc861bdeaaf786df90c4e5a40da recompiling
>   
>   
>^
> 
> 
> 
> single-threaded initial
> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o:
>  MD5=bbfcd715eee1f17799113c1826dfe124
> single-threaded same compilation
> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o:
>  MD5=bbfcd715eee1f17799113c1826dfe124
> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o:
>  prev MD5=bbfcd715eee1f17799113c1826dfe124 skipping
> single-threaded file changed
> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o:
>  MD5=bd6e3d5aef7c83992235017dacea08a9
> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_6

Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift Incremental RA - OS X (master) #3504

[Greg Parker via swift-dev]

Disabling the pass that way may have caused two more SILOptimizer test failures:
https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/4351/ 


I also suspect that the ArrayTraps failure is caused by something in the RR 
motion branch, but I'm still working to confirm that.


> On Apr 19, 2016, at 9:45 PM, Xin Tong  wrote:
> 
> Done in commit c2e8c81227263c9947f0ee0b8f9f6689d5e7bd21 , I have some commit 
> on top of this one, so reverting is not very easy.
> -Xin
> 
>> On Apr 19, 2016, at 9:40 PM, Greg Parker > > wrote:
>> 
>> Thanks. I'll try that.
>> 
>> 
>>> On Apr 19, 2016, at 9:35 PM, Xin Tong >> > wrote:
>>> 
>>> I will check in something to disable the pass.
>>> 
>>> -Xin
>>> 
>>> 
>>> 
 On Apr 19, 2016, at 9:34 PM, Greg Parker >>> > wrote:
 
 Looks like it was caused by the RR code motion merge 
 (https://github.com/apple/swift/pull/2064 
 ). 
 
 Xin, I'm planning to revert 49f1c66d7b20b29097d7aec99835c5a42a2048bf and 
 3824a9479ed2df701d4a0c9467495a4c37f0 once my tests finish, unless you 
 have a fix in the next few minutes.
 
 
> On Apr 19, 2016, at 8:50 PM, Erik Eckstein  > wrote:
> 
> This looks like there is some kind of non-determinism in the compilation.
> 
>> On Apr 19, 2016, at 8:14 PM, Greg Parker > > wrote:
>> 
>> 
>>> On Apr 19, 2016, at 12:45 PM, no-re...@swift.org 
>>>  wrote:
>>> 
>>> [FAILURE] oss-swift-incremental-RA-osx [#3504]
>>> 
>>> Tests: 
>>> 
>>> Name: Swift
>>> Failed: 1 test(s), Passed: 7808 test(s), Total: 7809 test(s)
>>> • Failed: Swift.IRGen.module_hash.swift
>>> 
>> 
>> This may be an older failure recently uncovered by changes to which 
>> tests get run. Jordan, Erik, any guesses of changes that might have 
>> broken it?
>> 
>> Errors and recorded output below:
>> 
>> /Volumes/precious/cvs/swift-github/swift/test/IRGen/module_hash.swift:49:15:
>>  error: expected string not found in input
>> // CHECK-DAG: test.o: MD5=[[TEST4_MD5]]
>>  ^
>> :21:1: note: scanning from here
>> thread 0: fetched 
>> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o
>> ^
>> :21:1: note: with variable "TEST4_MD5" equal to 
>> "c32902f17598124702a017fac0e9b86d"
>> thread 0: fetched 
>> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o
>> ^
>> :26:161: note: possible intended match here
>> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o:
>>  MD5=e888cbc861bdeaaf786df90c4e5a40da
>>  
>>  
>>  ^
>> /Volumes/precious/cvs/swift-github/swift/test/IRGen/module_hash.swift:59:15:
>>  error: expected string not found in input
>> // CHECK-DAG: test.o: prev MD5=[[TEST4_MD5]] skipping
>>  ^
>> :30:1: note: scanning from here
>> thread 0: fetched 
>> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o
>> ^
>> :30:1: note: with variable "TEST4_MD5" equal to 
>> "c32902f17598124702a017fac0e9b86d"
>> thread 0: fetched 
>> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o
>> ^
>> :35:161: note: possible intended match here
>> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o:
>>  prev MD5=e888cbc861bdeaaf786df90c4e5a40da recompiling
>>  
>>  
>>  ^
>> 
>> 
>> 
>> single-threaded initial
>> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o:
>>  MD5=bbfcd715eee1f17799113c1826dfe124
>> single-threaded same compilation
>> /Volumes/precious/cvs/swift-githu

Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift Incremental RA - OS X (master) #3504

[Xin Tong via swift-dev]

> On Apr 19, 2016, at 10:00 PM, Greg Parker  wrote:
> 
> Disabling the pass that way may have caused two more SILOptimizer test 
> failures:
> https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/4351/ 
> 
I am fixing the problem now. 
> 
> I also suspect that the ArrayTraps failure is caused by something in the RR 
> motion branch, but I'm still working to confirm that.

I do not think so.

https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-14_04/4240/ 


-Xin 

> 
> 
>> On Apr 19, 2016, at 9:45 PM, Xin Tong > > wrote:
>> 
>> Done in commit c2e8c81227263c9947f0ee0b8f9f6689d5e7bd21 , I have some commit 
>> on top of this one, so reverting is not very easy.
>> -Xin
>> 
>>> On Apr 19, 2016, at 9:40 PM, Greg Parker >> > wrote:
>>> 
>>> Thanks. I'll try that.
>>> 
>>> 
 On Apr 19, 2016, at 9:35 PM, Xin Tong >>> > wrote:
 
 I will check in something to disable the pass.
 
 -Xin
 
 
 
> On Apr 19, 2016, at 9:34 PM, Greg Parker  > wrote:
> 
> Looks like it was caused by the RR code motion merge 
> (https://github.com/apple/swift/pull/2064 
> ). 
> 
> Xin, I'm planning to revert 49f1c66d7b20b29097d7aec99835c5a42a2048bf and 
> 3824a9479ed2df701d4a0c9467495a4c37f0 once my tests finish, unless you 
> have a fix in the next few minutes.
> 
> 
>> On Apr 19, 2016, at 8:50 PM, Erik Eckstein > > wrote:
>> 
>> This looks like there is some kind of non-determinism in the compilation.
>> 
>>> On Apr 19, 2016, at 8:14 PM, Greg Parker >> > wrote:
>>> 
>>> 
 On Apr 19, 2016, at 12:45 PM, no-re...@swift.org 
  wrote:
 
 [FAILURE] oss-swift-incremental-RA-osx [#3504]
 
 Tests: 
 
 Name: Swift
 Failed: 1 test(s), Passed: 7808 test(s), Total: 7809 test(s)
• Failed: Swift.IRGen.module_hash.swift
 
>>> 
>>> This may be an older failure recently uncovered by changes to which 
>>> tests get run. Jordan, Erik, any guesses of changes that might have 
>>> broken it?
>>> 
>>> Errors and recorded output below:
>>> 
>>> /Volumes/precious/cvs/swift-github/swift/test/IRGen/module_hash.swift:49:15:
>>>  error: expected string not found in input
>>> // CHECK-DAG: test.o: MD5=[[TEST4_MD5]]
>>>  ^
>>> :21:1: note: scanning from here
>>> thread 0: fetched 
>>> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o
>>> ^
>>> :21:1: note: with variable "TEST4_MD5" equal to 
>>> "c32902f17598124702a017fac0e9b86d"
>>> thread 0: fetched 
>>> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o
>>> ^
>>> :26:161: note: possible intended match here
>>> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o:
>>>  MD5=e888cbc861bdeaaf786df90c4e5a40da
>>> 
>>> 
>>>^
>>> /Volumes/precious/cvs/swift-github/swift/test/IRGen/module_hash.swift:59:15:
>>>  error: expected string not found in input
>>> // CHECK-DAG: test.o: prev MD5=[[TEST4_MD5]] skipping
>>>  ^
>>> :30:1: note: scanning from here
>>> thread 0: fetched 
>>> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o
>>> ^
>>> :30:1: note: with variable "TEST4_MD5" equal to 
>>> "c32902f17598124702a017fac0e9b86d"
>>> thread 0: fetched 
>>> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o
>>> ^
>>> :35:161: note: possible intended match here
>>> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o:
>>>  prev MD5=e888cbc861bdeaaf786df90c4e5a40da recompiling
>>> 
>>> 

Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift Incremental RA - OS X (master) #3504

[Xin Tong via swift-dev]

> On Apr 19, 2016, at 10:03 PM, Xin Tong via swift-dev  
> wrote:
> 
> 
>> On Apr 19, 2016, at 10:00 PM, Greg Parker > > wrote:
>> 
>> Disabling the pass that way may have caused two more SILOptimizer test 
>> failures:
>> https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/4351/ 
>> 
> I am fixing the problem now. 
>> 
>> I also suspect that the ArrayTraps failure is caused by something in the RR 
>> motion branch, but I'm still working to confirm that.
> 
> I do not think so.
> 
> https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-14_04/4240/ 
> 
I meant if you look into the console output, the array test is still failing 
with RRcodemotion disabled.
> 
> -Xin 
> 
>> 
>> 
>>> On Apr 19, 2016, at 9:45 PM, Xin Tong >> > wrote:
>>> 
>>> Done in commit c2e8c81227263c9947f0ee0b8f9f6689d5e7bd21 , I have some 
>>> commit on top of this one, so reverting is not very easy.
>>> -Xin
>>> 
 On Apr 19, 2016, at 9:40 PM, Greg Parker >>> > wrote:
 
 Thanks. I'll try that.
 
 
> On Apr 19, 2016, at 9:35 PM, Xin Tong  > wrote:
> 
> I will check in something to disable the pass.
> 
> -Xin
> 
> 
> 
>> On Apr 19, 2016, at 9:34 PM, Greg Parker > > wrote:
>> 
>> Looks like it was caused by the RR code motion merge 
>> (https://github.com/apple/swift/pull/2064 
>> ). 
>> 
>> Xin, I'm planning to revert 49f1c66d7b20b29097d7aec99835c5a42a2048bf and 
>> 3824a9479ed2df701d4a0c9467495a4c37f0 once my tests finish, unless 
>> you have a fix in the next few minutes.
>> 
>> 
>>> On Apr 19, 2016, at 8:50 PM, Erik Eckstein >> > wrote:
>>> 
>>> This looks like there is some kind of non-determinism in the 
>>> compilation.
>>> 
 On Apr 19, 2016, at 8:14 PM, Greg Parker >>> > wrote:
 
 
> On Apr 19, 2016, at 12:45 PM, no-re...@swift.org 
>  wrote:
> 
> [FAILURE] oss-swift-incremental-RA-osx [#3504]
> 
> Tests: 
> 
> Name: Swift
> Failed: 1 test(s), Passed: 7808 test(s), Total: 7809 test(s)
>   • Failed: Swift.IRGen.module_hash.swift
> 
 
 This may be an older failure recently uncovered by changes to which 
 tests get run. Jordan, Erik, any guesses of changes that might have 
 broken it?
 
 Errors and recorded output below:
 
 /Volumes/precious/cvs/swift-github/swift/test/IRGen/module_hash.swift:49:15:
  error: expected string not found in input
 // CHECK-DAG: test.o: MD5=[[TEST4_MD5]]
  ^
 :21:1: note: scanning from here
 thread 0: fetched 
 /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o
 ^
 :21:1: note: with variable "TEST4_MD5" equal to 
 "c32902f17598124702a017fac0e9b86d"
 thread 0: fetched 
 /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o
 ^
 :26:161: note: possible intended match here
 /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o:
  MD5=e888cbc861bdeaaf786df90c4e5a40da


  ^
 /Volumes/precious/cvs/swift-github/swift/test/IRGen/module_hash.swift:59:15:
  error: expected string not found in input
 // CHECK-DAG: test.o: prev MD5=[[TEST4_MD5]] skipping
  ^
 :30:1: note: scanning from here
 thread 0: fetched 
 /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o
 ^
 :30:1: note: with variable "TEST4_MD5" equal to 
 "c32902f17598124702a017fac0e9b86d"
 thread 0: fetched 
 /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o
 ^
 :35:161: note: possible intended match here
 /Volumes/precious/cvs/

Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift Incremental RA - OS X (master) #3504

[Xin Tong via swift-dev]

To summarize. I think I fixed the non-determinism in commit 
7d26a472009eae673fd40a0403ceb319027481be and re-enabled retain release code 
motion (RRCM).

I do not think the array test failure is related to RRCM , the benchmark failed 
even after i disabled RRCM.

https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-14_04/4240/ 

https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/4351/ 


-Xin

> On Apr 19, 2016, at 10:05 PM, Xin Tong  wrote:
> 
> 
>> On Apr 19, 2016, at 10:03 PM, Xin Tong via swift-dev > > wrote:
>> 
>> 
>>> On Apr 19, 2016, at 10:00 PM, Greg Parker >> > wrote:
>>> 
>>> Disabling the pass that way may have caused two more SILOptimizer test 
>>> failures:
>>> https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/4351/ 
>>> 
>> I am fixing the problem now. 
>>> 
>>> I also suspect that the ArrayTraps failure is caused by something in the RR 
>>> motion branch, but I'm still working to confirm that.
>> 
>> I do not think so.
>> 
>> https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-14_04/4240/ 
>> 
> I meant if you look into the console output, the array test is still failing 
> with RRcodemotion disabled.
>> 
>> -Xin 
>> 
>>> 
>>> 
 On Apr 19, 2016, at 9:45 PM, Xin Tong >>> > wrote:
 
 Done in commit c2e8c81227263c9947f0ee0b8f9f6689d5e7bd21 , I have some 
 commit on top of this one, so reverting is not very easy.
 -Xin
 
> On Apr 19, 2016, at 9:40 PM, Greg Parker  > wrote:
> 
> Thanks. I'll try that.
> 
> 
>> On Apr 19, 2016, at 9:35 PM, Xin Tong > > wrote:
>> 
>> I will check in something to disable the pass.
>> 
>> -Xin
>> 
>> 
>> 
>>> On Apr 19, 2016, at 9:34 PM, Greg Parker >> > wrote:
>>> 
>>> Looks like it was caused by the RR code motion merge 
>>> (https://github.com/apple/swift/pull/2064 
>>> ). 
>>> 
>>> Xin, I'm planning to revert 49f1c66d7b20b29097d7aec99835c5a42a2048bf 
>>> and 3824a9479ed2df701d4a0c9467495a4c37f0 once my tests finish, 
>>> unless you have a fix in the next few minutes.
>>> 
>>> 
 On Apr 19, 2016, at 8:50 PM, Erik Eckstein >>> > wrote:
 
 This looks like there is some kind of non-determinism in the 
 compilation.
 
> On Apr 19, 2016, at 8:14 PM, Greg Parker  > wrote:
> 
> 
>> On Apr 19, 2016, at 12:45 PM, no-re...@swift.org 
>>  wrote:
>> 
>> [FAILURE] oss-swift-incremental-RA-osx [#3504]
>> 
>> Tests: 
>> 
>> Name: Swift
>> Failed: 1 test(s), Passed: 7808 test(s), Total: 7809 test(s)
>>  • Failed: Swift.IRGen.module_hash.swift
>> 
> 
> This may be an older failure recently uncovered by changes to which 
> tests get run. Jordan, Erik, any guesses of changes that might have 
> broken it?
> 
> Errors and recorded output below:
> 
> /Volumes/precious/cvs/swift-github/swift/test/IRGen/module_hash.swift:49:15:
>  error: expected string not found in input
> // CHECK-DAG: test.o: MD5=[[TEST4_MD5]]
>  ^
> :21:1: note: scanning from here
> thread 0: fetched 
> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o
> ^
> :21:1: note: with variable "TEST4_MD5" equal to 
> "c32902f17598124702a017fac0e9b86d"
> thread 0: fetched 
> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o
> ^
> :26:161: note: possible intended match here
> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o:
>  MD5=e888cbc861bdeaaf786df90c4e5a40da
>   
>   
>^
> /Volumes/precious/cvs/swift-github/swift/test/IRGen/module_hash.swift:59:15:
>  error: expected

Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift Incremental RA - OS X (master) #3504

[Greg Parker via swift-dev]

Looks good. Thanks.

I agree about the array failure. I mistakenly considered an OS X test in that 
diagnosis, but the test isn't failing anywhere on OS X.


> On Apr 19, 2016, at 10:35 PM, Xin Tong  wrote:
> 
> To summarize. I think I fixed the non-determinism in commit 
> 7d26a472009eae673fd40a0403ceb319027481be and re-enabled retain release code 
> motion (RRCM).
> 
> I do not think the array test failure is related to RRCM , the benchmark 
> failed even after i disabled RRCM.
> 
> https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-14_04/4240/ 
> 
> https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/4351/ 
> 
> 
> -Xin
> 
>> On Apr 19, 2016, at 10:05 PM, Xin Tong > > wrote:
>> 
>> 
>>> On Apr 19, 2016, at 10:03 PM, Xin Tong via swift-dev >> > wrote:
>>> 
>>> 
 On Apr 19, 2016, at 10:00 PM, Greg Parker >>> > wrote:
 
 Disabling the pass that way may have caused two more SILOptimizer test 
 failures:
 https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/4351/ 
 
>>> I am fixing the problem now. 
 
 I also suspect that the ArrayTraps failure is caused by something in the 
 RR motion branch, but I'm still working to confirm that.
>>> 
>>> I do not think so.
>>> 
>>> https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-14_04/4240/ 
>>> 
>> I meant if you look into the console output, the array test is still failing 
>> with RRcodemotion disabled.
>>> 
>>> -Xin 
>>> 
 
 
> On Apr 19, 2016, at 9:45 PM, Xin Tong  > wrote:
> 
> Done in commit c2e8c81227263c9947f0ee0b8f9f6689d5e7bd21 , I have some 
> commit on top of this one, so reverting is not very easy.
> -Xin
> 
>> On Apr 19, 2016, at 9:40 PM, Greg Parker > > wrote:
>> 
>> Thanks. I'll try that.
>> 
>> 
>>> On Apr 19, 2016, at 9:35 PM, Xin Tong >> > wrote:
>>> 
>>> I will check in something to disable the pass.
>>> 
>>> -Xin
>>> 
>>> 
>>> 
 On Apr 19, 2016, at 9:34 PM, Greg Parker >>> > wrote:
 
 Looks like it was caused by the RR code motion merge 
 (https://github.com/apple/swift/pull/2064 
 ). 
 
 Xin, I'm planning to revert 49f1c66d7b20b29097d7aec99835c5a42a2048bf 
 and 3824a9479ed2df701d4a0c9467495a4c37f0 once my tests finish, 
 unless you have a fix in the next few minutes.
 
 
> On Apr 19, 2016, at 8:50 PM, Erik Eckstein  > wrote:
> 
> This looks like there is some kind of non-determinism in the 
> compilation.
> 
>> On Apr 19, 2016, at 8:14 PM, Greg Parker > > wrote:
>> 
>> 
>>> On Apr 19, 2016, at 12:45 PM, no-re...@swift.org 
>>>  wrote:
>>> 
>>> [FAILURE] oss-swift-incremental-RA-osx [#3504]
>>> 
>>> Tests: 
>>> 
>>> Name: Swift
>>> Failed: 1 test(s), Passed: 7808 test(s), Total: 7809 test(s)
>>> • Failed: Swift.IRGen.module_hash.swift
>>> 
>> 
>> This may be an older failure recently uncovered by changes to which 
>> tests get run. Jordan, Erik, any guesses of changes that might have 
>> broken it?
>> 
>> Errors and recorded output below:
>> 
>> /Volumes/precious/cvs/swift-github/swift/test/IRGen/module_hash.swift:49:15:
>>  error: expected string not found in input
>> // CHECK-DAG: test.o: MD5=[[TEST4_MD5]]
>>  ^
>> :21:1: note: scanning from here
>> thread 0: fetched 
>> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o
>> ^
>> :21:1: note: with variable "TEST4_MD5" equal to 
>> "c32902f17598124702a017fac0e9b86d"
>> thread 0: fetched 
>> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module_hash.swift.tmp/test.o
>> ^
>> :26:161: note: possible intended match here
>> /Volumes/precious/cvs/swift-github/build/Ninja-RelWithDebInfoAssert+stdlib-DebugAssert/swift-macosx-x86_64/test-macosx-x86_64/IRGen/Output/module