Disable jdk17 reproducible comparison builds

[sophia-guo]

Signed-off-by: Sophia Guo sophia.gwf@gmail.com

[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,21"

[sxa]

There's no description or issue reference on this PR - why are we disabling it?

[andrew-m-leonard]

I realise the jdk17u compares have been red for a while, and we need to have a look at them, but is there another reason to remove them?

[sophia-guo]

@jiekang mentioned it's not needed anymore for 17 and we only need to focus on 21. Not in a hurry we can wait until he's back and double check.

[sxa]

Given the amount of work we've put into backporting stuff into the 17 codebase I'm personally very much -1 on this unless we are actively choose to avoid maintaining it.

[sophia-guo]

Based on the discussion we will hold it off for now