RFR for JDK-7027502: Test failures in demo/jvmti/hprof testcases, need to be othervm
david.holmes at oracle.com
Fri Jan 10 10:37:21 UTC 2014
On 10/01/2014 6:40 PM, Staffan Larsen wrote:
> On 10 jan 2014, at 09:34, Alan Bateman <Alan.Bateman at oracle.com> wrote:
>> On 09/01/2014 23:20, Tristan Yan wrote:
>>> Hi David
>>> I wasn't able to reproduce this failure either in local or in our same binaries running(This is a continuous running with same JDK binaries). So intention for this code change is bringing this test back; add some debug info and try to avoid possible issues in this test. I agree this code change won't solve the failure happened. But this test was put into ProblemList two years ago better move for this is move out it from ProblemList and trace down the issue in our normal nightly.
>> If we can't duplicate it now, and the output from previously reported failures (in 2011) is insufficient to diagnose it properly, then it seems reasonable to add better output so as to improve our chances of understanding if it fails again. So better output + removing from the exclude list seems fine here. (cc'ing serviceability-dev as that is actually the mailing list for the HPROF and JVM TI areas).
> Sounds good to me,
I'm not sure what is actually being proposed. I don't really see
anything that would help diagnoze the original issue. But bring back the
test - maybe this was a bug elsewhere that has now been fixed.
More information about the core-libs-dev