All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel@lists.xen.org
Subject: Re: [PATCH OSSTEST v2 5/5] ms-flights-summary: Produce an HTML report of all active flights
Date: Fri, 31 Jul 2015 16:58:23 +0100	[thread overview]
Message-ID: <1438358303.30740.73.camel@citrix.com> (raw)
In-Reply-To: <21947.39259.589923.46525@mariner.uk.xensource.com>

On Fri, 2015-07-31 at 16:50 +0100, Ian Jackson wrote:
> Ian Campbell writes ("[PATCH OSSTEST v2 5/5] ms-flights-summary: Produce 
> an HTML report of all active flights"):
> > This could surely use better Perl and produce better output, however
> > I'm sending it now because it would be useful for further development
> > if some or all of the preceding patches could go into production and
> > this serves as an example of why I think I want them.
> 
> I think it's pretty good actually.  I have some minor stylistic
> comments.  I haven't inspected the output, but as you say we can
> improve it later.

Thanks, I actually posted a v3 shortly after which rewrote a lot of this.

I'll try and apply those of your comments which are relevant to the v3
though.

> > diff --git a/ms-planner b/ms-planner
> > index f38f05b..35d430b 100755
> > --- a/ms-planner
> > +++ b/ms-planner
> > @@ -289,6 +289,7 @@ END
> >  	    $info= "rogue task $arow->{subtask}";
> >  	}
> >  	$plan->{Allocations}{$reskey}= {
> > +	    # Can we find a Job here?
> >              Task => $arow->{owntaskid},
> >  	    Info => $info,
> 
> I don't understand this comment.

This didn't really belong in this patch. It was in relation to this
paragraph from patch #1's commit message:

    cmd_reset does not include a ->Job for jobs which are "(preparing)",
    corresponding to a job which is going to use a shared host which is
    currently being installed by another job. I was unable to figure out a
    way to include these.

The upshot is that N-1 of the N jobs which are going to share a host sit in
the "Anonymous Jobs" list until the first job has finished with the actual
installation of the host, instead of being associated with the proper job.

I wasn't able to figure out how to get the original Job to include in those
records in the allocations.

Ian.

  reply	other threads:[~2015-07-31 15:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-14 13:58 [PATCH OSSTEST v2 0/5] add a flight summary html report Ian Campbell
2015-07-14 13:58 ` [PATCH OSSTEST v2 1/5] ms-planner: Propagate a booking's Job to the plan Ian Campbell
2015-07-31 15:39   ` Ian Jackson
2015-07-14 13:58 ` [PATCH OSSTEST v2 2/5] ms-planner: Expose the plan start in json Ian Campbell
2015-07-31 15:38   ` Ian Jackson
2015-07-14 13:58 ` [PATCH OSSTEST v2 3/5] ts-hosts-allocate-Executive: Add the requesting Job to the booking Ian Campbell
2015-07-31 15:41   ` Ian Jackson
2015-07-14 13:58 ` [PATCH OSSTEST v2 4/5] Osstest::Executive: Export get_plan Ian Campbell
2015-07-31 15:42   ` Ian Jackson
2015-07-14 13:58 ` [PATCH OSSTEST v2 5/5] ms-flights-summary: Produce an HTML report of all active flights Ian Campbell
2015-07-16 16:55   ` Ian Campbell
2015-07-31 15:50   ` Ian Jackson
2015-07-31 15:58     ` Ian Campbell [this message]
2015-07-31 16:04       ` Ian Jackson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1438358303.30740.73.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.