Building Penrose

[David Bosschaert]

The honest truth is that I didn't know how long it would take when I
wrote the blog and I was too impatient to wait for it to complete. It
was running tests as far as I could see :)
I let it run for a full night and when I returned to look at it in the
morning it was stuck somewhere in the test runs. Probably similar to
what you were seeing.

At least the good news is that the partial test runs (the ones where
you invoke jtreg with a file or a directory) do complete relatively
quickly. I'm still trying to figure out how to do debugging with those
in an IDE [1] - if someone has any tips for that this woud be
appreciated :)

Cheers,

David

[1] http://mail.openjdk.java.net/pipermail/jigsaw-dev/2012-February/002215.html

On 1 March 2012 17:32, Scott Stark <sstark at redhat.com> wrote:
> Can you define "above takes a very long time" from your blog when referring to the "make test" step? I killed the test run after about 18 hours since it was still running and burning a lot of cpu in the fedora vm it was running in. Looking back through some of the test output, I see a number of timeouts:
>
> TEST RESULT: Failed. Execution failed: `main' threw exception: sun.awt.SunToolkit$OperationTimedOut: 10002
>
>
> ----- Original Message -----
> From: "David Bosschaert" <david.bosschaert at gmail.com>
> To: penrose-dev at openjdk.java.net
> Sent: Wednesday, February 29, 2012 11:28:33 AM
> Subject: Re: Building Penrose
>
> ...
>
> In the mean time I figured out how to run the tests, for those who are
> interested, you can read my findings here:
> http://coderthoughts.blogspot.com/2012/02/running-penrose-or-openjdk-8-tests.html
>
> Best regards,
>
> David