updated [Re: new snapshot, and a huge set of coreutils test results

[Jim Meyering]

Bruno Haible <[EMAIL PROTECTED]> wrote:
> Jim Meyering wrote:
>> I'm publishing this mainly so that people who care about the affected
>> platforms can investigate further.
>
> As a first step to that: the list of failing tests:
>
> $ grep '^FAIL:' * | sort -k2
> go.2008.04.14.07.01.55.log:FAIL: 2g.log
> go.2008.04.14.07.01.55.log:FAIL: 8gb.log
...
> That will take a time...

Thanks for looking.
It's better with the newer snapshot:

  http://meyering.net/cu/build-logs/coreutils-build-log-6.10.194-0d03b.tar.lzma

Here's a different way to summarize, which shows we're in very good shape,
on all but a few fringe systems.  For example, I am confident that the
tty-eof failures are ignorable.

$ grep -h FAIL: *|sort |uniq -c|sort -nr
     16 FAIL: tty-eof.log (exit: 1)
     16 FAIL: tty-eof.log
      5 FAIL: files0-from.log (exit: 1)
      5 FAIL: files0-from.log
      4 FAIL: sort-compress.log (exit: 1)
      4 FAIL: sort-compress.log
      3 FAIL: test-ftello.sh
      3 FAIL: test-fseeko.sh
      3 FAIL: part-symlink.log (exit: 1)
      3 FAIL: part-symlink.log
      3 FAIL: basic.log (exit: 1)
      3 FAIL: basic.log
      2 FAIL: v-slash.log
      2 FAIL: unread3.log
      2 FAIL: unread2.log
      2 FAIL: thru-dangling.log (exit: 1)
      2 FAIL: thru-dangling.log
      2 FAIL: sunos-1.log
      2 FAIL: rm5.log
      2 FAIL: rm4.log
      2 FAIL: rm3.log
      2 FAIL: rm2.log
      2 FAIL: rm1.log
      2 FAIL: readdir-bug.log
      2 FAIL: r-4.log
      2 FAIL: r-3.log
      2 FAIL: r-2.log
      2 FAIL: r-1.log
      2 FAIL: parent-perm.log (exit: 1)
      2 FAIL: parent-perm.log
      2 FAIL: one-file-system.log
      2 FAIL: no-give-up.log
      2 FAIL: isatty.log
      2 FAIL: ir-1.log
      2 FAIL: interactive-once.log
      2 FAIL: interactive-always.log
      2 FAIL: inaccessible.log
      2 FAIL: ignorable.log
      2 FAIL: i-no-r.log
      2 FAIL: i-never.log
      2 FAIL: i-1.log
      2 FAIL: fail-eacces.log
      2 FAIL: fail-2eperm.log
      2 FAIL: f-1.log
      2 FAIL: empty-inacc.log
      2 FAIL: dot-rel.log
      2 FAIL: dir-nonrecur.log
      2 FAIL: dir-no-w.log
      2 FAIL: deep-2.log
      2 FAIL: deep-1.log
      2 FAIL: dangling-symlink.log
      2 FAIL: cycle.log
      1 FAIL: tee.log (exit: 1)
      1 FAIL: tee.log
      1 FAIL: tee
      1 FAIL: seq.log (exit: 1)
      1 FAIL: seq.log
      1 FAIL: help-version.log (exit: 1)
      1 FAIL: help-version.log
      1 + echo FAIL: tee

FYI, some of those are inevitable, given the
constraints of the build systems, so I do not expect the
total error count ever to reach 0.