Skip to content

test: fix flaky test-inspector-port-zero-cluster #13711

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.

Sign up for GitHub

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

Closed
Trott wants to merge 3 commits into from
Closed

test: fix flaky test-inspector-port-zero-cluster #13711

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
753c6c5
test: fix flaky test-inspector-port-zero-cluster
Trott Jun 16, 2017
df3fec0
squash: remove unused arguments
Trott Jun 16, 2017
e61bb61
squash: remove flaky status from inspector.status
Trott Jun 16, 2017
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
squash: remove unused arguments
  • Loading branch information
@Trott
Trott committed Jun 16, 2017
commit df3fec0414762d2e6080855d5b1eda4e278f5b55
2 changes: 1 addition & 1 deletion test/inspector/test-inspector-port-zero-cluster.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ if (cluster.isMaster) {
ports.push(message.debugPort);
worker.kill();
});
worker.on('exit', (code, signal) => {
worker.on('exit', () => {
// If the worker exited via `worker.kill()` above, exitedAfterDisconnect
// will be true. If the worker exited because the debug port was already
// in use, exitedAfterDisconnect will be false. That can be expected in
Expand Down