-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
ibmi: test.parallel.test-http-pipeline fails #48047
Labels
ibm i
Issues and PRs related to the IBM i platform.
Comments
I've been in contact with the IBM i sockets team and this looks like a bug. For now its on the backlog with no ETA for a fix. I propose that we skip this test on IBM i until there is a resolution. CC @richardlau @nodejs/platform-ibmi |
MoLow
pushed a commit
to MoLow/node
that referenced
this issue
Jul 6, 2023
PR-URL: nodejs#48048 Refs: nodejs#48047 Reviewed-By: Richard Lau <rlau@redhat.com> Reviewed-By: Michael Dawson <midawson@redhat.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Ceres6
pushed a commit
to Ceres6/node
that referenced
this issue
Aug 14, 2023
PR-URL: nodejs#48048 Refs: nodejs#48047 Reviewed-By: Richard Lau <rlau@redhat.com> Reviewed-By: Michael Dawson <midawson@redhat.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Ceres6
pushed a commit
to Ceres6/node
that referenced
this issue
Aug 14, 2023
PR-URL: nodejs#48048 Refs: nodejs#48047 Reviewed-By: Richard Lau <rlau@redhat.com> Reviewed-By: Michael Dawson <midawson@redhat.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I ran this test BEFORE applying this patch on IBM i, AIX, and Linux. The following were my results:
IBM i
AIX
Linux
The main difference is that on IBM i destroying and closing the client socket doen't happen after the timeout:
Instead the timeout gets called a second time and the server just hangs until the test runner times out.
After Applying this patch the output on IBM i is:
Any Ideas on how we can get this to work properly without having to call closeAllConnections?
Originally posted by @abmusse in #47038 (comment)
The text was updated successfully, but these errors were encountered: