+swift-lldb-dev > On Apr 14, 2016, at 7:20 , Joseph Bell via swift-dev <swift-dev@swift.org> > wrote: > > Ryan, thanks. I've voted on SR-1109 and will add the steps I use to > reproduce as well. > > I think now its clear why the 14.04 and 15.10 packaging tests are passing, > and that's because they aren't running the tests that leverage pexpect, if > you look at the console log for the 14.04 test: > https://ci.swift.org/view/Packages/job/oss-swift-package-linux-ubuntu-14_04/993/consoleText > > <https://ci.swift.org/view/Packages/job/oss-swift-package-linux-ubuntu-14_04/993/consoleText> > > lit.py: lit.cfg:101: note: 'pexpect' module unavailable, skipping related > tests > > Perhaps pexpect should be added to the CI server so these tests can begin > failing properly. > > > On Thu, Apr 14, 2016 at 8:47 AM, Ryan Lovelett via swift-dev > <swift-dev@swift.org <mailto:swift-dev@swift.org>> wrote: > On Thu, Apr 14, 2016, at 09:17 AM, Joseph Bell via swift-dev wrote: >> Howdy, >> >> I've mentioned this once before and didn't get any feedback; I thought I'd >> give it one more shot. >> >> Has anyone out there tried building, from scratch, the Swift 3.0 package on >> Ubuntu? The compile, link, packaging steps all complete successfully, but >> then the repl/test-repl-glibc.py fails. The failure is that the REPL >> doesn't interact (the underlying script is using pexpect to send/expect) >> properly: >> >> 2> import Glibc >> warning: <REPL>:1:1: warning: #line directive is deprecated, please use >> #sourceLocation instead >> #line 2 "repl.swift" >> ^~~~~ >> #sourceLocation >> >> warning: repl.swift:3:1: warning: #line directive is deprecated, please use >> #sourceLocation instead >> #line >> ^~~~~ >> #sourceLocation >> >> error: repl.swift:2:8: error: missing required module 'SwiftGlibc' >> import Glibc >> >> This is occurring on two separate Ubuntu 14.04 systems, one of which is a >> greenfield VM with all of the prerequisites/clang-3.6 installed. >> >> Stumped on this one and was just curious if anyone can reproduce. > > I can also reproduce. I actually broght this up yesterday too (just on a > different list) [1]. I suggest you go vote for SR-1109 [2] which is the bug > report for this issue. > > I think this is show stopper. Not for the REPL break but because it also > breaks the debugger on Linux as well. > > Right now I'm trying to bisect the repos to see which commit(s?) might have > introduced this regression. Kate Stone mentioned that she thinks this issue > was introduced sometime after the 3-16 snapshot. I'm trying to corroborate > that. > > [1] > https://lists.swift.org/pipermail/swift-lldb-dev/Week-of-Mon-20160411/000106.html > > <https://lists.swift.org/pipermail/swift-lldb-dev/Week-of-Mon-20160411/000106.html> > [2] https://bugs.swift.org/browse/SR-1109 > <https://bugs.swift.org/browse/SR-1109> > >> >> Thanks, >> Joe >> >> >> >> --- >> http://dev.iachieved.it/iachievedit/ <http://dev.iachieved.it/iachievedit/> >> @iachievedit >> _______________________________________________ >> swift-dev mailing list >> swift-dev@swift.org <mailto:swift-dev@swift.org> >> https://lists.swift.org/mailman/listinfo/swift-dev >> <https://lists.swift.org/mailman/listinfo/swift-dev> > > > _______________________________________________ > swift-dev mailing list > swift-dev@swift.org <mailto:swift-dev@swift.org> > https://lists.swift.org/mailman/listinfo/swift-dev > <https://lists.swift.org/mailman/listinfo/swift-dev> > > > > > -- > --- > http://dev.iachieved.it/iachievedit/ <http://dev.iachieved.it/iachievedit/> > @iachievedit > _______________________________________________ > 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
