-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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
AIX: parallel/test-cluster-dgram-1 failures #8380
Comments
May be related to this refactoring: #8261 which landed recently. |
@jasnell. Opened issue to cover and has info printed from last failure. |
Can we either revert the refactor of this specific test case until we can figure out the right way to go ? |
Check for the number of messages received in the `exit` event listener instead of the `disconnect` listener. Fixes: nodejs#8380
#8383 fixes the issue for me in |
Ok starting tests now. |
Tested results are in #8383 Net is that is helps but I still see failure 3/150 versus 0 with the old version. |
Ok, let's revert this one then. I'll get the PR together for that shortly. |
PR to revert that one test if we decide its the right way to go: https://github.com/nodejs/node/pull/8384/files |
Ok updated fix in #8383 resolves the issues. :) |
It looks like the failure here may have been happening before the refactor but just hadn't been caught. Adding the |
Check for the number of messages received in the `exit` event listener instead of the `disconnect` listener. Fixes: nodejs#8380 PR-URL: nodejs#8383 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Michael Dawson <[email protected]> Reviewed By: James M Snell <[email protected]>
Check for the number of messages received in the `exit` event listener instead of the `disconnect` listener. Fixes: #8380 PR-URL: #8383 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Michael Dawson <[email protected]> Reviewed By: James M Snell <[email protected]>
Check for the number of messages received in the `exit` event listener instead of the `disconnect` listener. Fixes: nodejs#8380 Ref: nodejs#8383 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Michael Dawson <[email protected]> Reviewed By: James M Snell <[email protected]>
Check for the number of messages received in the `exit` event listener instead of the `disconnect` listener. Fixes: #8380 Ref: #8383 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Michael Dawson <[email protected]> Reviewed By: James M Snell <[email protected]>
Check for the number of messages received in the `exit` event listener instead of the `disconnect` listener. Fixes: #8380 Ref: #8383 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Michael Dawson <[email protected]> Reviewed By: James M Snell <[email protected]>
This test seems to have started failing recently:
The text was updated successfully, but these errors were encountered: