node-test-runner: elm-test hanging on circleci

(And yes, I’m running it with sysconfcpus -n 2 elm-test.)

I only have two tests at the moment. (Unfortunately, the code is not open source, or else I’d post them.)

The closest issue I found was #53, but I’m not running on Windows, and neither of the tests are fuzz tests. The output is:

$ #!/bin/bash -eo pipefail
sysconfcpus -n 2 elm-test

Success! Compiled 105 modules.
Successfully generated /dev/null
Success! Compiled 11 modules.
Successfully generated /home/circleci/connect/elm-stuff/generated-code/elm-community/elm-test/elmTestOutput.js

elm-test 0.18.8
---------------

Running 2 tests. To reproduce these results, run: elm-test --fuzz 100 --seed 745527669

And then it never completes. Circle CI allows you to ssh into the box to debug a build. When I did that and ran elm-test myself, it worked the first time and hung thereafter.

Any thoughts on how to debug this further?

About this issue

Original URL
State: closed
Created 7 years ago
Comments: 30 (5 by maintainers)

Most upvoted comments

@zwilias Just wanted to let you know, I finally got around to upgrading the docker image I was using, and the new version of node-test-runner works fine. Thanks again!

97jaz on Feb 9, 2018

@simonh1000 This was fixed in elm-test version 0.19.0-beta10 - can you bump the version and see if it still reproduces?

rtfeldman on Oct 21, 2018

Alright, cool; thanks for the responses! So far the issues seem resolved with 0.18.10, so I’ll close this for now.

zwilias on Dec 1, 2017

It’s probably the same as #219. elm-test hangs the vast majority of times for me, even on an empty project for which I just do

$ npm install -g elm-test
$ elm test init
$ elm test

and attempt to run the plain old auto generated Example.elm.

Eight times I ran elm-test and it hung with

$ elm test
Success! Compiled 0 modules.                                        
Successfully generated /dev/null
Success! Compiled 1 module.                                         
Successfully generated /Users/ray/git-repos/lmu-cmsi-386/homework4/elm-stuff/generated-code/elm-community/elm-test/elmTestOutput.js

elm-test 0.18.9
---------------

Running 1 test. To reproduce these results, run: elm-test --fuzz 100 --seed 1772203118

(where the seed changed each time of course.) The ninth time I ran it, I FINALLY saw

TEST RUN INCOMPLETE because there is 1 TODO remaining

Duration: 182 ms
Passed:   0
Failed:   0
Todo:     1
↓ Example
◦ TODO: Implement our first test. See http://package.elm-lang.org/packages/elm-community/elm-test/latest for how to do this!

Definitely looking forward to a fix. In the meantime, my students will not be using elm-test for their Elm assignment. Too bad, because it’s really nice.

I am using a MacBookPro running Sierra and Elm 0.18.0.

rtoal on Nov 6, 2017