| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
There was a problem hiding this comment.
Please add a test for this.
Sorry, something went wrong.
|
@jasnell @BridgeAR with this fix we can make the options work when args is undefined or null, but it still fails when args is an empty object {}. Should we also incorporate this by throwing if an object is passed as the second argument? - fork('test.js', {} , {env: {foo: 'bar'}}); |
Sorry, something went wrong.
|
@jasnell A CITGM run is required. |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM
Sorry, something went wrong.
Sorry, something went wrong.
|
Related failure: |
Sorry, something went wrong.
|
@lundibundi Need some help fixing the failure that you've mentioned. Cannot reproduce in my local. |
Sorry, something went wrong.
|
@shobhitchittora fork is an async operation that does not keep the event loop alive. Therefore the test exits before the spawned file is done and in that case the test will not receive the message and the test fails. |
Sorry, something went wrong.
|
@BridgeAR I've removed exit(0) from the forked process fixture. I haven't found any existing fixture to use here. Also I've no clue about how to make the test wait for the fork's response. |
Sorry, something went wrong.
|
@shobhitchittora I think using .on('exit', common.mustCall()) might help. |
Sorry, something went wrong.
|
@lundibundi Are you sure? I don't see a point of using onexit. Can you please explain? Also any other ideas? This seems weird to me. |
Sorry, something went wrong.
|
Theoretically, it should make current node process wait until fork finishes as we are listening on its close event. Also, this seems to be the way it's done with other fork tests. Anyway I think it's worth a try, this is a simple change anyway. |
Sorry, something went wrong.
Sorry, something went wrong.
|
Any idea why the status code returned by child is 127 or 1 in the CI? This seems that there was some error while executing the forked process. Also I tried running the child js file in local and got the below error - TypeError: process.send is not a function
at Object.<anonymous> (/Users/schittora/Desktop/node/test/fixtures/child-process-spawn-node.js:10:9)
at Module._compile (module.js:635:30)
at Object.Module._extensions..js (module.js:646:10)
at Module.load (module.js:554:32)
at tryModuleLoad (module.js:497:12)
at Function.Module._load (module.js:489:3)
at Function.Module.runMain (module.js:676:10)
at startup (bootstrap_node.js:187:16)
at bootstrap_node.js:608:3 |
Sorry, something went wrong.
|
Sorry, forgot about this one. |
Sorry, something went wrong.
|
@lundibundi Everything looks green 💚 . Thanks!! 👍 |
Sorry, something went wrong.
PR-URL: nodejs#22416 Fixes: nodejs#20749 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Denys Otrishko <shishugi@gmail.com> Reviewed-By: Matheus Marchini <mat@mmarchini.me>
| Back | FazBrowse Home | New Git URL |
Closes: #20749
Checklist
NOTE: Run test using - python ./tools/test.py parallel/test-child-process-fork-options.js
Affected subsystem(s)
child_process / fork