Re: What to do with 'make check'?

[Paul Eggert]

mwoehlke <address@hidden> writes:

  [for chgrp/basic]
  + chgrp -h 522 symlink
  ++ stat --printf=%g f
  + test 116 = 116
  ++ stat --printf=%g symlink
  + test 0 = 522
  + fail=1

This indicates that "chgrp -h 522 symlink" is not working.  Can you
test this separately, e.g., by "ktrace -o /tmp/tr chgrp -h 522
symlink", to see which system calls are being executed?  You will need
to prepend the src directory to your PATH.

  [for chmod/no-x]
  + mkdir -p a/b
  + cd a
  + chmod a-x . b
  + fail=1

This indicates that "chmod a-x . b" succeeded, but it should have
failed because it should have made "." unsearchable before attempting
to access "b" (aka "./b").  Again, can you please try to see what
system calls chmod is doing, with "ktrace -o /tmp/tr chmod a-x . b"?

  [for cp/fail-perm]
  + mkdir D
  + ...
  + chmod 0 D
  + ln -s D/D symlink
  + touch F
  + ...
  + cp F symlink
  + fail=1

This indicates that "cp F symlink" succeeded, where it should have failed.
Again, "ktrace -o /tmp/tr cp F symlink" should tell us why.

  [for du/inaccessible-cwd]
  + mkdir -p inaccessible-cwd.tmp/5675
  + cd inaccessible-cwd.tmp/5675
  + mkdir -p no-x a/b
  + cd no-x
  + chmod 0 .
  + ...
  + du 
/home/install/gnu/alpha/src/coreutils-6.3/tests/du/inaccessible-cwd.tmp/5675/a
  du: unable to record current working directory: Permission denied
  + fail=1

Again, try the same setup, with "ktrace -o /tmp/tr du
.../inaccessible-cwd.tmp/5675/a".


[for power_darwin-local]
Why does pinky dump core?  What does ktrace say for it?


[for tests/mv/i-2]
+ echo e >e
+ echo f >f
+ echo y >y
+ chmod 0 f
+ cp -if e f <y >out 2>&1
+ ...
+ fail=1

Here, "cp" is supposed to output the message

cp: overwrite `f', overriding mode 0000?

into the file 'out'.  What does it output instead?


[for tests/rm/rm3, summarizing]
mkdir -p z
echo not-empty > z/fu
chmod u-w z/fu
rm -ir z
-rm: remove regular file `z/fu'
+rm: remove write-protected regular file `z/fu'

For some reason "rm" didn't think z/u was write-protected.
Can you try "ktrace -o /tmp/tr rm -ir z" to find out why?


Which of these tests, if any, were you running as root?


I hope the above comments lets you figure out how to do this sort of
analysis yourself.  If you have any questions along these lines please
let us know.