DO NOT REPLY [Bug 10413] - enhancement: JUnit task only creates one forked VM per batch
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=10413. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=10413 enhancement: JUnit task only creates one forked VM per batch [EMAIL PROTECTED] changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution||DUPLICATE Target Milestone|--- |1.6.2 --- Additional Comments From [EMAIL PROTECTED] 2004-04-21 06:33 --- I worked on bug 24697 and finally implemented the enhancement without realizing that this bug here exists. So the functionality is supposed to be there now. *** This bug has been marked as a duplicate of 24697 *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 10413] - enhancement: JUnit task only creates one forked VM per batch
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=10413. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=10413 enhancement: JUnit task only creates one forked VM per batch --- Additional Comments From [EMAIL PROTECTED] 2004-03-29 14:57 --- Thanks for the pointer. I've tested that patch, and it worked fine for me, except for the fact that it's 1.5.3 based, when I was running 1.6 beta at the time (didn't have if/unless on formatters for example). I can also only use released Ant versions, and even need compelling arguments to upgrade, since that implies tedious manipulations to upgrade the Ant within IntelliJ (which doesn't support using an external Ant!!!) So I'm just waiting for an equivalent feature out of Ant proper. Thanks, --DD - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 10413] - enhancement: JUnit task only creates one forked VM per batch
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=10413. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=10413 enhancement: JUnit task only creates one forked VM per batch --- Additional Comments From [EMAIL PROTECTED] 2004-03-28 03:25 --- You may also want to look at Bug 24697, which contains a backwards compatible patch. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 10413] - enhancement: JUnit task only creates one forked VM per batch
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10413. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10413 enhancement: JUnit task only creates one forked VM per batch --- Additional Comments From [EMAIL PROTECTED] 2004-01-07 10:50 --- Cleaning up is what teardown() methods are meant to be for, and like DD says, this is optional. Also I've found java to be less contaminated by bad test than say, Cpp unit, where a pointer defect or failure to release a reference in one test case destroys all that follow it. Therefore I think a single VM for all forked tests could be a good addition -those projects with many tests will appreciate it; we just need to do it in a way that integrates with everything. DD: try applying these patches and tell me what you think? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 10413] - enhancement: JUnit task only creates one forked VM per batch
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10413. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10413 enhancement: JUnit task only creates one forked VM per batch --- Additional Comments From [EMAIL PROTECTED] 2004-01-06 13:46 --- True, but you're free not to use this new feature. Forking all tests, one of my test target takes 7+ minutes, instead of around 1 minute forking only once (using the proposed change). This is a HUGE difference to me, and it's also one that is a deal breaker for developers. 7+ minutes is just too long. That's the difference between willingly running all the tests all the time, and not running them! I *very strongly* support adding this feature to junit. I'm not attached in any way to the proposed patch, but I really NEED this feature. --DD - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 10413] - enhancement: JUnit task only creates one forked VM per batch
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10413. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10413 enhancement: JUnit task only creates one forked VM per batch --- Additional Comments From [EMAIL PROTECTED] 2004-01-05 16:42 --- Solving this bug will pose a new problem. Having tests run in the same VM seems less powerful than running the test in a clean one: suppose, for example, that your project heavily relies on static object caches (as does mine). When running a long batch of tests, later tests may use a previously- created object from the cache, instead of using the clean object that will be created on a separate VM. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 10413] - enhancement: JUnit task only creates one forked VM per batch
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10413. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10413 enhancement: JUnit task only creates one forked VM per batch --- Additional Comments From [EMAIL PROTECTED] 2003-07-24 00:32 --- This may not be helpful in terms of getting to a good solution, but I am attaching a quick and dirty hack I have been using for a while. It basically modifies the test runner so that when the JUnit tests are forked, they get executed together. Each test still generates its own TEST-*.xml as if it had executed in separate VMs. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 10413] - enhancement: JUnit task only creates one forked VM per batch
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10413. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10413 enhancement: JUnit task only creates one forked VM per batch --- Additional Comments From [EMAIL PROTECTED] 2003-07-24 00:34 --- Created an attachment (id=7480) Quick hack - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 10413] - enhancement: JUnit task only creates one forked VM per batch
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10413. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10413 enhancement: JUnit task only creates one forked VM per batch --- Additional Comments From [EMAIL PROTECTED] 2003-07-24 00:34 --- Created an attachment (id=7481) Quick hack - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 10413] - enhancement: JUnit task only creates one forked VM per batch
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10413. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10413 enhancement: JUnit task only creates one forked VM per batch --- Additional Comments From [EMAIL PROTECTED] 2003-07-16 09:15 --- Haven't looked at the code but I would have expected that the XML formatter should be able to determine what hierarchy to produce from the test class package names, irrespective of whether they're in one suite or multiple suites. Taking this approach would also allow other TestSuite builder utilities to use the XML formatter effectively. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 10413] - enhancement: JUnit task only creates one forked VM per batch
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10413. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10413 enhancement: JUnit task only creates one forked VM per batch --- Additional Comments From [EMAIL PROTECTED] 2003-07-15 16:20 --- I've obtained a copy of Richard's code via email and discussed it with him. As it works via a DynamicTestSuite it actually works the same as if you have a 'TestAll' TestSuite which recursively composes all your TestCases. So the resultant output is a single TEST-xx file. This means you don't get the nice package tree structure to your test results from the junitreport task. I'd prefer any final solution to this request to produce output in the same way as the current batchtest task does. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 10413] - enhancement: JUnit task only creates one forked VM per batch
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10413. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10413 enhancement: JUnit task only creates one forked VM per batch [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |ASSIGNED --- Additional Comments From [EMAIL PROTECTED] 2003-07-14 07:21 --- I think this would be a good enhancement to have. Are you intending to contribute the code? The URL above was not responding. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 10413] - enhancement: JUnit task only creates one forked VM per batch
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10413. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10413 enhancement: JUnit task only creates one forked VM per batch [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Additional Comments From [EMAIL PROTECTED] 2003-03-20 07:05 --- *** Bug 14354 has been marked as a duplicate of this bug. ***
