[aarch64-port-dev ] RFR: merge up to jdk8-b111
Andrew Haley
aph at redhat.com
Thu Dec 5 00:48:29 PST 2013
On 12/04/2013 07:12 PM, Andrew McDermott wrote:
>
> Andrew Haley <aph at redhat.com> writes:
>
>> On 12/03/2013 07:14 AM, Andrew McDermott wrote:
>>> Some of the errors are tests timing out. It appears that some tests are
>>> leaving spinning JVM processes which exacerbates the problem. I haven't
>>> looked into why this is.
>>
>> Are these regressions?
>
> I don't believe so. The spinning processes are coming from the
> `forever' loop in os::abort() which is not reachable for `release'
> builds.
Right, so this is a catastrophic failure.
> NOTE: these invocations still had the `forever' code enabled, hence the
> errors.
No, the errors are not due to the `forever' code. They are due to
the abort that triggered it. The idea is that you are supposed to
attach a debugger and find out why.
If you give me precise reproducer instructions I can have a look.
Andrew.
More information about the aarch64-port-dev
mailing list