Re: [Pharo-users] valueUnpreemptively breaks coverage with ZnClient

2017-12-02 Thread Richard Sargent
Necessary? I can't see that. It seems patently wrong once you consider the cases that cannot be supported. On Dec 2, 2017 12:02, "Sven Van Caekenberghe" wrote: > > > > On 2 Dec 2017, at 17:21, Peter Uhnák wrote: > > > > After much digging as to why my tests are timing out even though running >

Re: [Pharo-users] valueUnpreemptively breaks coverage with ZnClient

2017-12-02 Thread Sven Van Caekenberghe
> On 2 Dec 2017, at 17:21, Peter Uhnák wrote: > > After much digging as to why my tests are timing out even though running > directly was always fine... I found out that TestRunner's coverageRun is > using #valueUnpreemptively to run all tests. > > The problem is that one of the tests is ret

[Pharo-users] valueUnpreemptively breaks coverage with ZnClient

2017-12-02 Thread Peter Uhnák
After much digging as to why my tests are timing out even though running directly was always fine... I found out that TestRunner's coverageRun is using #valueUnpreemptively to run all tests. The problem is that one of the tests is retrieving something over network, and that apparently doesn't go w