On Fri, 12 Feb 2021 14:47:31 GMT, Stanimir Stamenkov <github.com+1247730+sta...@openjdk.org> wrote:
>> Yeah, sure. Likely, this kind of issue will be reproducible in other >> environments if it fails. >> My initial idea during #1759 was to show a frame which would be useful >> during debugging. >> >> I hope it will never fail again. :) >> >> Anyway, I'm okay with whatever solution @stanio implements. The easiest one, >> however, is to use the second parameter to save the image. Sometimes it's >> useful to have the image captured even when the test does not fail. > > I had thought it would be most useful to have it save an image capture on > failure during an automated run, but I was not sure what file path is > possible/appropriate to use – would using the current working directory be > o.k.? I may fix the image capture file then, and possibly use a program > argument just to force saving a successful run capture – does it sound o.k.? Current directory is fine. The test harness sets it before running the test and then it captures the files there. When running the test manually, the current directory is also the most intuitive choice. ------------- PR: https://git.openjdk.java.net/jdk/pull/2515
