--
You received this message because you are subscribed to the Google Groups "indigo-bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to indigo-bugs...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Hello Joos,
Unfortunately I cannot not reproduce this problem. Usually we test Indigo rendering with 100 threads and everything works fine. Could you please send me a failing test example?
Best regards,
Mikhail.
On Jul 25, 2013, at 15:08 , joos....@gmail.com wrote:
There is an issue in Indigo 1.1.11 which I have trouble at pin-pointing. After upgrading from Indigo 1.1.10 a Unit test fails when running all unit tests (eg. alt+F6 in netbeans) with nullpointerexception. However when running the test individually it passes. I assume it has to do with the amount of indigo instances maybe that were created?
java.lang.NullPointerException
at com.ggasoftware.indigo.Indigo.setSessionID(Indigo.java:360)
at com.ggasoftware.indigo.Indigo.setOption(Indigo.java:364)
at org.bitbucket.kienerj.moleculedatabaseframework.io.IndigoMoleculeRenderer.setRenderingOptions(IndigoMoleculeRenderer.java:359)
-> indigo.setOption("render-output-format", "png");
Because the test works when run alone I can't debug the issue as then everything works.
Any ideas? 1.1.10 works perfectly fine!
--
You received this message because you are subscribed to the Google Groups "indigo-bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to indigo-bugs+unsubscribe@googlegroups.com.