Community
Participate
Working Groups
+++ This bug was initially created as a clone of Bug #342936 +++ We have made the tests more resilient but we should still investigate why we don't get the compiler in the test setup. Not high prio.
Could it be relate to code coverage ? I guess it something goes wrong while loading the default compiler, then it might return null. Kim, is it possible to run these tests again and see if there is anything interesting in the logs.
Sure, I can rerun them. Olivier, do you have a preference for the vm to run them with - Oracle or IBM?
(In reply to comment #1) > Could it be relate to code coverage ? I guess it something goes wrong while > loading the default compiler, then it might return null. > Kim, is it possible to run these tests again and see if there is anything > interesting in the logs. Didn't we already disable code coverage on the latest Oracle Java 7 run?(In reply to comment #2) > Sure, I can rerun them. Olivier, do you have a preference for the vm to run > them with - Oracle or IBM? Please use Oracle for now. Unfortunately the latest IBM results don't have the logs.
Yes, code coverage was disabled when I ran them.
I guess we can close this for now.