On Wed, Oct 25, 2017 at 04:23:35PM +0100, Anthony PERARD wrote: > On Wed, Oct 25, 2017 at 04:17:26PM +0100, Wei Liu wrote: > > On Tue, Oct 24, 2017 at 02:38:39PM +0100, Ian Jackson wrote: > > > > Also, what a developper should do when the build fail? She can't modify > > > > the current code, because changes are going to be losts. Maybe we could > > > > trap failures, restore original HEAD and point out which commit fails to > > > > build. > > > > > > IWBNI it would at least print the branch to checkout. Tools like "git > > > bisect" record the information in .git and allow "git bisect reset". > > > > Not sure I follow. Do you want the script to trap SIGCHLD, test the > > return value and act accordingly? > > In scripts with `set -e`, `trap 'echo something failed' EXIT` is enough. > But that is probably not necessary here, you could just check the return > value of the build command, then start printing imformation about > what/where it went wrong, and how to go back.
Either is fine. Thanks for the suggestion. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel