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
{{ message }}
This repository was archived by the owner on Apr 12, 2024. It is now read-only.
It actually looks like something else is making this happen. The test is returning, which brings the prompt back, but then something is being written to stdout after the fact—usually something like this would be caused by a background process of some sort.
Not positive, but I think learn-test-sender (which is what's throwing the second error that makes it look all broken) might be related to the experiment we've been running with the learn-test gem.
We should look into this, but it seems very unlikely that this is related to this IDE release.
The text was updated successfully, but these errors were encountered:
I ran into this when writing #43 . The issue is that the output of the mocha run is returning nil in the result method of the Mocha strategy. A clue on fixing this would be to take a look at how or what is cleaning up that results file.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
@kvignali commented on Wed May 17 2017
https://www.screencast.com/t/JVDyLHDMc
@drewprice commented on Wed May 17 2017
It actually looks like something else is making this happen. The test is returning, which brings the prompt back, but then something is being written to stdout after the fact—usually something like this would be caused by a background process of some sort.
Not positive, but I think
learn-test-sender
(which is what's throwing the second error that makes it look all broken) might be related to the experiment we've been running with thelearn-test
gem.We should look into this, but it seems very unlikely that this is related to this IDE release.
The text was updated successfully, but these errors were encountered: