Re: conflicts-130 fails - more info

[Pavel Roskin]

Hello!

> conflicts-130 fails on the today's CVS on RedHat 7.0 with ReiserFS (the
> later may be suggestive, since it doesn't sort the files automatically).
> However, the CVS from CVS passed "make check" few days ago on the same
> machine.

I have looked a bit deeper, this time with the CVS version as of "Mon Apr
2 15:45:08 UTC 2001". conflicts-130 fails if /tmp is on ramfs, but not on
ReiserFS or ext2. I'm using Linux-2.4.2-ac28.

As you can see from the listing below, "dir1" appears after "sdir" in the
directory.

$ ./sanity.sh -k ./cvs conflicts
This test should produce no other output than this line, and a final "OK".
FAIL: conflicts-130
$ ls -alU /tmp/cvs-sanity/2/first-dir
total 8
drwxrwxr-x    1 proski   proski          0 Apr  2 11:47 .
drwxrwxr-x    1 proski   proski          0 Apr  2 11:47 ..
-rw-rw-r--    1 proski   proski         23 Apr  2 11:47 .#a.1.1
drwxrwxr-x    1 proski   proski          0 Apr  2 11:47 sdir
drwxrwxr-x    1 proski   proski          0 Apr  2 11:47 dir1
-rw-rw-r--    1 proski   proski         64 Apr  2 11:47 a
drwxrwxr-x    1 proski   proski          0 Apr  2 11:47 CVS
$

I can "fix" this test by using dotest_sort, but then conflicts-136 fails.
It appears that sanity.sh relies on the filesystem reporting filenames in
a particular order.

I want to get some feedback before I start fixing all the tests - it may
take a lot of time.

Another fix would be to require CVS to sort some lists. This time it's a
list of unknown files.

My statement about the test passing few days ago was wrong - I wasn't
using ramfs on /tmp back then.

Regards,
Pavel Roskin