Pierre Labastie wrote:
>> It still looks like a race condition (what is the order of
>> entries in /proc/diskstats) or just a logic error in the test to me.
Looks that way to me too.
> Usually, I get the same as you (except loop is always at the end). It
> happened only twice during the last week, that the sr0 line was before
> the sda ones, while I think I have rebooted that machine at least 10 times.
> sed -i -r 's|(a-z\\])\+|\1\\{3\\}|' testsuite/vmstat.test/vmstat.exp
> should be OK, even if it happens that a loop? is mounted and has more
> than ten reads.
Since we are looking for *partitions*, [s|h]d[a-z]\d should identify them.
> Now, I have a new test failure in pmap:
> FAIL: pmap extra extended output (footer)
> :-(
> Needs more testing, but the behavior seems to be different when running
> in jhalfs and by hand...
I did fix a problem in pmap due to expect's spawn command doing things
when the parent process is not connected to a tty (internal stty
command). It seems to want to map newlines to \r\n. It may do other
things too.
set mypid [pid]
set pmap_procname "${mypid}:\\s+\\S+\[^\\r\]+\\s+"
set pmap_generic_header "${pmap_procname}\\s+\(?:\[A-Z\]\[a-z\]+ +\)+"
set test "pmap extended output"
spawn $pmap -X $mypid
expect_table $test $test $pmap_generic_header ".+" "\[= \]+"
expect_table is in testsuite/config/unix.exp
It seems to be matching the header, and the ".+", but not the "\[= \]+"
When I run this in chroot, it seems to be OK, but outside of chroot, I
get 'pmap: Unknown format in smaps file!'
A successful run gets a lot of data with a line at the bottom:
===== === === ========== ========= ==== ====== which would match '= '.
-- Bruce
-- Bruce
-- Bruce
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
