Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8288919 | 20 | Daniel Daugherty | P3 | Resolved | Fixed | b03 |
JDK-8291278 | 19.0.2 | Daniel Daugherty | P3 | Resolved | Fixed | b01 |
JDK-8291126 | 19.0.1 | Daniel Daugherty | P3 | Resolved | Fixed | b04 |
A couple of post-integration review comments for:
JDK-8286830 ~HandshakeState should not touch oops
should get resolved:
test/hotspot/jtreg/runtime/Thread/StopAtExit.java
};
threadCreator.setDaemon(true);
threadCreator.start();
test(timeMax);
Member
@dcubed-ojdk dcubed-ojdk 12 days ago
Okay, but now the test is going to execute for twice timeMax which might be
a bit of a surprise... In particular the usage() mesg is now wrong.
Member
@dcubed-ojdk dcubed-ojdk 12 days ago
Also, the @bug line is not updated with this bug ID.
Member Author
@pchilano pchilano 12 days ago
Ok, we could fix this in a new bug.
and
test/hotspot/jtreg/runtime/Thread/SuspendAtExit.java
};
threadCreator.setDaemon(true);
threadCreator.start();
test(timeMax);
Member
@dcubed-ojdk dcubed-ojdk 12 days ago
Okay, but now the test is going to execute for twice timeMax which might be
a bit of a surprise... In particular the usage() mesg is now wrong.
Member
@dcubed-ojdk dcubed-ojdk 12 days ago
Also, the @bug line is not updated with this bug ID.
Member Author
@pchilano pchilano 12 days ago
Ok, we could fix this in a new bug.
should get resolved:
test/hotspot/jtreg/runtime/Thread/StopAtExit.java
};
threadCreator.setDaemon(true);
threadCreator.start();
test(timeMax);
Member
@dcubed-ojdk dcubed-ojdk 12 days ago
Okay, but now the test is going to execute for twice timeMax which might be
a bit of a surprise... In particular the usage() mesg is now wrong.
Member
@dcubed-ojdk dcubed-ojdk 12 days ago
Also, the @bug line is not updated with this bug ID.
Member Author
@pchilano pchilano 12 days ago
Ok, we could fix this in a new bug.
and
test/hotspot/jtreg/runtime/Thread/SuspendAtExit.java
};
threadCreator.setDaemon(true);
threadCreator.start();
test(timeMax);
Member
@dcubed-ojdk dcubed-ojdk 12 days ago
Okay, but now the test is going to execute for twice timeMax which might be
a bit of a surprise... In particular the usage() mesg is now wrong.
Member
@dcubed-ojdk dcubed-ojdk 12 days ago
Also, the @bug line is not updated with this bug ID.
Member Author
@pchilano pchilano 12 days ago
Ok, we could fix this in a new bug.
- backported by
-
JDK-8288919 additional review changes for JDK-8286830
-
- Resolved
-
-
JDK-8291126 additional review changes for JDK-8286830
-
- Resolved
-
-
JDK-8291278 additional review changes for JDK-8286830
-
- Resolved
-
- relates to
-
JDK-8288497 add support for JavaThread::is_oop_safe()
-
- Resolved
-
-
JDK-8286830 ~HandshakeState should not touch oops
-
- Closed
-
(2 links to)