OK, thanks for the update. The comment/behavior is noted, though. I've
tried hard to make it easier to debug test failures, and first
impressions from a "newcomer" are always valuable.
For my part, I find that running all javadoc tests is "fairly fast" and
running any one test is "very fast", so it becomes practical to work
through the first few reported issues in any test failure, and rerun.
-- Jon
On 3/7/19 2:23 PM, Derek Thomson wrote:
Thanks Jonathan. This might have been a false alarm - I'm finding that
as I fix the errors caused by my change the other failures in the same
test seem to just disappear, even though they were (to my eye)
matching against unrelated sections of the HTML. Let me finish up, and
I bet it'll be fine after all.
If any are left broken after that, I'll raise them here.
On Thu, Mar 7, 2019 at 2:18 PM Jonathan Gibbons
<[email protected] <mailto:[email protected]>> wrote:
On 3/7/19 2:01 PM, Jonathan Gibbons wrote:
>
>
> If you are seeing tests that fail, I suggest you discuss them here
> first, before embarking on any additional campaign to get them
> working. Given the number of CI systems building and testing
OpenJDK
> on all platforms, I would be very surprised to hear of tests
failing
> in an unmodified repo.
>
... I should be more specific: if you are seeing tests failing for
reasons unrelated to your change ....
-- Jon
