Repository navigation
ibmi: test.parallel.test-http-pipeline fails #48047
Copy link
Copy link
Closed as not planned
Labels
ibm iIssues and PRs related to the IBM i platform.Issues and PRs related to the IBM i platform.staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.Issues and PRs marked stale due to inactivity and scheduled for automatic closure.
Description
Activity
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
Reacted by Richard Lau- addedibm iIssues and PRs related to the IBM i platform.Issues and PRs related to the IBM i platform.
on May 17, 2023 - added a commit that references this issue
on May 22, 2023 - added a commit that references this issue
on May 30, 2023 - added a commit that references this issue
on Jul 6, 2023 - added a commit that references this issue
on Jul 6, 2023 - added 2 commits that reference this issue
on Aug 14, 2023 This issue has been marked as stale due to 210 days of inactivity.
It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.- addedstaleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.Issues and PRs marked stale due to inactivity and scheduled for automatic closure.
on Jun 1, 2026 This issue has been automatically closed after 30 days of inactivity following its stale status (no activity for a total of 240 days).
If this is still relevant, feel free to reopen it or leave a comment with additional details so we can continue the discussion.
Metadata
Metadata
Assignees
Labels
ibm iIssues and PRs related to the IBM i platform.Issues and PRs related to the IBM i platform.staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.Issues and PRs marked stale due to inactivity and scheduled for automatic closure.
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)