Re: RFR: JDK-8066993: nsk.jdi.EventRequest.setEnabled.setenabled003 fails: event IS NOT a breakpoint
Right now I'm proposing we use the bug number that matches the entry in
the ProblemList to
remove the test from the ProblemList.
The other matching rules that were added for connection closed and the
other bugs with connection closed had no valid reason for attaching
to a bug with a specific error in a specific test. Since the other tests
were never added to the ProblemList, they obviously have not failed
in a long time. If those errors show up, new bugs should be filed.
This changeset would end up in jdk13. Since this change is specific
to the ProblemList, backports to the older releases would have to be
retested in those builds, if neeeded.
Presumably some other fix has made it so this test no longer is failing.
On 2/13/19 2:37 PM, Chris Plummer wrote:
Hi Gary,
Looks good. What are your plans for bug management? I think the CR
should actually be closed as CNR and removal from the problemlist be
done as a subtask.
Also, there are a lot of other failures reported with other tests
under this bug. Kind of became a dumping ground, but none of them
resulted in tests being quarantined. All of the reported failures seem
to be with 8u60, and they probably still happen there. I'm not sure of
the right procedure for closing out the bug in that case since no fix
is being provided, so no backport can be done. Also, the affects
versions includes 9 and 10. I think at some point Jerry reproduced
something on 10, but didn't give any details. I'm not sure how to
address that either.
Chris
On 2/13/19 8:53 AM, Gary Adams wrote:
The setenabled003 test has been on the ProblemList since it was first
moved to the open repos. After 1000 test runs on {solaris, macosx,
windows, linux}
for the test/hotspot/jtreg/vmTestbase/nsk/jdi/EventRequest/setEnabled
tests,
the problem does not currently reproduce.
My recommendation is that we remove it from the ProblemList at this
time.
diff --git a/test/hotspot/jtreg/ProblemList.txt
b/test/hotspot/jtreg/ProblemList.txt
--- a/test/hotspot/jtreg/ProblemList.txt
+++ b/test/hotspot/jtreg/ProblemList.txt
@@ -161,10 +161,8 @@
vmTestbase/nsk/jdi/ThreadReference/resume/resume001/TestDescription.java
8072701 generic-all
vmTestbase/nsk/jdi/ThreadReference/stop/stop001/TestDescription.java
7034630 generic-all
vmTestbase/nsk/jdi/BScenarios/hotswap/tc10x001/TestDescription.java
8013728 generic-all
-vmTestbase/nsk/jdi/EventRequest/setEnabled/setenabled003/TestDescription.java
8066993 generic-all
vmTestbase/nsk/jdi/VirtualMachine/redefineClasses/redefineclasses021/TestDescription.java
8065773 generic-all
vmTestbase/nsk/jdi/VirtualMachine/redefineClasses/redefineclasses023/TestDescription.java
8065773 generic-all
Re: RFR: JDK-8066993: nsk.jdi.EventRequest.setEnabled.setenabled003 fails: event IS NOT a breakpoint
Hi Gary,
Looks good. What are your plans for bug management? I think the CR
should actually be closed as CNR and removal from the problemlist be
done as a subtask.
Also, there are a lot of other failures reported with other tests under
this bug. Kind of became a dumping ground, but none of them resulted in
tests being quarantined. All of the reported failures seem to be with
8u60, and they probably still happen there. I'm not sure of the right
procedure for closing out the bug in that case since no fix is being
provided, so no backport can be done. Also, the affects versions
includes 9 and 10. I think at some point Jerry reproduced something on
10, but didn't give any details. I'm not sure how to address that either.
Chris
On 2/13/19 8:53 AM, Gary Adams wrote:
The setenabled003 test has been on the ProblemList since it was first
moved to the open repos. After 1000 test runs on {solaris, macosx,
windows, linux}
for the test/hotspot/jtreg/vmTestbase/nsk/jdi/EventRequest/setEnabled
tests,
the problem does not currently reproduce.
My recommendation is that we remove it from the ProblemList at this time.
diff --git a/test/hotspot/jtreg/ProblemList.txt
b/test/hotspot/jtreg/ProblemList.txt
--- a/test/hotspot/jtreg/ProblemList.txt
+++ b/test/hotspot/jtreg/ProblemList.txt
@@ -161,10 +161,8 @@
vmTestbase/nsk/jdi/ThreadReference/resume/resume001/TestDescription.java
8072701 generic-all
vmTestbase/nsk/jdi/ThreadReference/stop/stop001/TestDescription.java
7034630 generic-all
vmTestbase/nsk/jdi/BScenarios/hotswap/tc10x001/TestDescription.java
8013728 generic-all
-vmTestbase/nsk/jdi/EventRequest/setEnabled/setenabled003/TestDescription.java
8066993 generic-all
vmTestbase/nsk/jdi/VirtualMachine/redefineClasses/redefineclasses021/TestDescription.java
8065773 generic-all
vmTestbase/nsk/jdi/VirtualMachine/redefineClasses/redefineclasses023/TestDescription.java
8065773 generic-all
RFR: JDK-8066993: nsk.jdi.EventRequest.setEnabled.setenabled003 fails: event IS NOT a breakpoint
The setenabled003 test has been on the ProblemList since it was first
moved to the open repos. After 1000 test runs on {solaris, macosx,
windows, linux}
for the test/hotspot/jtreg/vmTestbase/nsk/jdi/EventRequest/setEnabled tests,
the problem does not currently reproduce.
My recommendation is that we remove it from the ProblemList at this time.
diff --git a/test/hotspot/jtreg/ProblemList.txt
b/test/hotspot/jtreg/ProblemList.txt
--- a/test/hotspot/jtreg/ProblemList.txt
+++ b/test/hotspot/jtreg/ProblemList.txt
@@ -161,10 +161,8 @@
vmTestbase/nsk/jdi/ThreadReference/resume/resume001/TestDescription.java
8072701 generic-all
vmTestbase/nsk/jdi/ThreadReference/stop/stop001/TestDescription.java
7034630 generic-all
vmTestbase/nsk/jdi/BScenarios/hotswap/tc10x001/TestDescription.java
8013728 generic-all
-vmTestbase/nsk/jdi/EventRequest/setEnabled/setenabled003/TestDescription.java
8066993 generic-all
vmTestbase/nsk/jdi/VirtualMachine/redefineClasses/redefineclasses021/TestDescription.java
8065773 generic-all
vmTestbase/nsk/jdi/VirtualMachine/redefineClasses/redefineclasses023/TestDescription.java
8065773 generic-all
