Tim Jacomb

I think it only works in Safari

hmm I think it used to work =/ (not that it was that useful)

any reason this is still in draft?

Not sure if I quite get this, you say https://user-images.githubusercontent.com/5233413/174359582-1b1b2d92-ee71-4601-aa76-641ce0d873b3.png is okay but it looks the same to me.

Yeah I guess not needed assuming junit-sql-storage works with h2. It's currently tested with Postgres automatically and has been manually tested with MySQL

can you explain more? Or sketch up a mock up? I don't really understand what the URL is for

Interested in providing a PR? With a test ideally

The issue is that there’s large performance impact of storing huge stack traces I believe, as they can be kept in memory and shown on pages @jglick probably knows more

https://plugins.jenkins.io/junit-sql-storage/ > IIRC the whole junitResults.xml file will be parsed into in-heap objects when using the default storage. There is no such thing as random access here (barring weird hacks...

both is fine with me, contributions welcome. Especially documentation fixes