<html><body><p>I would like to see if the community is interested in the ability for Swift libraries (when built with Swift Package Manager) to be aware of the current tagged version number applied on that library during compilation. This could be useful for when the executable is run, we can know the version of that library dependency so that we can dump that information out to our logs. Perhaps some macro like #file or #line, but something like #version. <br><br><br><br><br><img width="16" height="16" src="cid:2__=09BBF50ADFF003FF8f9e8a93df938690918c09B@" border="0" alt="Inactive hide details for swift-dev-request---04/18/2016 11:57:30 AM---Send swift-dev mailing list submissions to swift-dev@sw"><font color="#424282">swift-dev-request---04/18/2016 11:57:30 AM---Send swift-dev mailing list submissions to swift-dev@swift.org</font><br><br><font size="2" color="#5F5F5F">From: </font><font size="2">swift-dev-request@swift.org</font><br><font size="2" color="#5F5F5F">To: </font><font size="2">swift-dev@swift.org</font><br><font size="2" color="#5F5F5F">Date: </font><font size="2">04/18/2016 11:57 AM</font><br><font size="2" color="#5F5F5F">Subject: </font><font size="2">swift-dev Digest, Vol 5, Issue 18</font><br><font size="2" color="#5F5F5F">Sent by: </font><font size="2">swift-dev-bounces@swift.org</font><br><hr width="100%" size="2" align="left" noshade style="color:#8091A5; "><br><br><br><tt>Send swift-dev mailing list submissions to<br> swift-dev@swift.org<br><br>To subscribe or unsubscribe via the World Wide Web, visit<br> </tt><tt><a href="https://lists.swift.org/mailman/listinfo/swift-dev">https://lists.swift.org/mailman/listinfo/swift-dev</a></tt><tt><br>or, via email, send a message with subject or body 'help' to<br> swift-dev-request@swift.org<br><br>You can reach the person managing the list at<br> swift-dev-owner@swift.org<br><br>When replying, please edit your Subject line so it is more specific<br>than "Re: Contents of swift-dev digest..."<br><br><br>Today's Topics:<br><br> 1. Re: [SR-710][RFC] Automatically detecting XCTest test methods<br> on Linux: Reflection? SourceKit? (Brian Gesiak)<br> 2. Re: R_ARM_GOT_PREL error when building Swift on Pi from<br> source (Timothy Wood)<br> 3. Re: R_ARM_GOT_PREL error when building Swift on Pi from<br> source (Joe Bell)<br> 4. Re: R_ARM_GOT_PREL error when building Swift on Pi from<br> source (Timothy Wood)<br> 5. Random failure when building Swift on Pi (Timothy Wood)<br> 6. Re: [SR-710][RFC] Automatically detecting XCTest test methods<br> on Linux: Reflection? SourceKit? (Drew Crawford)<br> 7. Re: R_ARM_GOT_PREL error when building Swift on Pi from<br> source (Timothy Wood)<br> 8. SIMD in open source Swift? (Geordie Jay)<br> 9. Re: [Swift CI] Build Failure: 0. OSS - Swift Incremental RA -<br> Ubuntu 15.10 (master) #4254 (Sean Callanan)<br> 10. Re: [Swift CI] Build Failure: 0. OSS - Swift Incremental RA -<br> Ubuntu 15.10 (master) #4254 (Sean Callanan)<br> 11. Re: [Swift CI] Build Failure: 0. OSS - Swift Incremental RA -<br> OS X (master) #3432 (Sean Callanan)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Sun, 17 Apr 2016 14:36:08 -0400<br>From: Brian Gesiak <modocache@gmail.com><br>To: Daniel Dunbar <daniel_dunbar@apple.com><br>Cc: swift-dev <swift-dev@swift.org><br>Subject: Re: [swift-dev] [SR-710][RFC] Automatically detecting XCTest<br> test methods on Linux: Reflection? SourceKit?<br>Message-ID:<br> <CAN7MxmX3aeuCK3TQepC5cwJ+hzVK8v1FXQQwiqEt5c0tqF7t+A@mail.gmail.com><br>Content-Type: text/plain; charset="utf-8"<br><br>In case anyone interested missed it, John Holdsworth mentions another<br>approach in a comment on </tt><tt><a href="https://bugs.swift.org/browse/SR-710:">https://bugs.swift.org/browse/SR-710:</a></tt><tt> using<br>runtime metadata to find a list of tests. The linked project contains an<br>example. It:<br><br>1. Specifies a test method regex:<br></tt><tt><a href="https://github.com/johnno1962/TestRunner/blob/201bd04af14fdebf1a7fa2ae0a419fc59d6266ed/TestRunner/AppDelegate.swift#L69">https://github.com/johnno1962/TestRunner/blob/201bd04af14fdebf1a7fa2ae0a419fc59d6266ed/TestRunner/AppDelegate.swift#L69</a></tt><tt><br>2. In Swift, the project exposes metadata information for Swift objects:<br></tt><tt><a href="https://github.com/johnno1962/TestRunner/blob/201bd04af14fdebf1a7fa2ae0a419fc59d6266ed/TestRunner/TestRunner.swift#L52">https://github.com/johnno1962/TestRunner/blob/201bd04af14fdebf1a7fa2ae0a419fc59d6266ed/TestRunner/TestRunner.swift#L52</a></tt><tt><br>3. Uses an UnsafeMutablePointer<ClassMetadataSwift> to get a reference to<br>the methods defined on an instance:<br></tt><tt><a href="https://github.com/johnno1962/TestRunner/blob/201bd04af14fdebf1a7fa2ae0a419fc59d6266ed/TestRunner/TestRunner.swift#L97">https://github.com/johnno1962/TestRunner/blob/201bd04af14fdebf1a7fa2ae0a419fc59d6266ed/TestRunner/TestRunner.swift#L97</a></tt><tt><br><br>I assume this approach won't be acceptable to some because it relies on<br>private information about Swift objects, but I don't know for sure. Please<br>chime in if this approach seems reasonable to you!<br><br>Based on the assumption that we can't use metadata, however, I'm going to<br>try to begin working on approaches #2 or #3, which I mentioned in my<br>original email. I think the preliminary work is the same (like<br>moving SourceKit::FuncDeclEntityInfo.IsTestCandidate to libIDE), so I'll<br>hold off on making a hard decision between #2 and #3 until necessary.<br><br>- Brian Gesiak<br><br><br>On Mon, Apr 4, 2016 at 12:23 AM, Daniel Dunbar <daniel_dunbar@apple.com><br>wrote:<br><br>><br>> > On Apr 3, 2016, at 3:36 PM, Dmitri Gribenko <gribozavr@gmail.com> wrote:<br>> ><br>> > On Sun, Apr 3, 2016 at 2:11 PM, Brian Gesiak <modocache@gmail.com><br>> wrote:<br>> >> I think #2 is the best option. It’s less work than both #1 and #3. I<br>> believe<br>> >> logic like IsTestCandidate belongs in libIDE anyway—SourceKit should<br>> stick<br>> >> to XPC and asynchronous communication with libIDE.<br>> ><br>> > I like #3 better (an option to swiftc), because that would decouple<br>> > the test discovery tool from the Swift compiler. That would allow you<br>> > to use the discovery tool with different compilers. And, because we<br>> > would avoid statically linking libIDE, it would mean one less copy of<br>> > LLVM, Clang and Swift in the toolchain.<br>><br>> Ultimately my opinion is that it is likely that the package manager will<br>> want an API interface to Swift in any case. I personally would rather we<br>> simply plan on that.<br>><br>> I also would like to avoid duplicating anything in the toolchain, but<br>> think that should be done by moving the driver to sitting on top of a<br>> shared library.<br>><br>> >> Not being an expert in many of these components, I have several<br>> questions:<br>> >><br>> >> I’m assuming the reflection API to return a list of instance methods on<br>> a<br>> >> XCTestCase subclass is not ready yet, and won’t be for some time. Is<br>> this<br>> >> accurate?<br>> ><br>> > I think so.<br>> ><br>> >> I’m assuming that SourceKit is intended to be an asynchronous wrapper<br>> over<br>> >> libIDE, and that logic like IsTestCandidate should be moved to libIDE.<br>> Is<br>> >> this accurate?<br>> ><br>> > SourceKit has a lot of functionality of its own, but moving this<br>> > particular piece of logic to libIDE sounds reasonable.<br>> ><br>> >> I’m assuming that SourceKit is coupled with XPC, and that it would be<br>> more<br>> >> work to port it to Linux than it would be to move its logic to libIDE.<br>> Is<br>> >> this accurate?<br>> ><br>> > It is not tightly coupled with XPC, there is a portability layer that<br>> > you could implement for Linux. You would need to decide on an IPC<br>> > mechanism and serialization format though.<br>><br>> For our purposes, I don't think we need IPC. I think a direct (C) library<br>> interface would be fine. Clients can implement the IPC/XPC if they need it.<br>><br>> >> If you have thoughts/feedback, please reply to this email or comment on<br>> >> SR-710. Your input would be greatly appreciated!!<br>> ><br>> > I'm wondering how feasible is it to change the XCTest API to<br>> > accommodate better the Swift language that we have, rather than trying<br>> > to add custom tooling to make the existing API work. Adding magic<br>> > tooling that adds behavior not present in the language seems unnatural<br>> > to me.<br>><br>> I agree with you that it is unnatural, but I think this ship has sailed<br>> for XCTest, we have a need to support the existing API in a cross platform<br>> manner.<br>><br>> My personal preference is that eventually we would build features like<br>> this on top of general support for attributes (a la Java/Python/C#).<br>><br>> > Compare with StdlibUnittest -- by using an API to build tests we get<br>> > the following advantages:<br>> ><br>> > - We completely avoid having the issue of test discovery, executing<br>> > the code discovers the tests. No reflection needed!<br>><br>> While I think StdlibUnittest is neat, I also believe that there are very<br>> good reasons for supporting test discovery in a test suite. I have used<br>> these features in other suites to great avail to create (bidirectional,<br>> sometimes) lit bridge adaptors between various test frameworks (Python<br>> unittest, googletest, XCTest).<br>><br>> In an IDE context, it is also very useful to be able to perform test<br>> discovery independent of test execution.<br>><br>> As one other example, I've used lit with suites with hundreds of thousands<br>> of tests... it would be unfortunate to have to dynamically discover all of<br>> those tests when the user is just trying to run a single one.<br>><br>> > - We can add attributes to tests (for example, skip, xfail). In the<br>> > current XCTest API this would require adding some kind of user-defined<br>> > attributes, which is another language which is a long way from being<br>> > designed and implemented.<br>><br>> This isn't necessarily the case, XCTest could in theory provide explicit<br>> APIs to do these things as part of test execution. I agree attributes are a<br>> better fit in the current model.<br>><br>> > - We can define data-parameterized tests.<br>><br>> > - Tests can be dynamically synthesized by control flow. In the<br>> > current XCTest API, dynamically generating tests would mean<br>> > dynamically generating methods, which is even more far off than<br>> > read-only method reflection.<br>><br>> FWIW, XCTest has some support for doing these kinds of things, they just<br>> don't take the form of the pattern-matched methods.<br>><br>> - Daniel<br>><br>> ><br>> > Dmitri<br>> ><br>> > --<br>> > main(i,j){for(i=2;;i++){for(j=2;j<i;j++){if(!(i%j)){j=0;break;}}if<br>> > (j){printf("%d\n",i);}}} /*Dmitri Gribenko <gribozavr@gmail.com>*/<br>><br>><br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <</tt><tt><a href="https://lists.swift.org/pipermail/swift-dev/attachments/20160417/1346eb08/attachment-0001.html">https://lists.swift.org/pipermail/swift-dev/attachments/20160417/1346eb08/attachment-0001.html</a></tt><tt>><br><br>------------------------------<br><br>Message: 2<br>Date: Sun, 17 Apr 2016 13:46:33 -0700<br>From: Timothy Wood <tjw@omnigroup.com><br>To: William Dillon <william@housedillon.com><br>Cc: Kenny Leung via swift-dev <swift-dev@swift.org><br>Subject: Re: [swift-dev] R_ARM_GOT_PREL error when building Swift on<br> Pi from source<br>Message-ID: <29ABC0C6-92D9-4A67-ABD0-4CDDE2F5C45E@omnigroup.com><br>Content-Type: text/plain; charset="utf-8"<br><br><br>> On Apr 16, 2016, at 2:23 PM, William Dillon <william@housedillon.com> wrote:<br>> <br>> What LLVM are you using?<br>> <br>> You have to use the one from my github (and the arm branch) or it won't work:<br>> <br>> </tt><tt><a href="https://github.com/hpux735/swift-llvm/tree/arm">https://github.com/hpux735/swift-llvm/tree/arm</a></tt><tt> <</tt><tt><a href="https://github.com/hpux735/swift-llvm/tree/arm">https://github.com/hpux735/swift-llvm/tree/arm</a></tt><tt>> <br>> <br>> I haven't had time to upstream the changes to LLVM.<br>> <br>> - Will<br><br><br>Ah, thanks! I was using <</tt><tt><a href="https://github.com/apple/swift-llvm/tree/swift-2.2-branch">https://github.com/apple/swift-llvm/tree/swift-2.2-branch</a></tt><tt> <</tt><tt><a href="https://github.com/apple/swift-llvm/tree/swift-2.2-branch">https://github.com/apple/swift-llvm/tree/swift-2.2-branch</a></tt><tt>>>, but will give your fork a try!<br><br>-tim<br><br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <</tt><tt><a href="https://lists.swift.org/pipermail/swift-dev/attachments/20160417/5349c220/attachment-0001.html">https://lists.swift.org/pipermail/swift-dev/attachments/20160417/5349c220/attachment-0001.html</a></tt><tt>><br><br>------------------------------<br><br>Message: 3<br>Date: Sun, 17 Apr 2016 15:52:20 -0500<br>From: Joe Bell <joe@iachieved.it><br>To: Timothy Wood <tjw@omnigroup.com><br>Cc: Kenny Leung via swift-dev <swift-dev@swift.org><br>Subject: Re: [swift-dev] R_ARM_GOT_PREL error when building Swift on<br> Pi from source<br>Message-ID: <5D20A476-5349-426C-B884-49E202631D80@iachieved.it><br>Content-Type: text/plain; charset="utf-8"<br><br>I'll join in Tim and try compiling again on the BeagleX15, it failed the other day but I forgot about using Wills LLVM<br><br>Joe<br><br>> On Apr 17, 2016, at 3:46 PM, Timothy Wood via swift-dev <swift-dev@swift.org> wrote:<br>> <br>> <br>>> On Apr 16, 2016, at 2:23 PM, William Dillon <william@housedillon.com> wrote:<br>>> <br>>> What LLVM are you using?<br>>> <br>>> You have to use the one from my github (and the arm branch) or it won't work:<br>>> <br>>> </tt><tt><a href="https://github.com/hpux735/swift-llvm/tree/arm">https://github.com/hpux735/swift-llvm/tree/arm</a></tt><tt> <br>>> <br>>> I haven't had time to upstream the changes to LLVM.<br>>> <br>>> - Will<br>> <br>> <br>> Ah, thanks! I was using <</tt><tt><a href="https://github.com/apple/swift-llvm/tree/swift-2.2-branch">https://github.com/apple/swift-llvm/tree/swift-2.2-branch</a></tt><tt>>, but will give your fork a try!<br>> <br>> -tim<br>> <br>> _______________________________________________<br>> swift-dev mailing list<br>> swift-dev@swift.org<br>> </tt><tt><a href="https://lists.swift.org/mailman/listinfo/swift-dev">https://lists.swift.org/mailman/listinfo/swift-dev</a></tt><tt><br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <</tt><tt><a href="https://lists.swift.org/pipermail/swift-dev/attachments/20160417/ac2ace8e/attachment-0001.html">https://lists.swift.org/pipermail/swift-dev/attachments/20160417/ac2ace8e/attachment-0001.html</a></tt><tt>><br><br>------------------------------<br><br>Message: 4<br>Date: Sun, 17 Apr 2016 13:55:31 -0700<br>From: Timothy Wood <tjw@omnigroup.com><br>To: Joe Groff <jgroff@apple.com><br>Cc: swift-dev@swift.org<br>Subject: Re: [swift-dev] R_ARM_GOT_PREL error when building Swift on<br> Pi from source<br>Message-ID: <FFDED274-9542-4266-A319-DAD6B10184CC@omnigroup.com><br>Content-Type: text/plain; charset=utf-8<br><br><br>> On Apr 15, 2016, at 6:45 PM, Joe Groff <jgroff@apple.com> wrote:<br>> What linker are you using? GNU ld 2.26 in particular changed the behavior of protected visibility in a way that's incompatible with our usage, and we haven't fully implemented a workaround. You might try using gold or an older binutils, if that's what you're currently using.<br><br>I could have sworn I was using gold, but looking at my logs it was using the standard linker. Perhaps I’m remembering an attempt from the Swift 3 sources… Anyway, my current attempts are using this invocation now (though I’m getting other failures now):<br><br> utils/build-script -t -R -j 4 -- --use-gold-linker<br><br>Thanks!<br><br>-tim<br><br><br><br>------------------------------<br><br>Message: 5<br>Date: Sun, 17 Apr 2016 13:55:35 -0700<br>From: Timothy Wood <tjw@me.com><br>To: swift-dev@swift.org<br>Subject: [swift-dev] Random failure when building Swift on Pi<br>Message-ID: <6904C5F0-0395-48B7-9092-8117D82342BE@me.com><br>Content-Type: text/plain; charset="utf-8"<br><br><br><br>I’m encountering random build compile failures when building on Pi, using clang-3.6 (as suggested in the various instructions to do so), and when using <</tt><tt><a href="https://github.com/hpux735/swift-llvm/tree/arm">https://github.com/hpux735/swift-llvm/tree/arm</a></tt><tt>><br><br>One example looks like:<br><br>FAILED: /usr/bin/clang++ -DGTEST_HAS_RTTI=0 -D_DEBUG -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -Ilib/Support -I/home/pi/Source/Swift/llvm/lib/Support -Iinclude -I/home/pi/Source/Swift/llvm/include -fno-stack-protector -fPIC -fvisibility-inlines-hidden -Wall -W -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wmissing-field-initializers -pedantic -Wno-long-long -Wcovered-switch-default -Wnon-virtual-dtor -Wdelete-non-virtual-dtor -std=c++11 -fcolor-diagnostics -ffunction-sections -fdata-sections -O3 -UNDEBUG -fno-exceptions -fno-rtti -MMD -MT lib/Support/CMakeFiles/LLVMSupport.dir/YAMLTraits.cpp.o -MF lib/Support/CMakeFiles/LLVMSupport.dir/YAMLTraits.cpp.o.d -o lib/Support/CMakeFiles/LLVMSupport.dir/YAMLTraits.cpp.o -c /home/pi/Source/Swift/llvm/lib/Support/YAMLTraits.cpp<br>Stack dump:<br>0. Program arguments: /usr/lib/llvm-3.6/bin/clang -cc1 -triple armv6-unknown-linux-gnueabihf -emit-obj -disable-free -disable-llvm-verifier -main-file-name YAMLTraits.cpp -mrelocation-model pic -pic-level 2 -mthread-model posix -mdisable-fp-elim -fmath-errno -masm-verbose -mconstructor-aliases -fuse-init-array -target-cpu arm1136jf-s -target-abi aapcs-linux -mfloat-abi hard -target-linker-version 2.25 -dwarf-column-info -ffunction-sections -fdata-sections -coverage-file /home/pi/Source/Swift/build/Ninja-ReleaseAssert/llvm-linux-armv7/lib/Support/CMakeFiles/LLVMSupport.dir/YAMLTraits.cpp.o -resource-dir /usr/lib/llvm-3.6/bin/../lib/clang/3.6.2 -dependency-file lib/Support/CMakeFiles/LLVMSupport.dir/YAMLTraits.cpp.o.d -MT lib/Support/CMakeFiles/LLVMSupport.dir/YAMLTraits.cpp.o -D GTEST_HAS_RTTI=0 -D _DEBUG -D _GNU_SOURCE -D __STDC_CONSTANT_MACROS -D __STDC_FORMAT_MACROS -D __STDC_LIMIT_MACROS -U NDEBUG -I lib/Support -I /home/pi/Source/Swift/llvm/lib/Support -I include -I /home/pi/Source/Swift/llvm/include -internal-isystem /usr/bin/../lib/gcc/arm-linux-gnueabihf/4.9/../../../../include/c++/4.9 -internal-isystem /usr/bin/../lib/gcc/arm-linux-gnueabihf/4.9/../../../../include/arm-linux-gnueabihf/c++/4.9 -internal-isystem /usr/bin/../lib/gcc/arm-linux-gnueabihf/4.9/../../../../include/arm-linux-gnueabihf/c++/4.9 -internal-isystem /usr/bin/../lib/gcc/arm-linux-gnueabihf/4.9/../../../../include/c++/4.9/backward -internal-isystem /usr/local/include -internal-isystem /usr/lib/llvm-3.6/bin/../lib/clang/3.6.2/include -internal-externc-isystem /usr/include/arm-linux-gnueabihf -internal-externc-isystem /include -internal-externc-isystem /usr/include -O3 -Wall -W -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wmissing-field-initializers -Wno-long-long -Wcovered-switch-default -Wnon-virtual-dtor -Wdelete-non-virtual-dtor -pedantic -std=c++11 -fdeprecated-macro -fdebug-compilation-dir /home/pi/Source/Swift/build/Ninja-ReleaseAssert/llvm-linux-armv7 -ferror-limit 19 -fmessage-length 0 -fvisibility-inlines-hidden -mstackrealign -fno-rtti -fno-signed-char -fobjc-runtime=gcc -fdiagnostics-show-option -fcolor-diagnostics -vectorize-loops -vectorize-slp -o lib/Support/CMakeFiles/LLVMSupport.dir/YAMLTraits.cpp.o -x c++ /home/pi/Source/Swift/llvm/lib/Support/YAMLTraits.cpp <br>1. /usr/bin/../lib/gcc/arm-linux-gnueabihf/4.9/../../../../include/c++/4.9/ext/type_traits.h:113:6: current parser token ';'<br>2. /usr/bin/../lib/gcc/arm-linux-gnueabihf/4.9/../../../../include/c++/4.9/ext/type_traits.h:37:1: parsing namespace '__gnu_cxx'<br>3. /usr/bin/../lib/gcc/arm-linux-gnueabihf/4.9/../../../../include/c++/4.9/ext/type_traits.h:106:5: parsing struct/union/class body '__remove_unsigned'<br>clang: error: unable to execute command: Segmentation fault<br>clang: error: clang frontend command failed due to signal (use -v to see invocation)<br>Debian clang version 3.6.2-3 (tags/RELEASE_362/final) (based on LLVM 3.6.2)<br>Target: arm-unknown-linux-gnueabihf<br>Thread model: posix<br>clang: note: diagnostic msg: PLEASE submit a bug report to </tt><tt><a href="http://bugs.debian.org/">http://bugs.debian.org/</a></tt><tt> and include the crash backtrace, preprocessed source, and associated run script.<br>clang: note: diagnostic msg: <br>********************<br>PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT:<br>Preprocessed source(s) and associated run script(s) are located at:<br>clang: note: diagnostic msg: /tmp/YAMLTraits-d1f411.cpp<br>clang: note: diagnostic msg: /tmp/YAMLTraits-d1f411.sh<br>clang: note: diagnostic msg: <br><br>But, if I run the emitted script it works fine:<br><br>pushd /tmp<br>bash /tmp/YAMLTraits-d1f411.sh<br><br><br>Or, another example (where clang++ isn’t crashing):<br><br>FAILED: /usr/bin/clang++ -DGTEST_HAS_RTTI=0 -D_DEBUG -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -Iutils/TableGen -I/home/pi/Source/Swift/llvm/utils/TableGen -Iinclude -I/home/pi/Source/Swift/llvm/include -fno-stack-protector -fPIC -fvisibility-inlines-hidden -Wall -W -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wmissing-field-initializers -pedantic -Wno-long-long -Wcovered-switch-default -Wnon-virtual-dtor -Wdelete-non-virtual-dtor -std=c++11 -fcolor-diagnostics -ffunction-sections -fdata-sections -O3 -UNDEBUG -fno-exceptions -fno-rtti -MMD -MT utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/CodeGenInstruction.cpp.o -MF utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/CodeGenInstruction.cpp.o.d -o utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/CodeGenInstruction.cpp.o -c /home/pi/Source/Swift/llvm/utils/TableGen/CodeGenInstruction.cpp<br>Stack dump:<br>0. Program arguments: /usr/lib/llvm-3.6/bin/clang -cc1 -triple armv6-unknown-linux-gnueabihf -emit-obj -disable-free -disable-llvm-verifier -main-file-name CodeGenInstruction.cpp -mrelocation-model pic -pic-level 2 -mthread-model posix -mdisable-fp-elim -fmath-errno -masm-verbose -mconstructor-aliases -fuse-init-array -target-cpu arm1136jf-s -target-abi aapcs-linux -mfloat-abi hard -target-linker-version 2.25 -dwarf-column-info -ffunction-sections -fdata-sections -coverage-file /home/pi/Source/Swift/build/Ninja-ReleaseAssert/llvm-linux-armv7/utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/CodeGenInstruction.cpp.o -resource-dir /usr/lib/llvm-3.6/bin/../lib/clang/3.6.2 -dependency-file utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/CodeGenInstruction.cpp.o.d -MT utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/CodeGenInstruction.cpp.o -D GTEST_HAS_RTTI=0 -D _DEBUG -D _GNU_SOURCE -D __STDC_CONSTANT_MACROS -D __STDC_FORMAT_MACROS -D __STDC_LIMIT_MACROS -U NDEBUG -I utils/TableGen -I /home/pi/Source/Swift/llvm/utils/TableGen -I include -I /home/pi/Source/Swift/llvm/include -internal-isystem /usr/bin/../lib/gcc/arm-linux-gnueabihf/4.9/../../../../include/c++/4.9 -internal-isystem /usr/bin/../lib/gcc/arm-linux-gnueabihf/4.9/../../../../include/arm-linux-gnueabihf/c++/4.9 -internal-isystem /usr/bin/../lib/gcc/arm-linux-gnueabihf/4.9/../../../../include/arm-linux-gnueabihf/c++/4.9 -internal-isystem /usr/bin/../lib/gcc/arm-linux-gnueabihf/4.9/../../../../include/c++/4.9/backward -internal-isystem /usr/local/include -internal-isystem /usr/lib/llvm-3.6/bin/../lib/clang/3.6.2/include -internal-externc-isystem /usr/include/arm-linux-gnueabihf -internal-externc-isystem /include -internal-externc-isystem /usr/include -O3 -Wall -W -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wmissing-field-initializers -Wno-long-long -Wcovered-switch-default -Wnon-virtual-dtor -Wdelete-non-virtual-dtor -pedantic -std=c++11 -fdeprecated-macro -fdebug-compilation-dir /home/pi/Source/Swift/build/Ninja-ReleaseAssert/llvm-linux-armv7 -ferror-limit 19 -fmessage-length 0 -fvisibility-inlines-hidden -mstackrealign -fno-rtti -fno-signed-char -fobjc-runtime=gcc -fdiagnostics-show-option -fcolor-diagnostics -vectorize-loops -vectorize-slp -o utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/CodeGenInstruction.cpp.o -x c++ /home/pi/Source/Swift/llvm/utils/TableGen/CodeGenInstruction.cpp <br>1. /home/pi/Source/Swift/llvm/include/llvm/ADT/SmallVector.h:718:44: current parser token ')'<br>2. /home/pi/Source/Swift/llvm/include/llvm/ADT/SmallVector.h:31:1: parsing namespace 'llvm'<br>3. /home/pi/Source/Swift/llvm/include/llvm/ADT/SmallVector.h:700:56: parsing function body 'swap'<br>4. /home/pi/Source/Swift/llvm/include/llvm/ADT/SmallVector.h:700:56: in compound statement ('{}')<br>error: unable to rename temporary 'utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/CodeGenInstruction.cpp.o-9c605f46' to output file 'utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/CodeGenInstruction.cpp.o': 'No such file or directory'<br>1 error generated.<br><br><br>Each time I invoke the build script I get a few files further:<br><br>utils/build-script -t -R -j 4 -- --use-gold-linker<br><br>In my previous attempts to build Swift on Pi, I’d not seen this, so I’m confused why it’s started now. My only working theories so far are that when I did an `apt-get update`/`apt-get upgrade` to check for a new Swift build, I applied a whole bunch of other updates to the system or second, maybe my microSD card is going bad =/<br><br>-tim<br><br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <</tt><tt><a href="https://lists.swift.org/pipermail/swift-dev/attachments/20160417/089ccc30/attachment-0001.html">https://lists.swift.org/pipermail/swift-dev/attachments/20160417/089ccc30/attachment-0001.html</a></tt><tt>><br><br>------------------------------<br><br>Message: 6<br>Date: Sun, 17 Apr 2016 16:50:47 -0500<br>From: Drew Crawford <drew@sealedabstract.com><br>To: Dmitri Gribenko <gribozavr@gmail.com><br>Cc: swift-dev <swift-dev@swift.org><br>Subject: Re: [swift-dev] [SR-710][RFC] Automatically detecting XCTest<br> test methods on Linux: Reflection? SourceKit?<br>Message-ID: <CD4EB0A4-4521-4E81-8FDC-5D3B27DD70BC@sealedabstract.com><br>Content-Type: text/plain; charset="utf-8"<br><br><br>> On Apr 3, 2016, at 10:05 PM, Dmitri Gribenko <gribozavr@gmail.com> wrote:<br>> <br>>> Hmm... but then wouldn't that more tightly couple the test discovery tool<br>>> and the Swift compiler? In an earlier email you said you "like #3 better<br>>> [...] because that would decouple the test discovery tool from the Swift<br>>> compiler." I think that part is confusing me.<br>> <br>> Sorry -- what I meant is that the compiler remains the point of truth<br>> about the language and can find the tests. The tools that actually<br>> generate glue code won't need to parse code, and would be decoupled<br>> from the compiler.<br><br>I am internally shipping a test framework that discovers tests via an out-of-tree parser. Teaching swiftc about XCTest syntax is not sufficient to deprecate my parser, and therefore is not sufficient for the compiler to be the source of truth for my tests.<br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <</tt><tt><a href="https://lists.swift.org/pipermail/swift-dev/attachments/20160417/00b0efb5/attachment-0001.html">https://lists.swift.org/pipermail/swift-dev/attachments/20160417/00b0efb5/attachment-0001.html</a></tt><tt>><br><br>------------------------------<br><br>Message: 7<br>Date: Sun, 17 Apr 2016 23:33:08 -0700<br>From: Timothy Wood <tjw@me.com><br>To: William Dillon <william@housedillon.com>, Kenny Leung via<br> swift-dev <swift-dev@swift.org><br>Subject: Re: [swift-dev] R_ARM_GOT_PREL error when building Swift on<br> Pi from source<br>Message-ID: <BB74C65D-3547-4FCB-A43D-F74E8B81CBA7@me.com><br>Content-Type: text/plain; charset="utf-8"<br><br><br>> On Apr 17, 2016, at 1:46 PM, Timothy Wood via swift-dev <swift-dev@swift.org> wrote:<br>> <br>> <br>>> On Apr 16, 2016, at 2:23 PM, William Dillon <william@housedillon.com <</tt><tt><a href="mailto:william@housedillon.com">mailto:william@housedillon.com</a></tt><tt>>> wrote:<br>>> <br>>> What LLVM are you using?<br>>> <br>>> You have to use the one from my github (and the arm branch) or it won't work:<br>>> <br>>> </tt><tt><a href="https://github.com/hpux735/swift-llvm/tree/arm">https://github.com/hpux735/swift-llvm/tree/arm</a></tt><tt> <</tt><tt><a href="https://github.com/hpux735/swift-llvm/tree/arm">https://github.com/hpux735/swift-llvm/tree/arm</a></tt><tt>> <br>>> <br>>> I haven't had time to upstream the changes to LLVM.<br>>> <br>>> - Will<br>> <br>> <br>> Ah, thanks! I was using <</tt><tt><a href="https://github.com/apple/swift-llvm/tree/swift-2.2-branch">https://github.com/apple/swift-llvm/tree/swift-2.2-branch</a></tt><tt> <</tt><tt><a href="https://github.com/apple/swift-llvm/tree/swift-2.2-branch">https://github.com/apple/swift-llvm/tree/swift-2.2-branch</a></tt><tt>>>, but will give your fork a try!<br>> <br>> -tim<br>> <br><br>I reset my Pi 3 to a fresh install of Jessie (2016-03-18), did the clang-3.6 install from <</tt><tt><a href="http://dev.iachieved.it/iachievedit/open-source-swift-on-raspberry-pi-2/">http://dev.iachieved.it/iachievedit/open-source-swift-on-raspberry-pi-2/</a></tt><tt>> and tried building with the above mentioned branch of llvm. This fixed the spurious build failures I was seeing, but I’m hitting a persistent build failure now:<br><br>[939/1818] Building CXX object tools/clang/utils/TableGen/CMakeFiles/obj.clang-tblgen.dir/ClangAttrEmitter.cpp.o<br>FAILED: /usr/bin/clang++-3.6 -DCLANG_ENABLE_ARCMT -DCLANG_ENABLE_OBJC_REWRITER -DCLANG_ENABLE_STATIC_ANALYZER -DGTEST_HAS_RTTI=0 -D_DEBUG -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -Itools/clang/utils/TableGen -I/home/pi/Source/Swift/llvm/tools/clang/utils/TableGen -I/home/pi/Source/Swift/llvm/tools/clang/include -Itools/clang/include -Iinclude -I/home/pi/Source/Swift/llvm/include -fno-stack-protector -fPIC -fvisibility-inlines-hidden -Wall -W -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wmissing-field-initializers -pedantic -Wno-long-long -Wcovered-switch-default -Wnon-virtual-dtor -Wdelete-non-virtual-dtor -std=c++11 -fcolor-diagnostics -ffunction-sections -fdata-sections -fno-common -Woverloaded-virtual -Wno-nested-anon-types -O3 -UNDEBUG -fno-exceptions -fno-rtti -MMD -MT tools/clang/utils/TableGen/CMakeFiles/obj.clang-tblgen.dir/ClangAttrEmitter.cpp.o -MF tools/clang/utils/TableGen/CMakeFiles/obj.clang-tblgen.dir/ClangAttrEmitter.cpp.o.d -o tools/clang/utils/TableGen/CMakeFiles/obj.clang-tblgen.dir/ClangAttrEmitter.cpp.o -c /home/pi/Source/Swift/llvm/tools/clang/utils/TableGen/ClangAttrEmitter.cpp<br>/home/pi/Source/Swift/llvm/tools/clang/utils/TableGen/ClangAttrEmitter.cpp:1075:23: error: no viable conversion from 'ArrayRef<std::pair<Record *, SMRange>>' to 'ArrayRef<llvm::Record *>'<br> ArrayRef<Record*> Bases = Search->getSuperClasses();<br> ^ ~~~~~~~~~~~~~~~~~~~~~~~~~<br>/home/pi/Source/Swift/llvm/include/llvm/ADT/ArrayRef.h:32:9: note: candidate constructor (the implicit copy constructor) not viable: no known conversion from 'ArrayRef<std::pair<Record *, SMRange> >' to 'const llvm::ArrayRef<llvm::Record *> &' for 1st argument<br> class ArrayRef {<br> ^<br>/home/pi/Source/Swift/llvm/include/llvm/ADT/ArrayRef.h:32:9: note: candidate constructor (the implicit move constructor) not viable: no known conversion from 'ArrayRef<std::pair<Record *, SMRange> >' to 'llvm::ArrayRef<llvm::Record *> &&' for 1st argument<br> class ArrayRef {<br>...<br><br>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.<br><br>-tim<br><br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <</tt><tt><a href="https://lists.swift.org/pipermail/swift-dev/attachments/20160417/789510bf/attachment-0001.html">https://lists.swift.org/pipermail/swift-dev/attachments/20160417/789510bf/attachment-0001.html</a></tt><tt>><br><br>------------------------------<br><br>Message: 8<br>Date: Mon, 18 Apr 2016 17:39:51 +0200<br>From: Geordie Jay <geojay@gmail.com><br>To: swift-dev@swift.org<br>Subject: [swift-dev] SIMD in open source Swift?<br>Message-ID: <B4B1849C-8046-4C00-A34A-72BDC4CB08A8@gmail.com><br>Content-Type: text/plain; charset="utf-8"<br><br>Dear fellow Swift-Devvers,<br><br>On Darwin we have a SIMD module, but I’m assuming (based on playing around with it in the past) that it is unavailable in open-source Swift.<br><br>Does anyone know another way of using SIMD intrinsics in a cross-platform way (Linux-only would also do)? Also, is it a goal to provide at least SIMD intrinsics and basic operations within Swift’s core in the future, or is the general philosophy that this kind of thing will be maintained by the community?<br><br>Regards,<br>Geordie<br><br>-------------- next part --------------<br>A non-text attachment was scrubbed...<br>Name: signature.asc<br>Type: application/pgp-signature<br>Size: 455 bytes<br>Desc: Message signed with OpenPGP using GPGMail<br>URL: <</tt><tt><a href="https://lists.swift.org/pipermail/swift-dev/attachments/20160418/7083c5d4/attachment-0001.sig">https://lists.swift.org/pipermail/swift-dev/attachments/20160418/7083c5d4/attachment-0001.sig</a></tt><tt>><br><br>------------------------------<br><br>Message: 9<br>Date: Fri, 15 Apr 2016 17:00:18 -0700<br>From: Sean Callanan <scallanan@apple.com><br>To: swift-dev@swift.org<br>Subject: Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift<br> Incremental RA - Ubuntu 15.10 (master) #4254<br>Message-ID: <5DC21488-5922-40B9-9EDA-E3159B1B0099@apple.com><br>Content-Type: text/plain; charset="utf-8"<br><br>I’m on it.<br><br>Sean<br><br>> On Apr 15, 2016, at 4:56 PM, no-reply@swift.org wrote:<br>> <br>> [FAILURE] oss-swift-incremental-RA-linux-ubuntu-15_10 [#4254]<br>> <br>> Build URL: </tt><tt><a href="https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/4254/">https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/4254/</a></tt><tt> <</tt><tt><a href="https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/4254/">https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/4254/</a></tt><tt>><br>> Project: oss-swift-incremental-RA-linux-ubuntu-15_10<br>> Date of build: Fri, 15 Apr 2016 16:48:20 -0700<br>> Build duration: 8 min 3 sec<br>> Identified problems:<br>> <br>> Compile Error: This build failed because of a compile error. Below is a list of all errors in the build log:<br>> Indication 1 <</tt><tt><a href="https://ci.swift.org//job/oss-swift-incremental-RA-linux-ubuntu-15_10/4254/consoleFull#-1652570388ee1a197b-acac-4b17-83cf-a53b95139a76">https://ci.swift.org//job/oss-swift-incremental-RA-linux-ubuntu-15_10/4254/consoleFull#-1652570388ee1a197b-acac-4b17-83cf-a53b95139a76</a></tt><tt>><br>> Regression test failed: This build failed because a regression test in the test suite FAILed. Below is a list of all errors:<br>> Indication 1 <</tt><tt><a href="https://ci.swift.org//job/oss-swift-incremental-RA-linux-ubuntu-15_10/4254/consoleFull#1729578532fca400bf-2f4a-462e-b517-e058d770b2d7">https://ci.swift.org//job/oss-swift-incremental-RA-linux-ubuntu-15_10/4254/consoleFull#1729578532fca400bf-2f4a-462e-b517-e058d770b2d7</a></tt><tt>><br>> Tests:<br>> <br>> Name: Swift<br>> Failed: 11 test(s), Passed: 7798 test(s), Total: 7809 test(s)<br>> Failed: Swift.PlaygroundTransform.array.swift <</tt><tt><a href="https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/4254/testReport/junit/Swift/PlaygroundTransform/array_swift">https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/4254/testReport/junit/Swift/PlaygroundTransform/array_swift</a></tt><tt>><br>> Failed: Swift.PlaygroundTransform.array_did_set.swift <</tt><tt><a href="https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/4254/testReport/junit/Swift/PlaygroundTransform/array_did_set_swift">https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/4254/testReport/junit/Swift/PlaygroundTransform/array_did_set_swift</a></tt><tt>><br>> Failed: Swift.PlaygroundTransform.bare_value.swift <</tt><tt><a href="https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/4254/testReport/junit/Swift/PlaygroundTransform/bare_value_swift">https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/4254/testReport/junit/Swift/PlaygroundTransform/bare_value_swift</a></tt><tt>><br>> Failed: Swift.PlaygroundTransform.control-flow.swift <</tt><tt><a href="https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/4254/testReport/junit/Swift/PlaygroundTransform/control_flow_swift">https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/4254/testReport/junit/Swift/PlaygroundTransform/control_flow_swift</a></tt><tt>><br>> Failed: Swift.PlaygroundTransform.declarations.swift <</tt><tt><a href="https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/4254/testReport/junit/Swift/PlaygroundTransform/declarations_swift">https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/4254/testReport/junit/Swift/PlaygroundTransform/declarations_swift</a></tt><tt>><br>> Failed: Swift.PlaygroundTransform.do-catch.swift <</tt><tt><a href="https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/4254/testReport/junit/Swift/PlaygroundTransform/do_catch_swift">https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/4254/testReport/junit/Swift/PlaygroundTransform/do_catch_swift</a></tt><tt>><br>> Failed: Swift.PlaygroundTransform.do.swift <</tt><tt><a href="https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/4254/testReport/junit/Swift/PlaygroundTransform/do_swift">https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/4254/testReport/junit/Swift/PlaygroundTransform/do_swift</a></tt><tt>><br>> Failed: Swift.PlaygroundTransform.high_performance.swift <</tt><tt><a href="https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/4254/testReport/junit/Swift/PlaygroundTransform/high_performance_swift">https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/4254/testReport/junit/Swift/PlaygroundTransform/high_performance_swift</a></tt><tt>><br>> Failed: Swift.PlaygroundTransform.init.swift <</tt><tt><a href="https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/4254/testReport/junit/Swift/PlaygroundTransform/init_swift">https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/4254/testReport/junit/Swift/PlaygroundTransform/init_swift</a></tt><tt>><br>> Failed: Swift.PlaygroundTransform.mutation.swift <</tt><tt><a href="https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/4254/testReport/junit/Swift/PlaygroundTransform/mutation_swift">https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/4254/testReport/junit/Swift/PlaygroundTransform/mutation_swift</a></tt><tt>><br>> Failed: Swift.PlaygroundTransform.print.swift <</tt><tt><a href="https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/4254/testReport/junit/Swift/PlaygroundTransform/print_swift">https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/4254/testReport/junit/Swift/PlaygroundTransform/print_swift</a></tt><tt>><br>> Name: Swift-Unit<br>> Failed: 0 test(s), Passed: 270 test(s), Total: 270 test(s)<br>> <br>> Changes<br>> <br>> Commit a0fa099f1a3d6da66db4b86e0047f91fbdae041c by scallanan:<br>> [PlaygroundTransform] embed source ranges in data packets before sending<br>> <br>> edit: lib/Sema/PlaygroundTransform.cpp<br>> edit: test/PlaygroundTransform/Inputs/PlaygroundsRuntime.swift<br><br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <</tt><tt><a href="https://lists.swift.org/pipermail/swift-dev/attachments/20160415/03100110/attachment-0001.html">https://lists.swift.org/pipermail/swift-dev/attachments/20160415/03100110/attachment-0001.html</a></tt><tt>><br><br>------------------------------<br><br>Message: 10<br>Date: Fri, 15 Apr 2016 17:05:02 -0700<br>From: Sean Callanan <scallanan@apple.com><br>To: swift-dev@swift.org<br>Subject: Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift<br> Incremental RA - Ubuntu 15.10 (master) #4254<br>Message-ID: <FD143CA3-ACB5-495A-8877-DB618A68783C@apple.com><br>Content-Type: text/plain; charset="utf-8"<br><br>Should be resolved by 5a86c9631d1caa900d4de6b40e4eac0a9e6e421a<br><br>Sean<br><br>> On Apr 15, 2016, at 5:00 PM, Sean Callanan <scallanan@apple.com> wrote:<br>> <br>> I’m on it.<br>> <br>> Sean<br>> <br>>> On Apr 15, 2016, at 4:56 PM, no-reply@swift.org <</tt><tt><a href="mailto:no-reply@swift.org">mailto:no-reply@swift.org</a></tt><tt>> wrote:<br>>> <br>>> [FAILURE] oss-swift-incremental-RA-linux-ubuntu-15_10 [#4254]<br>>> <br>>> Build URL: </tt><tt><a href="https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/4254/">https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/4254/</a></tt><tt> <</tt><tt><a href="https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/4254/">https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/4254/</a></tt><tt>><br>>> Project: oss-swift-incremental-RA-linux-ubuntu-15_10<br>>> Date of build: Fri, 15 Apr 2016 16:48:20 -0700<br>>> Build duration: 8 min 3 sec<br>>> Identified problems:<br>>> <br>>> Compile Error: This build failed because of a compile error. Below is a list of all errors in the build log:<br>>> Indication 1 <</tt><tt><a href="https://ci.swift.org//job/oss-swift-incremental-RA-linux-ubuntu-15_10/4254/consoleFull#-1652570388ee1a197b-acac-4b17-83cf-a53b95139a76">https://ci.swift.org//job/oss-swift-incremental-RA-linux-ubuntu-15_10/4254/consoleFull#-1652570388ee1a197b-acac-4b17-83cf-a53b95139a76</a></tt><tt>><br>>> Regression test failed: This build failed because a regression test in the test suite FAILed. Below is a list of all errors:<br>>> Indication 1 <</tt><tt><a href="https://ci.swift.org//job/oss-swift-incremental-RA-linux-ubuntu-15_10/4254/consoleFull#1729578532fca400bf-2f4a-462e-b517-e058d770b2d7">https://ci.swift.org//job/oss-swift-incremental-RA-linux-ubuntu-15_10/4254/consoleFull#1729578532fca400bf-2f4a-462e-b517-e058d770b2d7</a></tt><tt>><br>>> Tests:<br>>> <br>>> Name: Swift<br>>> Failed: 11 test(s), Passed: 7798 test(s), Total: 7809 test(s)<br>>> Failed: Swift.PlaygroundTransform.array.swift <</tt><tt><a href="https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/4254/testReport/junit/Swift/PlaygroundTransform/array_swift">https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/4254/testReport/junit/Swift/PlaygroundTransform/array_swift</a></tt><tt>><br>>> Failed: Swift.PlaygroundTransform.array_did_set.swift <</tt><tt><a href="https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/4254/testReport/junit/Swift/PlaygroundTransform/array_did_set_swift">https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/4254/testReport/junit/Swift/PlaygroundTransform/array_did_set_swift</a></tt><tt>><br>>> Failed: Swift.PlaygroundTransform.bare_value.swift <</tt><tt><a href="https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/4254/testReport/junit/Swift/PlaygroundTransform/bare_value_swift">https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/4254/testReport/junit/Swift/PlaygroundTransform/bare_value_swift</a></tt><tt>><br>>> Failed: Swift.PlaygroundTransform.control-flow.swift <</tt><tt><a href="https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/4254/testReport/junit/Swift/PlaygroundTransform/control_flow_swift">https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/4254/testReport/junit/Swift/PlaygroundTransform/control_flow_swift</a></tt><tt>><br>>> Failed: Swift.PlaygroundTransform.declarations.swift <</tt><tt><a href="https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/4254/testReport/junit/Swift/PlaygroundTransform/declarations_swift">https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/4254/testReport/junit/Swift/PlaygroundTransform/declarations_swift</a></tt><tt>><br>>> Failed: Swift.PlaygroundTransform.do-catch.swift <</tt><tt><a href="https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/4254/testReport/junit/Swift/PlaygroundTransform/do_catch_swift">https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/4254/testReport/junit/Swift/PlaygroundTransform/do_catch_swift</a></tt><tt>><br>>> Failed: Swift.PlaygroundTransform.do.swift <</tt><tt><a href="https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/4254/testReport/junit/Swift/PlaygroundTransform/do_swift">https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/4254/testReport/junit/Swift/PlaygroundTransform/do_swift</a></tt><tt>><br>>> Failed: Swift.PlaygroundTransform.high_performance.swift <</tt><tt><a href="https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/4254/testReport/junit/Swift/PlaygroundTransform/high_performance_swift">https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/4254/testReport/junit/Swift/PlaygroundTransform/high_performance_swift</a></tt><tt>><br>>> Failed: Swift.PlaygroundTransform.init.swift <</tt><tt><a href="https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/4254/testReport/junit/Swift/PlaygroundTransform/init_swift">https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/4254/testReport/junit/Swift/PlaygroundTransform/init_swift</a></tt><tt>><br>>> Failed: Swift.PlaygroundTransform.mutation.swift <</tt><tt><a href="https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/4254/testReport/junit/Swift/PlaygroundTransform/mutation_swift">https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/4254/testReport/junit/Swift/PlaygroundTransform/mutation_swift</a></tt><tt>><br>>> Failed: Swift.PlaygroundTransform.print.swift <</tt><tt><a href="https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/4254/testReport/junit/Swift/PlaygroundTransform/print_swift">https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-15_10/4254/testReport/junit/Swift/PlaygroundTransform/print_swift</a></tt><tt>></tt><br><tt>>> Name: Swift-Unit<br>>> Failed: 0 test(s), Passed: 270 test(s), Total: 270 test(s)<br>>> <br>>> Changes<br>>> <br>>> Commit a0fa099f1a3d6da66db4b86e0047f91fbdae041c by scallanan:<br>>> [PlaygroundTransform] embed source ranges in data packets before sending<br>>> <br>>> edit: lib/Sema/PlaygroundTransform.cpp<br>>> edit: test/PlaygroundTransform/Inputs/PlaygroundsRuntime.swift<br>> <br><br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <</tt><tt><a href="https://lists.swift.org/pipermail/swift-dev/attachments/20160415/93cf70e9/attachment-0001.html">https://lists.swift.org/pipermail/swift-dev/attachments/20160415/93cf70e9/attachment-0001.html</a></tt><tt>><br><br>------------------------------<br><br>Message: 11<br>Date: Fri, 15 Apr 2016 17:21:11 -0700<br>From: Sean Callanan <scallanan@apple.com><br>To: swift-dev@swift.org<br>Subject: Re: [swift-dev] [Swift CI] Build Failure: 0. OSS - Swift<br> Incremental RA - OS X (master) #3432<br>Message-ID: <AF7D4469-C5E9-4A2F-B9A7-3D649ED8A19D@apple.com><br>Content-Type: text/plain; charset="utf-8"<br><br>This is already fixed in 5a86c9631d1caa900d4de6b40e4eac0a9e6e421a.<br><br>> On Apr 15, 2016, at 5:20 PM, no-reply@swift.org wrote:<br>> <br>> [FAILURE] oss-swift-incremental-RA-osx [#3432]<br>> <br>> Build URL: </tt><tt><a href="https://ci.swift.org/job/oss-swift-incremental-RA-osx/3432/">https://ci.swift.org/job/oss-swift-incremental-RA-osx/3432/</a></tt><tt> <</tt><tt><a href="https://ci.swift.org/job/oss-swift-incremental-RA-osx/3432/">https://ci.swift.org/job/oss-swift-incremental-RA-osx/3432/</a></tt><tt>><br>> Project: oss-swift-incremental-RA-osx<br>> Date of build: Fri, 15 Apr 2016 16:55:05 -0700<br>> Build duration: 25 min<br>> Identified problems:<br>> <br>> Compile Error: This build failed because of a compile error. Below is a list of all errors in the build log:<br>> Indication 1 <</tt><tt><a href="https://ci.swift.org//job/oss-swift-incremental-RA-osx/3432/consoleFull#-324893336ee1a197b-acac-4b17-83cf-a53b95139a76">https://ci.swift.org//job/oss-swift-incremental-RA-osx/3432/consoleFull#-324893336ee1a197b-acac-4b17-83cf-a53b95139a76</a></tt><tt>><br>> Regression test failed: This build failed because a regression test in the test suite FAILed. Below is a list of all errors:<br>> Indication 1 <</tt><tt><a href="https://ci.swift.org//job/oss-swift-incremental-RA-osx/3432/consoleFull#-1524476087fca400bf-2f4a-462e-b517-e058d770b2d7">https://ci.swift.org//job/oss-swift-incremental-RA-osx/3432/consoleFull#-1524476087fca400bf-2f4a-462e-b517-e058d770b2d7</a></tt><tt>><br>> Tests:<br>> <br>> Name: Swift<br>> Failed: 11 test(s), Passed: 7798 test(s), Total: 7809 test(s)<br>> Failed: Swift.PlaygroundTransform.array.swift <</tt><tt><a href="https://ci.swift.org/job/oss-swift-incremental-RA-osx/3432/testReport/junit/Swift/PlaygroundTransform/array_swift">https://ci.swift.org/job/oss-swift-incremental-RA-osx/3432/testReport/junit/Swift/PlaygroundTransform/array_swift</a></tt><tt>><br>> Failed: Swift.PlaygroundTransform.array_did_set.swift <</tt><tt><a href="https://ci.swift.org/job/oss-swift-incremental-RA-osx/3432/testReport/junit/Swift/PlaygroundTransform/array_did_set_swift">https://ci.swift.org/job/oss-swift-incremental-RA-osx/3432/testReport/junit/Swift/PlaygroundTransform/array_did_set_swift</a></tt><tt>><br>> Failed: Swift.PlaygroundTransform.bare_value.swift <</tt><tt><a href="https://ci.swift.org/job/oss-swift-incremental-RA-osx/3432/testReport/junit/Swift/PlaygroundTransform/bare_value_swift">https://ci.swift.org/job/oss-swift-incremental-RA-osx/3432/testReport/junit/Swift/PlaygroundTransform/bare_value_swift</a></tt><tt>><br>> Failed: Swift.PlaygroundTransform.control-flow.swift <</tt><tt><a href="https://ci.swift.org/job/oss-swift-incremental-RA-osx/3432/testReport/junit/Swift/PlaygroundTransform/control_flow_swift">https://ci.swift.org/job/oss-swift-incremental-RA-osx/3432/testReport/junit/Swift/PlaygroundTransform/control_flow_swift</a></tt><tt>><br>> Failed: Swift.PlaygroundTransform.declarations.swift <</tt><tt><a href="https://ci.swift.org/job/oss-swift-incremental-RA-osx/3432/testReport/junit/Swift/PlaygroundTransform/declarations_swift">https://ci.swift.org/job/oss-swift-incremental-RA-osx/3432/testReport/junit/Swift/PlaygroundTransform/declarations_swift</a></tt><tt>><br>> Failed: Swift.PlaygroundTransform.do-catch.swift <</tt><tt><a href="https://ci.swift.org/job/oss-swift-incremental-RA-osx/3432/testReport/junit/Swift/PlaygroundTransform/do_catch_swift">https://ci.swift.org/job/oss-swift-incremental-RA-osx/3432/testReport/junit/Swift/PlaygroundTransform/do_catch_swift</a></tt><tt>><br>> Failed: Swift.PlaygroundTransform.do.swift <</tt><tt><a href="https://ci.swift.org/job/oss-swift-incremental-RA-osx/3432/testReport/junit/Swift/PlaygroundTransform/do_swift">https://ci.swift.org/job/oss-swift-incremental-RA-osx/3432/testReport/junit/Swift/PlaygroundTransform/do_swift</a></tt><tt>><br>> Failed: Swift.PlaygroundTransform.high_performance.swift <</tt><tt><a href="https://ci.swift.org/job/oss-swift-incremental-RA-osx/3432/testReport/junit/Swift/PlaygroundTransform/high_performance_swift">https://ci.swift.org/job/oss-swift-incremental-RA-osx/3432/testReport/junit/Swift/PlaygroundTransform/high_performance_swift</a></tt><tt>><br>> Failed: Swift.PlaygroundTransform.init.swift <</tt><tt><a href="https://ci.swift.org/job/oss-swift-incremental-RA-osx/3432/testReport/junit/Swift/PlaygroundTransform/init_swift">https://ci.swift.org/job/oss-swift-incremental-RA-osx/3432/testReport/junit/Swift/PlaygroundTransform/init_swift</a></tt><tt>><br>> Failed: Swift.PlaygroundTransform.mutation.swift <</tt><tt><a href="https://ci.swift.org/job/oss-swift-incremental-RA-osx/3432/testReport/junit/Swift/PlaygroundTransform/mutation_swift">https://ci.swift.org/job/oss-swift-incremental-RA-osx/3432/testReport/junit/Swift/PlaygroundTransform/mutation_swift</a></tt><tt>><br>> Failed: Swift.PlaygroundTransform.print.swift <</tt><tt><a href="https://ci.swift.org/job/oss-swift-incremental-RA-osx/3432/testReport/junit/Swift/PlaygroundTransform/print_swift">https://ci.swift.org/job/oss-swift-incremental-RA-osx/3432/testReport/junit/Swift/PlaygroundTransform/print_swift</a></tt><tt>><br>> Name: Swift-Unit<br>> Failed: 0 test(s), Passed: 302 test(s), Total: 302 test(s)<br>> <br>> Changes<br>> <br>> Commit a0fa099f1a3d6da66db4b86e0047f91fbdae041c by scallanan:<br>> [PlaygroundTransform] embed source ranges in data packets before sending<br>> <br>> edit: lib/Sema/PlaygroundTransform.cpp<br>> edit: test/PlaygroundTransform/Inputs/PlaygroundsRuntime.swift<br><br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <</tt><tt><a href="https://lists.swift.org/pipermail/swift-dev/attachments/20160415/ffc98b5c/attachment-0001.html">https://lists.swift.org/pipermail/swift-dev/attachments/20160415/ffc98b5c/attachment-0001.html</a></tt><tt>><br><br>------------------------------<br><br>_______________________________________________<br>swift-dev mailing list<br>swift-dev@swift.org<br></tt><tt><a href="https://lists.swift.org/mailman/listinfo/swift-dev">https://lists.swift.org/mailman/listinfo/swift-dev</a></tt><tt><br><br><br>End of swift-dev Digest, Vol 5, Issue 18<br>****************************************<br></tt><br><br><BR>
</body></html>