[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#19005: [platform-testers] new snapshot available: grep-2.20.83-06900
From: |
Assaf Gordon |
Subject: |
bug#19005: [platform-testers] new snapshot available: grep-2.20.83-06900 |
Date: |
Sun, 09 Nov 2014 17:30:59 -0500 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 |
Hello,
On 11/09/2014 04:00 PM, Jim Meyering wrote:
Testing the first snapshot exposed several problems,
and most have been addressed. The sole remaining problem
is the failure of an "expensive" (not run by default: big-match)
that makes most systems run out of memory. I haven't looked at it yet.
<...>
Please let us know if you find any problems.
Two quick tests:
-1-
On an old ubuntu 10 64-bit machine with PCRE, test "pcre-invalid-utf8-input"
fails.
Log attached.
It is possible due to the test using "en_US.UTF-8" but the available locales
are:
$ locale -a | grep en_US
en_US
en_US.utf8
However, the 'get-mb-cur-max' does seem to accept "UTF-8":
$ ./tests/get-mb-cur-max en_US
1
$ ./tests/get-mb-cur-max en_US.utf8
6
$ ./tests/get-mb-cur-max en_US.UTF-8
6
$ ./tests/get-mb-cur-max en_US.FOO-8
(EMPTY)
It is possible this old machine is mis-configured, and if so - please ignore
this failure.
Using "libpcre3" version "7.8-3build1" (from ubuntu 10 package).
-2-
On the same machine, which has 128 GB ram total, and 106 GB ram free:
$ free -g
total used free shared buffers cached
Mem: 125 38 87 0 6 13
-/+ buffers/cache: 18 106
Swap: 9 3 6
The "big-match" test is still skipped with "not enough main memory to run the
test" - which sounds a bit weird.
Log attached.
During the execution of the tests, the "grep" process consumed up to 4.0GB of ram (in the
"RES" column of "top").
I'll be able to run the other test (on more OSes) a bit later.
Regards,
- Assaf
grep.tests-suite.big-match.log
Description: Text Data
grep.tests-suite.pcre_utf.log
Description: Text Data