Facing one test issue on PPC64LE architecture.
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 261
- Forks
- 31
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 4
Description
I'm facing one test failure on PPC64LE architecture
🌈 SUMMARY RESULTS 🌈
SKIP test/commonjs-fallback.test.js 3 skip of 3 4.042ms
~ yarn module resolution
~ yarn module resolution for directories with special characters
~ yarn module resolution for typescript commonjs modules
SKIP test/never-drain.test.js 1 skip of 1 3.61ms
~ emit warning when the worker gracefully exit without the stream ended
FAIL test/pkg/pkg.test.js 1 failed of 1 18s
✖ stdout maxBuffer length exceeded
Suites: 1 failed, 16 passed, 17 of 17 completed
Asserts: 1 failed, 155 passed, 4 skip, of 160
Time: 43s
OS:
NAME="Red Hat Enterprise Linux"
VERSION="9.3 (Plow)"
ID="rhel"
ID_LIKE="fedora"
VERSION_ID="9.3"
PLATFORM_ID="platform:el9"
PRETTY_NAME="Red Hat Enterprise Linux 9.3 (Plow)"
ANSI_COLOR="0;31"
LOGO="fedora-logo-icon"
CPE_NAME="cpe:/o:redhat:enterprise_linux:9::baseos"
HOME_URL="https://www.redhat.com/"
DOCUMENTATION_URL="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Red Hat Enterprise Linux 9"
REDHAT_BUGZILLA_PRODUCT_VERSION=9.3
REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux"
REDHAT_SUPPORT_PRODUCT_VERSION="9.3"
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing test/pkg/pkg.test.js on PPC64LE with the reported RHEL 9.3 environment, then inspect the stdout maxBuffer length exceeded failure. Done means the package test passes on PPC64LE while the existing test suite remains passing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100