8065: Remove socket read illegal value

[xpbob]

Socket read failure returns -1
Negative statistics affect accuracy

After modification

---

Progress

• Commit message must refer to an issue
• Change must be properly reviewed (1 review required, with at least 1 Committer)

Issue

• JMC-8065: Remove socket read illegal value

Reviewers

• Marcus Hirt (@thegreystone - Reviewer) ⚠️ Review applies to 7cbf73cf

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 478

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jmc/pull/478.diff

Webrev

Link to Webrev Comment

[bridgekeeper]

👋 Welcome back xpbob! 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.

[mlbridge]

Webrevs

• 03: Full - Incremental (8cc9d1c3)
• 02: Full - Incremental (7cbf73cf)
• 01: Full - Incremental (989ade49)
• 00: Full (aa4851cc)

[openjdk]

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

8065: Remove socket read illegal value

Reviewed-by: hirt

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 3 new commits pushed to the master branch:

• 06bbd5f: 8057: Upgrade to 2023-03
• 7d88877: 8067: JMC Automated Analysis Page shows blank
• 1fb69d4: 8046: build.bat --packageAgent doesn't detect failed builds

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 (@thegreystone) 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).

[thegreystone]

Nit: I think I'd prefer this as this(accessor).

[thegreystone]

Thanks for the contribution! 👍

[xpbob]

@thegreystone Thanks for the review

[xpbob]

/integrate

[openjdk]

@xpbob
Your change (at version 7cbf73c) is now ready to be sponsored by a Committer.

[xpbob]

The code has been updated

[thegreystone]

/sponsor

[openjdk]

@thegreystone The PR has been updated since the change author (@xpbob) issued the integrate command - the author must perform this command again.

[thegreystone]

Hi @xpbob! Please /integrate again.

[xpbob]

/integrate

[openjdk]

@xpbob
Your change (at version 8cc9d1c) is now ready to be sponsored by a Committer.

[xpbob]

Hi @thegreystone
Thanks for the review
I add tag /integrate

[RealCLanger]

/sponsor

[openjdk]

Going to push as commit 58c9ede.
Since your change was applied there have been 3 commits pushed to the master branch:

• 06bbd5f: 8057: Upgrade to 2023-03
• 7d88877: 8067: JMC Automated Analysis Page shows blank
• 1fb69d4: 8046: build.bat --packageAgent doesn't detect failed builds

Your commit was automatically rebased without conflicts.

[openjdk]

@RealCLanger @xpbob Pushed as commit 58c9ede.

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