Thanks for the info.  I won't do a rollback of 3413 unless someone else sees
the same failure and reports it to the dev list.

On 3/26/07, Tony Wu <[EMAIL PROTECTED]> wrote:

Hi Weldon,
This message indicates that vm crashed when running
java.lang.ThreadGroupTest. I think we got the last changed date and
last log according to "svn info" and "svn log" on your local working
copy, so, H3413 possibly is not the guilty commit.

On 3/27/07, Weldon Washburn <[EMAIL PROTECTED]> wrote:
> All,
>
> I don't completely understand  the messages that are sent to
> [EMAIL PROTECTED]@apache.org.  Below is the first few lines of a message
sent
> recently.  It says H3413 is causing build failure.  I will rollback if
this
> is indeed the case.  So far, I have been unable to reproduce this
failure on
> my single CPU 32-bit laptop running winxp servicepack 2.  Some questions
and
> observations:
>
> 1)
> I assume cruise control is only running 32-bit windows at this
point.  It
> seems the alerts emails do not specifically mention win32.  They only
> mention windows and nothing about 32/64.
>
> 2)
> Is anyone else seeing this failure?  If true, is it intermittant?  Are
you
> running on a multiprocessor?
>
>
> BUILD FAILED:
>
> Ant Error Message:
>
> C:\cruise\trunk\cc\projects\classlib\trunk\build.xml:167: The following
> error occurred while executing this line:
> C:\cruise\trunk\cc\projects\classlib\trunk\make\build-test.xml:138:
There
> were test crashes:
> C:\cruise\trunk\cc\projects\classlib\trunk\build\test_report\TEST-
> org.apache.harmony.luni.tests.java.lang.ThreadGroupTest.xml
>
> Date of build: 03/26/2007 10:10:32
>
> Time to build: 37 minutes 55 seconds
>
> Last changed: 03/24/2007 19:55:07
>
> Last log entry: H3413, refactor, cleanup of exception safepoint callback
>
> build, build-test passes on win32 and rhel4.0, gcc 4.0.2
>
>
>
> --
> Weldon Washburn
> Intel Enterprise Solutions Software Division
>


--
Tony Wu
China Software Development Lab, IBM




--
Weldon Washburn
Intel Enterprise Solutions Software Division

Reply via email to