Skip to content

Conversation

@serhiysachkov
Copy link
Contributor

@serhiysachkov serhiysachkov commented Sep 15, 2025

This task addresses the restructuring of the test to handle exception, especially during test setup, in a more immediate "fail fast" manner.


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

Issue

  • JDK-8333526: Restructure java/nio/channels/DatagramChannel/StressNativeSignal.java to a fail fast exception handling policy (Enhancement - P4)

Reviewers

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/27294/head:pull/27294
$ git checkout pull/27294

Update a local copy of the PR:
$ git checkout pull/27294
$ git pull https://git.openjdk.org/jdk.git pull/27294/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 27294

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/27294.diff

Using Webrev

Link to Webrev Comment

…gnal.java to a fail fast exception handling policy
@bridgekeeper
Copy link

bridgekeeper bot commented Sep 15, 2025

👋 Welcome back serhiysachkov! 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
Copy link

openjdk bot commented Sep 15, 2025

@serhiysachkov 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:

8333526: Restructure java/nio/channels/DatagramChannel/StressNativeSignal.java to a fail fast exception handling policy

Reviewed-by: dfuchs

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 185 new commits pushed to 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 (@dfuch, @bplb) 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
Copy link

openjdk bot commented Sep 15, 2025

@serhiysachkov The following label will be automatically applied to this pull request:

  • nio

When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command.

@openjdk openjdk bot added nio nio-dev@openjdk.org rfr Pull request is ready for review labels Sep 15, 2025
@mlbridge
Copy link

mlbridge bot commented Sep 15, 2025

Webrevs

Copy link
Member

@dfuch dfuch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The refactoring looks good generally but why are we explicitely using ports 1122 and 19870?

@serhiysachkov
Copy link
Contributor Author

The refactoring looks good generally but why are we explicitely using ports 1122 and 19870?

not sure about the original purpose of using specific ports, but it changed to 0 as suggested.

Copy link
Member

@bplb bplb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The changes look reasonable to me.

@openjdk openjdk bot added the ready Pull request is ready to be integrated label Sep 24, 2025
@serhiysachkov
Copy link
Contributor Author

/integrate

@openjdk openjdk bot added the sponsor Pull request is ready to be sponsored label Sep 25, 2025
@openjdk
Copy link

openjdk bot commented Sep 25, 2025

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

@msheppar
Copy link

/sponsor

@openjdk
Copy link

openjdk bot commented Sep 25, 2025

Going to push as commit 4f4030a.
Since your change was applied there have been 187 commits pushed to the master branch:

Your commit was automatically rebased without conflicts.

@openjdk openjdk bot added the integrated Pull request has been integrated label Sep 25, 2025
@openjdk openjdk bot closed this Sep 25, 2025
@openjdk openjdk bot removed ready Pull request is ready to be integrated rfr Pull request is ready for review sponsor Pull request is ready to be sponsored labels Sep 25, 2025
@openjdk
Copy link

openjdk bot commented Sep 25, 2025

@msheppar @serhiysachkov Pushed as commit 4f4030a.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

integrated Pull request has been integrated nio nio-dev@openjdk.org

Development

Successfully merging this pull request may close these issues.

4 participants