rtfeldman / rtfeldman/node-test-runner
Maximum call stack size exceeeded whenever a fuzz test fails
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 140
- Forks
- 83
- Avg merge
- 8h 25m
- Merged PRs (30d)
- 5
Description
I'm converting an app to Elm 0.19 and I was updating my tests, I was just following any compiling issues I had and at some point I fixed them (at least I think so) and now I'm seeing the following error:
I'm using beta9 on a Win10 computer
I'm not sure how can I get more information to help with this issue, or if you have something else I can do to try it.
I'm not even sure if this is an elm-test issue or elm-explorations\test issue
Thanks
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
The report names no source file, test case, or reproducible input; begin by reproducing the failure with the stated Elm 0.19 beta9 setup and determine whether it belongs to elm-test or elm-explorations/test. Capture a minimal failing fuzz test and the full stack-overflow output; done means the responsible component and a repeatable case are identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100