RFR: 7903519 : jtreg/jtharness is missing features for basic crash testing

andrlos duke at openjdk.org
Wed Dec 13 11:36:02 UTC 2023


On Wed, 13 Dec 2023 10:29:39 GMT, Jiří Vaněk <jvanek at openjdk.org> wrote:

>> but.. shouldnt user know this already, since he would be the one to put the foreign implementation there? I would leave it up to user to notify himself in the status line that the result has been modified.. alternative would be to check the status after calling "tryModifyResult" and if its not the same status, appending String saying that the Status has been modified by external code.. :shrug:
>
> not necessarily. the one who set-up jtreg runner can be somebody else then who read the logs. Generally any jenkins infra - one person prepare generic runners, another jenkins jobs, and thne developer submit jdk, and read the results

I still believe it would be up to the user who meddles in it to properly document it.. but I can definitely try to put in a mechanism that compares the statuses and in case of difference adds a line to the status line

-------------

PR Review Comment: https://git.openjdk.org/jtharness/pull/57#discussion_r1425226976


More information about the jtharness-dev mailing list