Hi Adrian, all I took some time to further investigate this and discovered something very strange.
The "org.apache.stanbol.enhancer.it.DefaultConfigTest" needs 800+MByte of Heap while execution. To be clear not on the Stanbol Server, but on the client! When this test is deactivated the memory requirement is about 40MByte. What is does is simple to explain: 1) it downloads the file http://{stanbol-host}/system/console/config/configuration-status-20110304-1743+0100.txt (this is around 3MByte Text) 2) uses REFEX to check if some patterns are contained in that file I think it was added by Bertrand to validate that loading OSGI configuration via the Sling launcher does work. This is implicitly checked by a lot of other tests because the Stanbol default configuration (including the loading of the DBpedia default data, enhancement chain ... ) is done using this feature. So I suggest to just remove this test. This would also allow us to remove the "ExampleBootstrapConfig" configuration file from the stanbol launcher that is just present to make this test complete successfully. WDYT Rupert On Tue, Jul 10, 2012 at 4:31 PM, Rupert Westenthaler <[email protected]> wrote: > Hi Adrian, > > On Tue, Jul 10, 2012 at 1:09 PM, Adrian Gschwend <[email protected]> wrote: >> On 09.07.12 21:33, Bertrand Delacretaz wrote: >> >>> OTOH it's good to have people run those tests on different platforms, >>> at least from time to time. >> >> Built finished now, some tests fail: >> > [..] >> Tests in error: >> testDefaultConfig(org.apache.stanbol.it.DefaultConfigTest): Java heap >> space >> > > This message indicated that the Stanbol server the test where run > against run out of memory. However to be sure you would need to > provide the *.txt files with Exceptions in the folder > >> Please refer to >> /usr/local/src/trunk/integration-tests/target/surefire-reports > > [..] >> Do I care about that and if so should I have at the logs and report here? >> > > If you can provide the logs It would be definitely interesting. I > recently inspected the memory requirements of the integration tests. > This tests showed that around 300MByte memory where needed. As the > limit is currently set to 512 MByte running out of memory during the > integration tests is definitely not expected. > > thx for the report > best > Rupert > > > > -- > | Rupert Westenthaler [email protected] > | Bodenlehenstraße 11 ++43-699-11108907 > | A-5500 Bischofshofen -- | Rupert Westenthaler [email protected] | Bodenlehenstraße 11 ++43-699-11108907 | A-5500 Bischofshofen
