17 Nov
2016
17 Nov
'16
10:21 a.m.
On 10 November 2016 at 14:07, James Oakley james.oakley@multapplied.net wrote:
These specific tests have been running just fine for months under 2016.9, and the release before that. This problem began immediately after I upgraded to 2016.11 this morning.
After some digging, I found that there was an external factor causing the tests to hang.
Sorry for the noise.
-- James Oakley james.oakley@multapplied.net