The following VM/NSK tests failed in the 2011.03.02 nightly:

    nsk/jvmti/RedefineClasses/redefclass028
    nsk/jvmti/RedefineClasses/redefclass029
    nsk/jvmti/RedefineClasses/redefclass030
    nsk/jvmti/scenarios/capability/CM02/cm02t001
    nsk/jvmti/scenarios/events/EM02/em02t003
    nsk/jvmti/scenarios/events/EM07/em07t002
    nsk/jvmti/scenarios/hotswap/HS101/hs101t001
    nsk/jvmti/scenarios/hotswap/HS101/hs101t002
    nsk/jvmti/scenarios/hotswap/HS101/hs101t003
    nsk/jvmti/scenarios/hotswap/HS101/hs101t004
    nsk/jvmti/scenarios/hotswap/HS101/hs101t006
    nsk/jvmti/scenarios/hotswap/HS102/hs102t001
    nsk/jvmti/scenarios/hotswap/HS102/hs102t002
    nsk/jvmti/scenarios/multienv/MA10/ma10t006

The assertion failure looks like:

# Internal Error (c:\temp\jprt\p3\b\161826.zg131198\source\src\share\vm\code/nmethod.hpp:449), pid=3592, tid=4472
# assert(!_oops_are_stale) failed: oops are stale
#
# JRE version: 7.0-b131
# Java VM: Java HotSpot(TM) 64-Bit Server VM (21.0-b03-internal-201103021618.zg131198.hotspot-fastdebug compiled mode windows-amd64 )


The hs_err_pid file does not contain a stack trace.