| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
@bzoz build started: https://ci.nodejs.org/blue/organizations/jenkins/node-test-pull-request-lite-pipeline/detail/node-test-pull-request-lite-pipeline/859/pipeline |
Sorry, something went wrong.
| // for others it will be silently reduced to PRIORITY_HIGH | ||
| if (expected < PRIORITY_HIGH) | ||
| assert.strictEqual(priority, PRIORITY_HIGHEST); | ||
| assert.ok(priority === PRIORITY_HIGHEST || priority === PRIORITY_HIGH); |
There was a problem hiding this comment.
Instead of doing this for all cases, can we make an explicit check for Windows and possibly for elevated user status before making this kind of assertion?
Sorry, something went wrong.
There was a problem hiding this comment.
This is for Windows only (see line 114)
Sorry, something went wrong.
There was a problem hiding this comment.
I see, can we check for elevated status then? Perhaps using this method or something similar (without 3rd party utilities)?
Sorry, something went wrong.
Sorry, something went wrong.
Refs: nodejs/node#22817 PR-URL: #1985 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Santiago Gimeno <santiago.gimeno@gmail.com>
Refs: nodejs/node#22817 Refs: libuv/help#64 PR-URL: libuv#2002 Reviewed-By: Bartosz Sosnowski <bartosz@janeasystems.com>
| Back | FazBrowse Home | New Git URL |
Also fixes the test: #22799
See https://support.microsoft.com/en-us/help/110853/prb-can-t-increase-process-priority
Checklist