8334078: RISC-V: TestIntVect.java fails after JDK-8332153 when running without RVV

[zifeihan]

Hi, at JDK-8334078, modified the matching logic for the linux-riscv64 rvv test, here i would like to backport this to jdk21u-dev, to simplify the subsequent functionality and testing of the backport to jdk21u-dev. This is a risc-v specific change, risk is low.

Testing

• Run tier1 tests on SOPHON SG2042 (fastdebug)

---

Progress

• Change must be properly reviewed (1 review required, with at least 1 Reviewer)
• Change must not contain extraneous whitespace
• Commit message must refer to an issue
• JDK-8334078 needs maintainer approval

Issue

• JDK-8334078: RISC-V: TestIntVect.java fails after JDK-8332153 when running without RVV (Bug - P4 - Approved)

Reviewers

• Fei Yang (@RealFYang - Reviewer)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk21u-dev.git pull/937/head:pull/937
$ git checkout pull/937

Update a local copy of the PR:
$ git checkout pull/937
$ git pull https://git.openjdk.org/jdk21u-dev.git pull/937/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 937

View PR using the GUI difftool:
$ git pr show -t 937

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk21u-dev/pull/937.diff

Webrev

Link to Webrev Comment

[bridgekeeper]

👋 Welcome back gcao! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

[openjdk]

@zifeihan This change now passes all automated pre-integration checks.

ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details.

After integration, the commit message for the final commit will be:

8334078: RISC-V: TestIntVect.java fails after JDK-8332153 when running without RVV

Reviewed-by: fyang

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been 2 new commits pushed to the master branch:

• cd5ac19: 8299813: java/nio/channels/DatagramChannel/Disconnect.java fails with jtreg test timeout due to lost datagram
• 4c86bf5: 8309067: gtest/AsyncLogGtest.java fails again in stderrOutput_vm

Please see this link for an up-to-date comparison between the source branch of this pull request and the master branch.
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.

As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@RealFYang) but any other Committer may sponsor as well.

➡️ To flag this PR as ready for integration with the above commit message, type /integrate in a new comment. (Afterwards, your sponsor types /sponsor in a new comment to perform the integration).

[openjdk]

This backport pull request has now been updated with issue from the original commit.

[mlbridge]

Webrevs

• 00: Full (74479998)

[RealFYang]

LGTM. Thanks.

[zifeihan]

Thanks for the review.
/integrate

[openjdk]

@zifeihan
Your change (at version 7447999) is now ready to be sponsored by a Committer.

[RealFYang]

/sponsor

[openjdk]

Going to push as commit 846962d.
Since your change was applied there have been 2 commits pushed to the master branch:

• cd5ac19: 8299813: java/nio/channels/DatagramChannel/Disconnect.java fails with jtreg test timeout due to lost datagram
• 4c86bf5: 8309067: gtest/AsyncLogGtest.java fails again in stderrOutput_vm

Your commit was automatically rebased without conflicts.

[openjdk]

@RealFYang @zifeihan Pushed as commit 846962d.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.