GNU bug report logs -
#24516
Previous Next
Reported by: Jim Meyering <jim <at> meyering.net>
Date: Fri, 23 Sep 2016 06:02:01 UTC
Severity: normal
Done: Jim Meyering <jim <at> meyering.net>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
Nelson Beebe reported that the backref-multibyte-slow test was
failing. From his log, where I saw max_seconds=1, and the following
timeout 1s ... timed out.
I concluded that something (load on the underlying system, disk/kernel
latency) caused that final grep to take far more wall-clock time than
the former one. This would be expected if some other build/test were
running concurrently.
To work around that, I've written the attached: when the timeout would
be just 1s, increase it to 3. In coreutils tests (because there are so
many, and some were so abusive, and running them in parallel...), we
ended up increasing most timeouts to 10s, but for now, that seems like
it'd be overkill here.
I have so far been able to reproduce that failure, so the above is
just an educated guess. If someone can reproduce the failure and test
the patch, that'd be great.
[grep-unwarranted-failure-of-backref-multibyte-slow.diff (application/octet-stream, attachment)]
This bug report was last modified 8 years and 300 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.