Actually this is still a work in progress, you'll find quite a few
tests don't work
yet because they require some modification.
For example on machines 8 years back you could actually see socket state
changes when you closed your side of the socket. Now you close it, and
bang (usually)
the socket gets unconnected, so a test fails that was looking at state
changes.
Also some of the tests required use of port ECHO to reflect data back to
check for send/receive, that's very hard to do now because most linux
systems
consider poking at the echo port as a denial of service attack.
On Nov 12, 2008, at 12:32 AM, Damien Cassou wrote:
Hi Dan,
On Sat, Oct 25, 2008 at 8:36 PM, Dan Corneanu
<[EMAIL PROTECTED]> wrote:
I've played with the change sets from
http://www.smalltalkconsulting.com/html/OTNotes4.html.
I've made some changes to the tests, to fit the current Socket and
NetNameResolver implementations. If it is of any help, I can put up a
mcz so others can have a look to the code.
John released a new changeset:
http://code.google.com/p/pharo/issues/detail?id=275. However, unit
tests does not run due to missing NetNameResolver
class>>initializeNetworkIfFail:. I think you removed that method.
Could you please check the changeset, make the necessary changes,
verify that all unit tests run and commit to PharoInbox?
Also, please update the issue on google code according to what you do.
Bye
--
Damien Cassou
http://damiencassou.seasidehosting.st
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
--
=
=
=
========================================================================
John M. McIntosh <[EMAIL PROTECTED]>
Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com
=
=
=
========================================================================
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
