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

[Jiří Vaněk]

On Wed, 13 Dec 2023 10:18:50 GMT, andrlos <duke at openjdk.org> wrote:

>> src/com/sun/javatest/Script.java line 496:
>> 
>>> 494:             searchResultModifier();
>>> 495:         }
>>> 496:         return resultModifier.modifyStatus(proposedStatus, td);
>> 
>> maybe if a foreign code changed status result,  the FQN of class should be logged.
>
> 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

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

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