On the 0x23D day of Apache Harmony Alexander Kleymenov wrote: > Egor, > > Thank you for pointing this out! > Currently there are two pending patches finishing the implementation > of the infrastructure (particularly HARMONY-2416 and HARMONY-2540). > And if your patch will be applied before them it will cause conflict > and reimplementation of supplied patches. As I see your patch is > simple and can be easily fixed to feet on top of other. So, please, > indicate this in JIRA report you have filed. Especially that your > patch should be applied after framework will be finished (i.e. H-2416 > and H2540 will be applied).
OK, I have put the dependency links to these issues. You can update your patch to HARMONY-2540 to include my trivial fix. That would be the fastest way to apply the necessary changes. Anyway, I can rework my patch if you do not feel like doing that) BTW, Some other bugs also depend on the HARMONY-2540 resolution, for example: HARMONY-2259 and HARMONY-2261 because they depend on non-automatic test integration which is fixed with HARMONY-2540. I would suggest to commit HARMONY-2540 and HARMONY-2416 _ASAP_ because they do not break anything, and have several important issues depending on them. > Regards, > Alexander > > On 11 Dec 2006 12:23:38 +0600, Egor Pasko <[EMAIL PROTECTED]> wrote: > > Alexander, > > > > I found a small bug in passing parameters to JVM from > > reg.test. Please, look at the fix in HARMONY-2565. > > > > On the 0x235 day of Apache Harmony Alexander Kleymenov wrote: > > > Hello, > > > > > > I've made an attempt to resolve the issue with JVM crashes during the > > > test run. The appropriate patch for DRLVM workspace is provided with > > > HARMONY-2416 report [1]. This patch extends default functionality of > > > Ant's <junit> task with JVM crash handling means. The visible benefits > > > of such an approach are: > > > 1. There is no need in new test format (java classes with main > > > function returning predefined result code). So most of the testes can > > > be implemented in JUnit format. > > > 2. This approach preserves standard test result reporting > > > functionality (trough XML to HTML reports) and there is no need to > > > implement it as in case of using of new test format. > > > 3. It's easy to switch between standard and enhanced test > > > execution. The <junit> task redefining can be made dependable on some > > > switch. > > > > > > To try the patch, just apply it on the built DRLVM workspace, than > > > make "ant update", and then "ant reg.test". The test results in html > > > format will be placed in semis/reg.tests/reports/html directory under > > > the DRLVM's build directory. Note that H000 regression test is failed > > > because of DRLVM crash. > > > > > > Please, try the patch and give your thoughts and advices about it. > > > > > > So with this patch the current status of regression testing > > > infrastructure is as follows: > > > 1. There are the working means for automated regression testing > > > and report generation. > > > 2. The test format for regression test is JUnit. The sources for > > > regression tests are placed in src/test/regression/Hxyz directories, > > > where Hxyz is named according to corresponding JIRA report. > > > 3. There are 4 regression tests included in the regression test suite. > > > 4. I'm working on automated test integration (don/t list each > > > particular test in reg.test.xml file, but search them automatically). > > > 5. I'm working on document describing directions for developers of > > > new regression tests. > > > 6. Existing regression tests under src/test directory will be > > > integrated to regression test suite. > > > 7. It is ready to be used by cruise control system. > > > > > > Thank you, > > > Alexander Kleymenov > > > > > > [1] http://issues.apache.org/jira/browse/HARMONY-2416 > > > > > > > -- > > Egor Pasko > > > > > -- Egor Pasko
