RFR: JDK-8191933 Use failure handler in run-test
Martin Buchholz
martinrb at google.com
Wed Nov 29 23:03:46 UTC 2017
jtreg is already hard to build. I see my own build script
defining JDK17HOME JDK18HOME JDK19HOME.
Optionally using features when a jdk is sufficiently up to date is
annoyingly difficult, but that's what java programmers everywhere do,
typically using reflection.
On Wed, Nov 29, 2017 at 1:08 PM, Jonathan Gibbons <
jonathan.gibbons at oracle.com> wrote:
> One reason it is difficult to move some of this into jtreg itself is
> because some
> of these handlers use recent/new APIs. That makes writing and/or building
> jtreg
> that much harder. But I agree in general with the overall goal of moving
> stuff
> into jtreg when it is practical to do so.
>
> -- Jon
>
>
> On 11/28/2017 02:03 PM, Martin Buchholz wrote:
>
>> Every jtreg run would like to have the most helpful failure handling
>> possible. Should some/all of this be pushed into jtreg itself instead of
>> the makefiles?
>>
>> On Mon, Nov 27, 2017 at 1:39 PM, Magnus Ihse Bursie <
>> magnus.ihse.bursie at oracle.com> wrote:
>>
>> The jtreg failure handler needs to be used when running tests using the
>>> run-test framework.
>>>
>>> Bug: https://bugs.openjdk.java.net/browse/JDK-8191933
>>> WebRev: http://cr.openjdk.java.net/~ihse/JDK-8191933-use-failure-han
>>> dler-in-run-test/webrev.01
>>>
>>> /Magnus
>>>
>>>
>>>
>
More information about the build-dev
mailing list