comparison tests/test-bisect.out @ 9584:17da88da1abd

bisect: use util.system and fix good/bad when using -c The existing scheme using util.find_exe and subprocess.call meant we couldn't use simple shell commands in tests. Fix that. Also, it mistakenly used status from the system() call rather than good from the bisect call in reporting results.
author Matt Mackall <mpm@selenic.com>
date Mon, 12 Oct 2009 18:25:46 -0500
parents 2726a6df11e9
children 807633f1e3c2
comparison
equal deleted inserted replaced
9583:0491be4448bf 9584:17da88da1abd
302 user: test 302 user: test
303 date: Thu Jan 01 00:00:06 1970 +0000 303 date: Thu Jan 01 00:00:06 1970 +0000
304 summary: msg 6 304 summary: msg 6
305 305
306 % test invalid command 306 % test invalid command
307 abort: cannot find executable: foobar 307 /bin/sh: foobar: command not found
308 abort: failed to execute foobar
308 % test bisecting command 309 % test bisecting command
309 Testing changeset 15:e7fa0811edb0 (31 changesets remaining, ~4 tests) 310 Testing changeset 15:e7fa0811edb0 (31 changesets remaining, ~4 tests)
310 1 files updated, 0 files merged, 0 files removed, 0 files unresolved 311 1 files updated, 0 files merged, 0 files removed, 0 files unresolved
311 Changeset 15:e7fa0811edb0: good 312 Changeset 15:e7fa0811edb0: good
312 Changeset 7:03750880c6b5: good 313 Changeset 7:03750880c6b5: good