Re: [Xen-devel] [OSSTEST PATCH 4/4] README.bisection: New consumer-oriented document

[Wei Liu <wei.liu2@xxxxxxxxxx>]

On Mon, Oct 19, 2015 at 05:15:35PM +0100, Ian Jackson wrote:
[...]
> +
> +The bisection report email lists the relevant trees:
> +
> +  Tree: linux git://xenbits.xen.org/linux-pvops.git
> +  Tree: linuxfirmware git://xenbits.xen.org/osstest/linux-firmware.git
> +  Tree: qemu git://xenbits.xen.org/staging/qemu-xen-unstable.git
> +  Tree: qemuu git://xenbits.xen.org/staging/qemu-upstream-unstable.git
> +  Tree: xen git://xenbits.xen.org/xen.git
> +        ^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> +         |       url used for fetching the bits
> +      |
> +         ` Identifier indicating the purpose for which the tree
> +        is used.

A tab was inserted here.

> +
> +
> +Result
> +------
[...]
> +Progress Reports
> +================
> +
> +When the bisector is running, it sends similar-looking emails to the
> +osstest-output mailing list.
> +
> +These contain the roughly same information; instead of "complete" they
> +may say "running", "inconclusive", "unreproducible", etc.

On xen-devel there are only "complete" emails. It might be helpful to
send "unreproducible" and / or "inconclusive" emails as well? What I'm
thinking is that it would be helpful to clearly indicate human
intervention is needed.

Wei.

> -- 
> 1.7.10.4

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