-
Notifications
You must be signed in to change notification settings - Fork 30.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
process: refactor process per thread #40746
process: refactor process per thread #40746
Conversation
36baf89
to
1ede072
Compare
849b46f
to
31df23c
Compare
• Validate the `prevValue` parameter in the `cpuUsage()` function at the correct place. • Use validation methods for consistency. • Use the logical OR assignment operator (`||=`) where appropriate. • Use `StringPrototypeReplaceAll()` where appropriate.
31df23c
to
1d9a80c
Compare
This comment has been minimized.
This comment has been minimized.
According to the console output of the Jenkins CI checks, none of the actual tests seem to be failing, but the Jenkins CI checks seem to fail either way due to a Java error raised by disconnecting from the specified backing channel. Anything we can do about that? |
Given every platform and also the GitHub Action tests workflows are failing and we're not seeing the same across-the-board failures on other PR's there's likely to be some non-obvious issue with this PR. |
• Validate the
prevValue
parameter in thecpuUsage()
function at the correct place.• Use validation methods for consistency.
• Use the logical OR assignment operator (
||=
) where appropriate.• Use
StringPrototypeReplaceAll()
where appropriate.