TypeError thrown from non-native Elm code (in elm-test)

[rhofour]

Issue originally detailed at: elm-community/elm-test#227

Summary: I'm able to trigger a type error

This test failed because it threw an exception: "TypeError: shrink1 is not a function"

in my tests in both the Node and HTML runners. The offending commit is: rhofour/elm-comidi@0d62c8f . Before this commit the tests pass and afterwards they fail with the above error.

This is on Elm 0.18. The exact-dependencies.json for my tests is:

"elm-community/lazy-list": "1.0.0",
"elm-community/elm-test": "4.2.0",
"elm-community/shrink": "2.0.0",
"elm-lang/virtual-dom": "2.0.4",
"eeue56/elm-lazy": "1.0.0",
"mgold/elm-random-pcg": "5.0.2",
"elm-lang/lazy": "2.0.0",
"eeue56/elm-lazy-list": "1.0.0",
"elm-lang/html": "2.0.0",
"eeue56/elm-shrink": "1.0.0",
"Bogdanp/elm-combine": "3.1.1",
"elm-lang/core": "5.1.1"

I'm on Fedora 27 with Google Chrome 63.0.3239.108 (64-bit).

[process-bot]

Thanks for the issue! Make sure it satisfies this checklist. My human colleagues will appreciate it!

Here is what to expect next, and if anyone wants to comment, keep these things in mind.

[process-bot]

Thanks for the issue! Make sure it satisfies this checklist. My human colleagues will appreciate it!

Here is what to expect next, and if anyone wants to comment, keep these things in mind.

[evancz]

I need issues with an http://sscce.org to do anything. I cannot be the one sorting through 12 dependencies and a whole application repo to figure out if my code is responsible here.

@rtfeldman and others in that thread, when you get issues like the original elm-test one, can you either (1) tell people what is expected before passing them to me or (2) do the work that needs to be done for it to be a viable issue.

Please someone open this again once it has been pinned down to an SSCCE that demonstrates the issue is actually in elm-lang/core or in elm-lang/elm-compiler.

[evancz]

I need issues with an http://sscce.org to do anything. I cannot be the one sorting through 12 dependencies and a whole application repo to figure out if my code is responsible here.

@rtfeldman and others in that thread, when you get issues like the original elm-test one, can you either (1) tell people what is expected before passing them to me or (2) do the work that needs to be done for it to be a viable issue.

Please someone open this again once it has been pinned down to an SSCCE that demonstrates the issue is actually in elm-lang/core or in elm-lang/elm-compiler.