You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm sporadically getting the dreaded RangeError: Maximum call stack size exceeded with Expect.equalLists. Because the occurrence of the error seems to be very sensitive to factors that I don't fully understand, I've put the relevant files for reproduction (all three of them) into a repository at https://github.com/Steve-OH/elm-test-crash.
What's happening: The test fuzzer creates lists of integers that are 99% 1s and 1% 2s. (The ratio is not important; it's just there to make the failure conditions more apparent.) The only "test" (such as it is) in the suite compares the original list to a list that has all of the 2s stripped out, using Expect.equalLists. Thus, the test should pass if the original list consists only of 1s, and fail if the original list contains any 2s. The test does pass in the first case, but rather than failing in the second, it crashes with RangeError: Maximum call stack size exceeded.
The crash seems to be dependent on factors that you wouldn't expect to be relevant, such as whether the Elm code is in a package (crashes reliably) or in an application (I could not get it to crash that way).
Reported info:
OS: Windows 10.0.18362.0 (version 1903 build 18362.657)
elm --version: 0.19.1
elm-test --version: 0.19.1-revision2
node --version: v12.13.1
The text was updated successfully, but these errors were encountered:
I've just run the tests of your elm-test-crash repo and I can't get a crash, so maybe this bug was solved? I run it with elm-explorations/test at version 1.2.2
Could you confirm if it's working for you too? I'd suggest removing elm-stuff/ to make sure elm-test uses the latest version of elm-explorations/test.
In particular, it seems I can consistently trigger the call stack crash with version 1.0.0 of elm-explorations/test but not crash anymore starting with version 1.1.0. So if that was the issue, I'd suggest using the following lower bound in your tests dependencies:
"test-dependencies": {
"elm-explorations/test": "1.2.2 <= v < 2.0.0"
}
I'm sporadically getting the dreaded RangeError: Maximum call stack size exceeded with
Expect.equalLists
. Because the occurrence of the error seems to be very sensitive to factors that I don't fully understand, I've put the relevant files for reproduction (all three of them) into a repository at https://github.com/Steve-OH/elm-test-crash.What's happening: The test fuzzer creates lists of integers that are 99%
1
s and 1%2
s. (The ratio is not important; it's just there to make the failure conditions more apparent.) The only "test" (such as it is) in the suite compares the original list to a list that has all of the2
s stripped out, usingExpect.equalLists
. Thus, the test should pass if the original list consists only of1
s, and fail if the original list contains any2
s. The test does pass in the first case, but rather than failing in the second, it crashes with RangeError: Maximum call stack size exceeded.The crash seems to be dependent on factors that you wouldn't expect to be relevant, such as whether the Elm code is in a package (crashes reliably) or in an application (I could not get it to crash that way).
Reported info:
OS: Windows 10.0.18362.0 (version 1903 build 18362.657)
elm --version: 0.19.1
elm-test --version: 0.19.1-revision2
node --version: v12.13.1
The text was updated successfully, but these errors were encountered: