Oops. I missed part of the diff.
On Wed, Oct/17/2007 04:22:51PM, Jeff Squyres wrote:
> What is Timing($cmd, timestr($timediff));?
>
> That's not found on my OS X on RHEL4U4 boxen.
>
>
>
> On Oct 17, 2007, at 4:14 PM, Ethan Mallove wrote:
>
> > On Wed, Oct/17/2007 04:01:43PM, Jeff Squyres wrot
What is Timing($cmd, timestr($timediff));?
That's not found on my OS X on RHEL4U4 boxen.
On Oct 17, 2007, at 4:14 PM, Ethan Mallove wrote:
On Wed, Oct/17/2007 04:01:43PM, Jeff Squyres wrote:
There was no patch attached...
On Oct 17, 2007, at 3:18 PM, Ethan Mallove wrote:
WHAT: Add timing
On Wed, Oct/17/2007 04:01:43PM, Jeff Squyres wrote:
> There was no patch attached...
>
> On Oct 17, 2007, at 3:18 PM, Ethan Mallove wrote:
>
> > WHAT: Add timing info to DoCommand::Cmd
> >
> > WHY: Need visibility into how long individual commands are
> > taking (right now we only time entire pha
There was no patch attached...
On Oct 17, 2007, at 3:18 PM, Ethan Mallove wrote:
WHAT: Add timing info to DoCommand::Cmd
WHY: Need visibility into how long individual commands are
taking (right now we only time entire phases).
WHERE: DoCommand.pm, client/mtt, Messages.pm
WHEN: ASAP
---
WHAT: Add timing info to DoCommand::Cmd
WHY: Need visibility into how long individual commands are
taking (right now we only time entire phases).
WHERE: DoCommand.pm, client/mtt, Messages.pm
WHEN: ASAP
---
I need to see how long individual commands are taking within
an MTT run. There is a
On Oct 17, 2007, at 9:31 AM, Ethan Mallove wrote:
Either or both of those would be fine (don't we have a timeout in
DoCommand.pm already?).
There is a timeout in DoCommand, but currently I keep
reinvoking DoCommand on each "interrupted system call" so
the timeout gets reset each time. This wou
On Wed, Oct/17/2007 07:45:53AM, Jeff Squyres wrote:
> On Oct 16, 2007, at 6:36 PM, Ethan Mallove wrote:
>
> >>> The bail is that "make" will eventually succeed or fail
> >>> with something other than "interrupted system call". Do
> >>> we need another condition?
> >>
> >> I'm just worried that Sun
On Oct 16, 2007, at 6:36 PM, Ethan Mallove wrote:
The bail is that "make" will eventually succeed or fail
with something other than "interrupted system call". Do
we need another condition?
I'm just worried that Sun's NFS will somehow get in a
perpetual "interrupted system call" loop such that