Re: t5570 trap use in start/stop_git_daemon

2015-02-13 Thread Jeff King
On Fri, Feb 13, 2015 at 02:44:03AM -0500, Jeff King wrote: On Thu, Feb 12, 2015 at 03:31:12PM -0500, Randall S. Becker wrote: On the NonStop port, we found that “trap” was causing an issue with test success for t5570. When start_git_daemon completes, the shell (ksh,bash) on this platform

Re: t5570 trap use in start/stop_git_daemon

2015-02-13 Thread Joachim Schmitz
Jeff King peff at peff.net writes: On Fri, Feb 13, 2015 at 02:44:03AM -0500, Jeff King wrote: On Thu, Feb 12, 2015 at 03:31:12PM -0500, Randall S. Becker wrote: snip Hmm, today I learned something new about ksh. Apparently when you use the function keyword to define a function like:

RE: t5570 trap use in start/stop_git_daemon

2015-02-13 Thread Randall S. Becker
On 2015/02/13 3:58AM Joachim Schmitz wrote: Jeff King peff at peff.net writes: On Fri, Feb 13, 2015 at 02:44:03AM -0500, Jeff King wrote: On Thu, Feb 12, 2015 at 03:31:12PM -0500, Randall S. Becker wrote: snip Hmm, today I learned something new about ksh. Apparently when you use the

Re: t5570 trap use in start/stop_git_daemon

2015-02-12 Thread Jeff King
On Thu, Feb 12, 2015 at 03:31:12PM -0500, Randall S. Becker wrote: On the NonStop port, we found that “trap” was causing an issue with test success for t5570. When start_git_daemon completes, the shell (ksh,bash) on this platform is sending a signal 0 that is being caught and acted on by the