Skip to:
In working on , I noticed a warning in the test output. I was able to track it down to the Interpreter tests.
Not sure when this was introduced, but the warning is also there in the tests from the last merge against develop-0.7.
We figured out the root cause, which was calling the jest done() function twice in the offending test. That test was also doing two things in parallel rather than chaining them properly. It's fixed in .
I think this may have been fixed somehow, or at least mitigated by the changes I made in . The most recent test run against develop-0.8 still has the problem, but the most recent test run against C2LC-227 doesn't.
In working on , I noticed a warning in the test output. I was able to track it down to the Interpreter tests.
Not sure when this was introduced, but the warning is also there in the tests from the last merge against develop-0.7.