HI,

I think it would be better not to test out of memory unless especially
asked for.

Too many systems will work hard to keep going at the expense of
basically seeming to freeze from the user's POV.

We can keep the test, but, only run when someone asks specifically.

cheers

bruce

On 2022-05-19T11:26:54.000+02:00, Marcel Taeumel
<marcel.taeumel at hpi.de> wrote:

> Hmm... I think we should ignore that #testOutOfMemorySignal until
> we can define some kind of upper limit in the VM. Operating Systems
> these days start paging and whatnot. You will never be out-of-memory
> until your system crashes. xD
> 
> Best,
> Marcel
> 
>>  Am 19.05.2022 06:54:10 schrieb Lauren Pullen <drurowin at gmail.com>:
>>  
>>  testOneMegAllocation: pass 
>>  testOneGigAllocation: fail 
>>  testOutOfMemorySignal: fail 
>>  
>>  When run from Print-it, testOneGigAllocation still fails and 
>>  testOutOfMemorySignal passes... both with a near zero duration
>>  reported. 
>>  
>>  When run from Debug-it, both tests pass with duration equal to
>>  wall time. 
>>  
>>  Squeak 6.0 beta 21760 
>>  202205110711 VM 
>>  Mac OSX x64 (non-fat) binary 
>>  Intel CPU (no Rosetta... or whatever they call it now)
> 
> -------------------------

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20220519/9a83d38a/attachment.html>