bill can you open a new bug entry. There are too much activities so that we could remember all the information passing around :)
Stef On May 25, 2010, at 8:58 PM, Schwab,Wilhelm K wrote: > Hello all, > > Please see attached - CAREFULLY :) It turns out that NetworkSmokeTest will > fail in your images, for want of #nextMany: and other additions I have made > to streams. I will try to get them packaged for release, but if nothing > else, please take a careful look at ConnectionQueue, which appears to be > broken in 1.x, and hopefully fixed by the attached. > > Bill > > > > ________________________________________ > From: [email protected] > [[email protected]] On Behalf Of Schwab,Wilhelm K > [[email protected]] > Sent: Monday, May 24, 2010 6:33 PM > To: [email protected] > Subject: [Pharo-project] ConnectionQueue defect in 1.0 > > Hello all, > > Attached is a simple test for networking. It passed in 1.0 RC1 and fails in > 1.0 and in 1.1 beta. The problem arises in ConnectionQueue>>listenLoop. > #waitForConnectionFor: returns a boolean, not the new socket, and the listen > loop looks like it is expecting the socket. Any ideas? > > Billx > > <SocketWoes.1.cs>_______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
