error in test-bisect

Stuart W. Marks smarks at smarks.org
Tue Nov 3 22:53:48 CST 2009


I just pulled crew and now my test run gets an error in test-bisect. This seems 
related to:

   changeset:   9692:807633f1e3c2
   user:        Sune Foldager <cryo at cyanite.org>
   date:        Mon Nov 02 10:18:43 2009 +0100
   summary:     test-bisect: fix shell-dependent output

The error is:

   ERROR: test-bisect output changed
   --- Expected output
   +++ Test output
   @@ -304,7 +304,7 @@
    summary:     msg 6

    % test invalid command
   -/bin/sh: ./foobar: not found
   +/bin/sh: ./foobar: No such file or directory
    abort: failed to execute ./foobar
    % test bisecting command
    Testing changeset 15:e7fa0811edb0 (31 changesets remaining, ~4 tests)

The bisect command seems to behave correctly; it's just that the error message 
is still system-specific. I'm on MacOS X 10.5.8, where /bin/sh is bash. The 
change was to replace the invocation of "foobar" with "./foobar" but on MacOS 
oddly enough this changes the error message from "command not found" to "No 
such file or directory":

   $ /bin/sh -c foobar
   /bin/sh: foobar: command not found
   $ /bin/sh -c ./foobar
   /bin/sh: ./foobar: No such file or directory

I'm not sure of the best way to deal with this. Maybe send stderr in this case 
to file and then do pattern-matching over it? Or maybe omit this part of the 
test; it might not be worth the trouble.

s'marks


More information about the Mercurial-devel mailing list