On Sat, Jul 19, 2014 at 06:55:02PM +, Miod Vallat wrote:
> What flags were you using? As its name implies, this test causes a lot
> of memory to be allocated, so malloc flags such as F and G will take a
> toll...
I was using G since I had S enabled.
> > I think that was the cause of the kqueu
> > That's odd. This test only takes a few seconds on an amd64 system. Do
> > you have any local changes to libc, or any particular /etc/malloc.conf
> > settings, which could explain the slowdown?
>
> Ahh you caught me. Yes, I had /etc/malloc.conf settings. I'll try it
> again without those sett
> Date: Sat, 19 Jul 2014 18:16:56 +
> From: Miod Vallat
>
> > REGRESS_SKIP_SLOW didn't work as intended. Default is no yet it checks
> > for !empty.
>
> Good catch! Applied, thanks.
>
> > Added t-exhaust as slow because it takes > 90 minutes on my recent CPU.
>
> That's odd. This test onl
On Sat, Jul 19, 2014 at 06:16:56PM +, Miod Vallat wrote:
> > Added t-exhaust as slow because it takes > 90 minutes on my recent CPU.
>
> That's odd. This test only takes a few seconds on an amd64 system. Do
> you have any local changes to libc, or any particular /etc/malloc.conf
> settings, wh
> REGRESS_SKIP_SLOW didn't work as intended. Default is no yet it checks
> for !empty.
Good catch! Applied, thanks.
> Added t-exhaust as slow because it takes > 90 minutes on my recent CPU.
That's odd. This test only takes a few seconds on an amd64 system. Do
you have any local changes to libc,
REGRESS_SKIP_SLOW didn't work as intended. Default is no yet it checks
for !empty.
Added t-exhaust as slow because it takes > 90 minutes on my recent CPU.
Index: regress/lib/libc/regex/Makefile
===
RCS file: /cvs/src/regress/lib/li
