[email protected] (Trent W. Buck) writes: > Another thing I sometimes do to test a command "foo" is > > env -i >/dev/null 2>&1 </dev/null foo > > which ought to remove tty-ness as well as all environment variables > (e.g. $HOME and $TERM). Sticking a "sudo -u nobody" in front also > occurs to me, since sometimes programs use nss to expand ~ instead of > honouring $HOME... sudo -u won't reset HOME if that's what you mean (throw in -H). Moreover, buildbot usually uses PTYs to let programs run in a virtual TTY. Environment may be a better bet, or inherited signal handlers (or something else inherited) or similar issue. Although IIRC exec clears most of the inherited stuff.
The most interesting test I can currently think of is to run the harness (i.e. Setup) in valgrind. Without buildbot first (it may be that the bug is always there, but the subtle difference in environment causes it not to trigger -- valgrind may still detect it though) and if that fails within buildbot. Yours, Petr. _______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
