Re: [Xen-devel] [OSSTEST PATCH] README: Better documentation of recipes, db, etc.

[Roger Pau Monné <roger.pau@xxxxxxxxxx>]

On Fri, Sep 08, 2017 at 02:52:36PM +0100, Ian Jackson wrote:
> CC: George Dunlap <george.dunlap@xxxxxxxxxx>
> Signed-off-by: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>

Reviewed-by: Roger Pau Monné <roger.pau@xxxxxxxxxx>

Just one comment, which is probably pointless...

> ---
>  README | 75 
> ++++++++++++++++++++++++++++++++++++++++++++++++++++--------------
>  1 file changed, 60 insertions(+), 15 deletions(-)
> 
> diff --git a/README b/README
> index ffe0018..93129e3 100644
> --- a/README
> +++ b/README
> @@ -8,32 +8,55 @@ Terminology
>  
>  "flight":
>  
> -    Each run of osstest is referred to as a "flight". Each flight is
> -    given a unique ID (a number or name).
> +    Each run of osstest is referred to as a "flight".  Each flight is
> +    given a unique ID.
> +
> +    Standalone mode generally uses a flight named "standalone", which
> +    is frequently erased and reused.  In "Executive" mode (used for
> +    production osstest instances) flights are numbered and the
> +    metadata is permanently recorded.
>  
>  "job":
>  
> -    Each flight consists of one or more "jobs". These are a sequence
> +    Each flight consists of one or more "jobs".  These are a sequence
>      of test steps run in order and correspond to a column in the test
> -    report grid. They have names like "build-amd64" or
> -    "test-amd64-amd64-pv". A job can depend on the output of another
> +    report grid.  They have names like "build-amd64" or
> +    "test-amd64-amd64-pv".  A job can depend on the output of another
>      job in the flight -- e.g. most test-* jobs depend on one or more
>      build-* jobs.
>  
> +    A job has a named "recipe", which indicates what things need to be
                                                        ^ steps maybe?

Thanks, Roger.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel