Show exit codes in unified tests?

Martin Geisler mg at lazybytes.net
Wed Sep 15 17:30:22 CDT 2010


Dirkjan Ochtman <dirkjan at ochtman.nl> writes:

> On Wed, Sep 15, 2010 at 22:14, Matt Mackall <mpm at selenic.com> wrote:
>> This only show nonzero exit codes. Turning this on currently breaks 107
>> tests. And there are probably issues with different exit codes from
>> non-hg tools on different platforms we'd need to sort out too.
>
> I like the idea. Can we come up with a method to alleviate
> cross-platform incompatibility? I.e. allowing specifying multiple
> allowed return codes.

I like it too -- and can we not catch the different error codes using a
regexp like we do the for the rest of the test? Something like

  $ command
  \[(1|42|255)\]

though the escaping makes the square brackets a bad choice. Maybe like
this instead

  $ command
  exit code: (1|42|255)

which I think reads quite nicely.

-- 
Martin Geisler

Mercurial links: http://mercurial.ch/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20100916/de929ed6/attachment.pgp>


More information about the Mercurial-devel mailing list