[#1653] add CI reference job with IBM Semeru Runtimes

[bmarwell]

fixes #1653

now that actions/setup-java#289 was merged

[cherylking]

@bmarwell We have intermittent failures in a couple of tests (usually dev-it and generate-features-it). Does this reference build have to pass all the tests in order for the other builds to run? If so, we would probably want to exclude those two tests at a minimum to ensure the other builds run.

[bmarwell]

@bmarwell We have intermittent failures in a couple of tests (usually dev-it and generate-features-it). Does this reference build have to pass all the tests in order for the other builds to run? If so, we would probably want to exclude those two tests at a minimum to ensure the other builds run.

Yes, that's why I opened #1633 a while ago. That really should be fixed first. Sadly, I cannot run the tests locally due to the slightly special setup.

Also, it seems that 'semeru' is still not recognized. 😞

[bmarwell]

@cherylking the first tests fails sometimes (as expected) after 63 minutes.
Maybe we could not use all the tests all the time to save some time. WDYT?

What already works:

• If there's a more general problem (i.e. compilation error, expected test failure) it will not occupy as much action runners as before

[cherylking]

the first tests fails sometimes (as expected) after 63 minutes.
Maybe we could not use all the tests all the time to save some time. WDYT?

@bmarwell That was my concern for the reference build/test...the intermittent test failures. So I think it would be wise to exclude the dev-it and generate-features-it tests in just the reference build. That way we are more likely to get to the rest of the builds.