Re: non-automated test failure report! :)

[christos%zoulas.com@localhost (Christos Zoulas)]

On Nov 15,  7:29pm, gson%gson.org@localhost (Andreas Gustafsson) wrote:
-- Subject: Re: non-automated test failure report!  :)

| Jukka Ruohonen wrote:
| > On Tue, Nov 15, 2011 at 09:07:45AM -0800, Paul Goyette wrote:
| > > Original report indicated failure on i386:
| > > 
| > > lib/libtre/t_exhaust (388/485): 1 test cases
| > >     regcomp_too_big: UVM: pid 20107 (t_exhaust), uid 0 killed: out of swap
| > > Failed: Test program received signal 9
| > > 
| > > Looks like a test-bed failure?
| > 
| > Can you take a look, Andreas?
| 
| It seems pretty clear to me what is happening: the test program is
| using a lot of memory and is being killed because the machine is
| running out of swap.
| 
| What's not clear to me is why it's failing in this particular way
| instead of e.g. malloc() returning NULL, and what to do about it.
| 
| I'm reluctant to work around this issue by increasing the memory size
| of the test VM from the current 32 MB, because having a limited amount
| of memory has helped find real regressions such as a huge memory leak
| in the /bin/sh yacc parser a while back.  If the test really needs
| that much memory, maybe it should be skipped on low-memory machines.

[1:12pm] 2517>limit memoryuse 32M
[1:12pm] 2518>./t_exhaust regcomp_too_big
t_exhaust: WARNING: Running test cases without atf-run(1) is unsupported
t_exhaust: WARNING: No isolation nor timeout control is being applied; you may 
get unexpected failures; see atf-test-case(4)
passed
[1:12pm] 2519>limit
cputime      unlimited
filesize     unlimited
datasize     262144 kbytes
stacksize    2048 kbytes
coredumpsize 0 kbytes
memoryuse    32768 kbytes
descriptors  128 
memorylocked 165733 kbytes
maxproc      160 
sbsize       unlimited

Either limits don't work... which they seem not to...

25277 christos  34    0   102M   98M RUN        0:07 85.23% 28.12% t_exhaust

Grr.

christos