[ http://issues.apache.org/jira/browse/GERONIMO-407?page=comments#action_54837 ] Ralf Barkow commented on GERONIMO-407: --------------------------------------
The current revision of SocketProtocolStressTest.java is 55671, with the deactivated XtestSimple() and XtestConcurrentRequests(), ergo pointless. Rev 55278 -- with activated testSimple() and testConcurrentRequests() -- even runs on a 300Mhz machine as an JUnit Test in Eclipse but not in the maven build context! dain commited Rev 55671 with the comment: "These tests don't run on osx[...]". I still think it would be a better solution to un-X the tests again (fall back to Rev 55278) and exclude this test by patching the project.xml file [see attached modules_network.patch (1 kb)]. So, it still could be launched from within an IDE like Eclipse but doesn't harm osx users and owners of slow machines. ;-) > SocketProtocolStressTest fails > ------------------------------- > > Key: GERONIMO-407 > URL: http://issues.apache.org/jira/browse/GERONIMO-407 > Project: Apache Geronimo > Type: Wish > Components: buildsystem > Versions: 1.0-M3 > Environment: Maven v. 1.0 > java version "1.4.2_05" > Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_05-b04) > Java HotSpot(TM) Client VM (build 1.4.2_05-b04, mixed mode) > Microsoft Windows 2000 [Version 5.00.2195] > Servie Pack 4 DE and current Updates > Computer: > AMD-K6(tm) 3D processor > 392.692 KB RAM ;-) > Reporter: Ralf Barkow > Assignee: Alan Cabrera > Priority: Minor > Attachments: modules_network.patch > > SocketProtocolStressTest testConcurrentRequests() constantly fails during > a maven build (cf. TIMEOUT problem, GERONIMO-160) but succeeds after a 'Run | > JUnit Test' from within Eclipse v. 3.0.1. > I'd like to have it excluded from unitTest in the file > modules/network/project.xml like DatagramProtocolTest (patch follows). > BTW: Could someone with Admin rights for jira add the network module to > the Component/s list. Thanks. > -- Ralf -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
