xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Ian.Jackson@eu.citrix.com, xen-devel@lists.xen.org
Subject: [PATCH OSSTEST RFC 0/2] simplify testing with adhoc jobs
Date: Tue, 15 Sep 2015 10:00:20 +0100	[thread overview]
Message-ID: <1442307620.3549.333.camel@citrix.com> (raw)

While I was doing some adhoc testing on chardonnay I needed to define some
adhoc recipes and ended up writing the following two patches.

In the end I didn't end up using the first (I just created the job out of
whole cloth rather than copying an existing template and modifying).

For the second I was using an sg-run-job-adhoc containing:
    proc need-hosts/adhoc-xen-boot-x5 {} { return host }
    proc run-job/adhoc-xen-boot-x5 {} {
        repeat-ts 5 xen-boot.repeat \
                   ts-host-reboot     host \; \
                   ts-host-ping-check host 
    }
Which arguably could a useful addition to sg-run-job proper.

Anyway, here they are...

We also discussed making it possible to invert the bisector (i.e. to look
for a patch which fixed an issue), in the end by the time I'd done a bit of
adhoc work to narrow the range down to something the bisector wouldn't balk
at I had a pretty good guess which merge commit it was going to be, so
finding the commit was just a few more adhoc jobs.

Ian.

             reply	other threads:[~2015-09-15  9:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-15  9:00 Ian Campbell [this message]
2015-09-15  9:00 ` [PATCH OSSTEST RFC 1/2] cs-adjust-flight: add recipe-set to adjust the recipe for a set of jobs Ian Campbell
2015-09-15 14:44   ` Ian Jackson
2015-09-15  9:00 ` [PATCH OSSTEST RFC 2/2] sg-run-job: support dropping in adhoc test recipes Ian Campbell
2015-09-15 14:44   ` 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=1442307620.3549.333.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).