Skip to content
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

Closed

Conversation

VoltrexKeyva
Copy link
Member

@VoltrexKeyva VoltrexKeyva commented Nov 6, 2021

• 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.

@nodejs-github-bot nodejs-github-bot added needs-ci PRs that need a full CI run. process Issues and PRs related to the process subsystem. labels Nov 6, 2021
@VoltrexKeyva VoltrexKeyva force-pushed the refactor-process-per-thread branch from 36baf89 to 1ede072 Compare November 6, 2021 17:01
@aduh95
Copy link
Contributor

aduh95 commented Nov 6, 2021

@VoltrexKeyva VoltrexKeyva force-pushed the refactor-process-per-thread branch 2 times, most recently from 849b46f to 31df23c Compare November 7, 2021 12:40
• 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.
@VoltrexKeyva VoltrexKeyva force-pushed the refactor-process-per-thread branch from 31df23c to 1d9a80c Compare November 7, 2021 12:52
@VoltrexKeyva VoltrexKeyva requested a review from aduh95 November 10, 2021 15:14
@aduh95 aduh95 added the request-ci Add this label to start a Jenkins CI on a PR. label Nov 13, 2021
@github-actions github-actions bot removed the request-ci Add this label to start a Jenkins CI on a PR. label Nov 13, 2021
@nodejs-github-bot

This comment has been minimized.

@nodejs-github-bot
Copy link
Collaborator

@VoltrexKeyva
Copy link
Member Author

VoltrexKeyva commented Nov 16, 2021

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?

@richardlau
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-ci PRs that need a full CI run. process Issues and PRs related to the process subsystem.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants