java.lang.InternalError - No RenderingEngine module found

Omair Majid omajid at
Mon Mar 19 08:17:11 PDT 2012

On 03/19/2012 10:40 AM, Jiri Vanek wrote:
> On 03/17/2012 12:24 AM, Omair Majid wrote:
>> The attached patch works for me. It runs the test (which fails).
> Wooou! Tyvm for wise advice!

You are welcome :)

> In case this will be needed, will it be possible to apply this patch for
> icedtea-web head? If no - then only for tests running?

Since I wrote the patch (and wasn't ashamed enough to not post it
publicly), I am fine with it. It could use a review from others.

An alternate fix might be to stop (ab)using bootcalpath instead. Perhaps
-Xbootclasspath/a: might suffice.

>> That said, I am a little confused. Are you trying to use junit to run
>> entire applications and take screenshots and do comparisons? I am not
> 50/50% right and wrong :)
> What I want to is to enable reprodcures with gui, yes. But not complex
> applications.  For lunching comlex applications we are thinking little
> bit outside of junit sandbox, but it is in early stage of planing.

Hm.. still seems a little bit out of scope for junit but okay :)

>> sure if junit is the best tool for this. Perhaps a simple java program
>> will suffice (unless you need the various
>> annoations/methods/integration-support provided by junit).
> Will be probably needed. We can already now launch reproducers with gui,
> we can also run browsers (extension to this topic is coming) we can read
> the stdout/err of their runs, and we can generate quite useful outputs.
> but we cannot examine gui and we can not affect it. Awt robot should be
> more then helpful.
> Whole concept is working very well and I think this can just enrich it.
> The jnlp reprodcures are working quite well (Although I found nasty bug
> today inside the engine:-/), In-browser tests as I have designed them
> last week are also working very well. Do yo think it is really bad idea
> to include some more capacity by adding awt.robot in some future?

No, adding just the awt support cant hurt that much.

But we might want to take a step back at some point and ensure we are
using the right tool for the right task. JUnit is meant for unit tests
not for integration tests (our reproducers or complex applications). We
are writing quite a bit of extra code to do what we want (and that code
will have bugs). Is there something that can make our lives easier instead?


More information about the distro-pkg-dev mailing list