Changing error to println to prevent misinterpretation

[adamfarley]

To prevent this message being interpreted as cause for failure in and of itself, I'm changing this to a println.

Tested here.

Note: I'm also hoping this prevents the pipeline job from interpreting an unstable job as a cause for overall failure. Since this doesn't break anything, I advocate putting this change in anyway and running a big pipeline to test it in anger.

[github-actions]

Thank you for creating a pull request!

Please check out the information below if you have not made a pull request here before (or if you need a reminder how things work).

Code Quality and Contributing Guidelines

If you have not done so already, please familiarise yourself with our Contributing Guidelines and Code Of Conduct, even if you have contributed before.

Tests

Github actions will run a set of jobs against your PR that will lint and unit test your changes. Keep an eye out for the results from these on the latest commit you submitted. For more information, please see our testing documentation.

In order to run the advanced pipeline tests (executing a set of mock pipelines), it requires an admin to post run tests on this PR.
If you are not an admin, please ask for one's attention in #infrastructure on Slack or ping one here.
To run full set of tests, use "run tests"; a subset of tests on specific jdk version, use "run tests quick 11,20"

[andrew-m-leonard]

lgtm thanks

[andrew-m-leonard]

run tests

[sxa]

+1 from me but we can wait for hte pipeline test to finish before mergingm

[eclipse-temurin-bot]

 PR TESTER RESULT 

❎ Some pipelines failed or the job was aborted! ❎
See the pipeline-build-check below for more information...

[github-actions]

Thank you for creating a pull request!

Please check out the information below if you have not made a pull request here before (or if you need a reminder how things work).

Code Quality and Contributing Guidelines

If you have not done so already, please familiarise yourself with our Contributing Guidelines and Code Of Conduct, even if you have contributed before.

Tests

Github actions will run a set of jobs against your PR that will lint and unit test your changes. Keep an eye out for the results from these on the latest commit you submitted. For more information, please see our testing documentation.

In order to run the advanced pipeline tests (executing a set of mock pipelines), it requires an admin to post run tests on this PR.
If you are not an admin, please ask for one's attention in #infrastructure on Slack or ping one here.
To run full set of tests, use "run tests"; a subset of tests on specific jdk version, use "run tests quick 11,20"

[karianna]

@adamfarley Looks like some failures for jdk20u on Windows and the pipeline-build-check

[adamfarley]

@adamfarley Looks like some failures for jdk20u on Windows and the pipeline-build-check

Looks like the failure on Windows wasn't anywhere near my code, so I'm going to merge this check anyway. My code executes prior to the build, and the failure appears to occur after the build stopped outputting for 40-ish minutes and @steelhead31 aborted it.

Also, I believe the pipeline-build-check is the superset of the test builds, including Windows jdk20u. FYI.