-
Bug
-
Resolution: Fixed
-
P3
-
6
-
b51
-
x86
-
windows
This bug affects the following NSK tests:
nsk/jvmpi/DisableEvent/disablev001
nsk/jvmpi/EnableEvent/enablev001
nsk/jvmpi/GetThreadStatus/thrstat001
These tests started failing when I synced up with main/baseline
after last week's c2_baseline push:
20050824132849.sgoldman.c2_merge
Below is the entry from my nightly analysis report:
New nsk.quick_jvmpi failures (from 2005.08.25)
* nsk/jvmpi/DisableEvent/disablev001
* nsk/jvmpi/EnableEvent/enablev001
* nsk/jvmpi/GetThreadStatus/thrstat001
These tests failed with exit code 128 on Win32 Client VM (machine
dantooine). The .err and .out files are empty.
Update: These three failure reproduced on the 2005.08.26 run
on a different Client VM machine (vmnightly8). Looks like
a real regression in the c2_baseline push.
Update: 2005.08.29 run reproduced on machine bothawui.
Steve G. has been investigating the failures and asked me
to file the bug on his behalf.
nsk/jvmpi/DisableEvent/disablev001
nsk/jvmpi/EnableEvent/enablev001
nsk/jvmpi/GetThreadStatus/thrstat001
These tests started failing when I synced up with main/baseline
after last week's c2_baseline push:
20050824132849.sgoldman.c2_merge
Below is the entry from my nightly analysis report:
New nsk.quick_jvmpi failures (from 2005.08.25)
* nsk/jvmpi/DisableEvent/disablev001
* nsk/jvmpi/EnableEvent/enablev001
* nsk/jvmpi/GetThreadStatus/thrstat001
These tests failed with exit code 128 on Win32 Client VM (machine
dantooine). The .err and .out files are empty.
Update: These three failure reproduced on the 2005.08.26 run
on a different Client VM machine (vmnightly8). Looks like
a real regression in the c2_baseline push.
Update: 2005.08.29 run reproduced on machine bothawui.
Steve G. has been investigating the failures and asked me
to file the bug on his behalf.