Author gphemsley
Recipients gphemsley, zach.ware
Date 2019-05-05.13:58:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
It seems the primary cause of the problem is simply that testing crossed the boundary of maximum execution time allotted by Travis CI.

I'm experimenting now with ways to speed up testing without losing granularity. However, given how long code coverage has been missing, it might be worthwhile to move forward on a stopgap solution that at least gets code coverage being tracked again, if not comprehensively.
Date User Action Args
2019-05-05 13:58:21gphemsleysetrecipients: + gphemsley, zach.ware
2019-05-05 13:58:21gphemsleysetmessageid: <>
2019-05-05 13:58:21gphemsleylinkissue36684 messages
2019-05-05 13:58:21gphemsleycreate