-
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
test-fs-read-type fails on IBM i #36925
Comments
cc @nodejs/platform-ibmi |
They were invited to join the team according to nodejs/admin#490 (comment) |
I'm sorry this happened. Perhaps adding a check for node/test/parallel/test-fs-read-type.js Line 238 in 1772ae7
- if (err.code !== 'EFBIG') throw err;
+ if (err.code !== 'EFBIG' && err.code !== 'UNKNOWN') throw err; |
I'd rather see if the
|
@dmabupt should definitely be added to the @nodejs/platform-ibmi team. @dmabupt, please check to see if you have a pending invite still, or maybe you need to be re-invited. |
Sorry again, I misclicked. |
Invited @dmabupt to the team. |
PR-URL: #36986 Refs: #34410 Refs: #36925 Refs: #36929 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Michael Dawson <[email protected]> Reviewed-By: Rich Trott <[email protected]>
PR-URL: #36986 Refs: #34410 Refs: #36925 Refs: #36929 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Michael Dawson <[email protected]> Reviewed-By: Rich Trott <[email protected]>
PR-URL: #36986 Refs: #34410 Refs: #36925 Refs: #36929 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Michael Dawson <[email protected]> Reviewed-By: Rich Trott <[email protected]>
@dmabupt have you had a chance to look at this? |
PR-URL: #36986 Refs: #34410 Refs: #36925 Refs: #36929 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Michael Dawson <[email protected]> Reviewed-By: Rich Trott <[email protected]>
I think it fails every time now that 72b678a was merged a day or two ago. Since IBM i only runs in the nightly CI job, this issue wasn't apparent during pull request reviews.
Wha't's the right thing to do here? Leave it for now and someone on @nodejs/platform-ibmii will take a look? Add this to the list of skipped tests on IBM i in
parallel.status
? Both? Something else?https://ci.nodejs.org/job/node-test-commit-ibmi/223
@nodejs/platform-ibmi @RaisinTen
The text was updated successfully, but these errors were encountered: