RFC simplify testing with adhoc jobs
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest2 patches 2 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | cs-adjust-flight: add recipe-set to adjust the recipe for a set of jobscs-adjust-flight | +16 | 1 reply | |
| 2/2 | sg-run-job: support dropping in adhoc test recipessg-run-job | +4 | 1 reply |
Reviews trailers per patch
All 2 patches have a Reviewed-by or Acked-by.
| Patch | Ian Jackson |
|---|---|
| 1/2 | A-b |
| 2/2 | A-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH OSSTEST RFC 0/2] simplify testing with adhoc jobs
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.