Related to this, what branch should one actually be building if they are hoping to create a version that looks like the 2.2-SNAPSHOT. There is a master branch and a swift-2.2-branch in the repo, with the default git clone branch being master. What purpose does the swift-2.2-branch server?
Also, is there documentation or a reference on what the purpose of the branches are and a streaming strategy around them (when do they diverge, when do they merge, etc.) Thanks! Joe On Sat, Dec 19, 2015 at 5:03 PM, Joseph Bell <j...@iachieved.it> wrote: > Thanks Emanuel, I was operating with a clean environment and see another > dependency has been added to the buildbot_linux (swift-integration-tests) > so I'll pull that down and build again. > > > > On Sat, Dec 19, 2015 at 4:54 PM, Emanuel Zephir <emanuelzep...@gmail.com> > wrote: > >> I can't reproduce this on Ubuntu 14.04 or on OS X 10.10 at 696544a0. >> >> On Linux: >> >> Expected Passes : 6964 >> Expected Failures : 100 >> Unsupported Tests : 622 >> -- check-swift-all-linux-x86_64 finished -- >> --- Finished tests for swift --- >> >> Specifically on the SIL Crashers, the results are: >> >> PASS: Swift :: SIL/crashers/002-swift-performnamebinding.sil (1 of 7) >> PASS: Swift :: SIL/crashers/003-swift-parser-parsetypesimple.sil (2 of 7) >> PASS: Swift :: SIL/crashers/004-swift-expr-getsourcerange.sil (3 of 7) >> PASS: Swift :: SIL/crashers/001-swift-parser-parsesilvtable.sil (4 of 7) >> PASS: Swift :: SIL/crashers/005-swift-silfunction-verify.sil (5 of 7) >> PASS: Swift :: SIL/crashers/007-swift-abstractstoragedecl-makecomputed.sil >> (6 of 7) >> PASS: Swift :: >> SIL/crashers/006-swift-syntaxsugartype-getimplementationtype.sil >> (7 of 7) >> >> and on OS X I have: >> >> Expected Passes : 7679 >> Expected Failures : 8 >> Unsupported Tests : 40 >> -- check-swift-all-macosx-x86_64 finished -- >> --- Finished tests for swift --- >> >> It's interesting to note that I seem to have one more test on Linux than >> you. >> >> --Emanuel >> >> On Sat, Dec 19, 2015 at 2:34 PM, Joseph Bell via swift-dev >> <swift-dev@swift.org> wrote: >> > That is interesting, this was on Ubuntu 15.10, the other being on 14.04: >> > >> > ******************** >> > Testing Time: 260.04s >> > ******************** >> > Failing Tests (1): >> > Swift :: SIL/crashers/004-swift-expr-getsourcerange.sil >> > >> > Expected Passes : 6965 >> > Expected Failures : 100 >> > Unsupported Tests : 620 >> > Unexpected Failures: 1 >> > *** Failed while running tests for swift (check-swift-all-linux-x86_64) >> > ./swift/utils/build-script: command terminated with a non-zero exit >> status >> > 1, aborting >> > ./swift/utils/build-script: command terminated with a non-zero exit >> status >> > 1, aborting >> > >> > Command Output (stderr): >> > -- >> > >> /home/package-swift/swift/validation-test/SIL/crashers/004-swift-expr-getsourcerange.sil:3:15: >> > error: expected convention name identifier in 'convention' attribute >> > l<@convention()>( >> > ^ >> > >> /home/package-swift/swift/validation-test/SIL/crashers/004-swift-expr-getsourcerange.sil:3:16: >> > error: expected type >> > l<@convention()>( >> > ^ >> > >> /home/package-swift/swift/validation-test/SIL/crashers/004-swift-expr-getsourcerange.sil:3:2: >> > note: while parsing this '<' as a type parameter bracket >> > l<@convention()>( >> > ^ >> > >> /home/package-swift/swift/validation-test/SIL/crashers/004-swift-expr-getsourcerange.sil:3:18: >> > error: expected expression in list of expressions >> > l<@convention()>( >> > ^ >> > >> /home/package-swift/swift/validation-test/SIL/crashers/004-swift-expr-getsourcerange.sil:3:18: >> > error: expected ',' separator >> > l<@convention()>( >> > ^ >> > , >> > >> /home/package-swift/swift/validation-test/SIL/crashers/004-swift-expr-getsourcerange.sil:3:1: >> > error: expressions are not allowed at the top level >> > l<@convention()>( >> > ^ >> > >> /home/package-swift/swift/validation-test/SIL/crashers/004-swift-expr-getsourcerange.sil:3:1: >> > error: use of unresolved identifier 'l' >> > l<@convention()>( >> > ^ >> > >> > Joe >> > >> > >> > On Sat, Dec 19, 2015 at 3:23 PM, Wallacy <walla...@gmail.com> wrote: >> >> >> >> >> >> Last commit: 696544a0003d43de824ead0b4ec9c19fda9a7553 (4 hours ago) >> >> >> >> Testing Time: 1838.83s >> >> Expected Passes : 2357 >> >> Expected Failures : 5 >> >> Unsupported Tests : 35 >> >> -- check-swift-macosx-x86_64 finished -- >> >> --- Finished tests for swift --- >> >> >> >> >> >> Em sáb, 19 de dez de 2015 às 16:47, Joseph Bell via swift-dev >> >> <swift-dev@swift.org> escreveu: >> >>> >> >>> Can anyone confirm or deny that this is a known issue at the moment? >> >>> This is with a fresh checkout as of this morning (Dec 19). >> >>> >> >>> ******************** >> >>> Testing Time: 261.00s >> >>> ******************** >> >>> Failing Tests (1): >> >>> Swift :: SIL/crashers/004-swift-expr-getsourcerange.sil >> >>> >> >>> Expected Passes : 6965 >> >>> Expected Failures : 100 >> >>> Unsupported Tests : 620 >> >>> Unexpected Failures: 1 >> >>> *** Failed while running tests for swift >> (check-swift-all-linux-x86_64) >> >>> ./swift/utils/build-script: command terminated with a non-zero exit >> >>> status 1, aborting >> >>> ./swift/utils/build-script: command terminated with a non-zero exit >> >>> status 1, aborting >> >>> >> >>> ➜ swift git:(master) git rev-parse HEAD >> >>> 696544a0003d43de824ead0b4ec9c19fda9a7553 >> >>> >> >>> _______________________________________________ >> >>> swift-dev mailing list >> >>> swift-dev@swift.org >> >>> https://lists.swift.org/mailman/listinfo/swift-dev >> > >> > >> > >> > _______________________________________________ >> > swift-dev mailing list >> > swift-dev@swift.org >> > https://lists.swift.org/mailman/listinfo/swift-dev >> > >> > >
_______________________________________________ swift-dev mailing list swift-dev@swift.org https://lists.swift.org/mailman/listinfo/swift-dev
