On Thu, 5 Sep 2024 09:59:51 GMT, Jaikiran Pai <j...@openjdk.org> wrote:
> Hello Fernando, I'm not familiar with this test or the area, but if this > change is just to make available jtreg logs (in a separate file) to allow for > debugging a currently intermittent test failure, then there are ways to > change the jtreg output log limit in our CI, without having to change the > test code - I can show you the command, offline, to do that. As far as I remember, we don't have a precedence of changing tests to write out to additional locations to bypass the jtreg log limit. Thanks for the review. I removed the additional file and updated the test properties to increment maxOutputSize. This approach is more commonly used in other tests. ------------- PR Comment: https://git.openjdk.org/jdk/pull/20838#issuecomment-2332131291
