bug#24516:

2016-09-23 Thread Jim Meyering
On Fri, Sep 23, 2016 at 8:16 AM, Jim Meyering wrote: > Anyway, thanks for confirming that this simple fix is probably enough. Adjusted s/3/5/ to be a little more consistent with the above default-to-5s case, and pushed.

bug#24516:

2016-09-23 Thread Jim Meyering
On Fri, Sep 23, 2016 at 6:55 AM, Nelson H. F. Beebe wrote: > Thanks, Jim, for the patch to backref-multibyte-slow; I've applied it > to a new directory grep-2.25.92-f3e9.p1, and have builds in progress > now on the Fedora systems. > > I think that any kind of wallclock-time-dependent test in a pac

bug#24516:

2016-09-23 Thread Nelson H. F. Beebe
Thanks, Jim, for the patch to backref-multibyte-slow; I've applied it to a new directory grep-2.25.92-f3e9.p1, and have builds in progress now on the Fedora systems. I think that any kind of wallclock-time-dependent test in a package test suite is seriously prone to failure. Although some develop

bug#24516:

2016-09-22 Thread Jim Meyering
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