On Fri, 2015-11-27 at 16:54 +0000, Ian Jackson wrote:
> Fold `guest-localmigrate.2' into `guest-localmigrate/x10' and
> `guest-start.2' into `guest-start.repeat'. In each case increase the
> iteration count of the 2nd test by one so that the total number of
> reps remains constant.
>
> This will allow the heisenbug compensator to see more of these
> failures as the same failures.
>
> The resulting testid `guest-localmigrate/x10' becomes a bit misleading
> in that it now does 11 repetitions. But we don't want to change the
> testid.
I'd be inclined to just accept the possibility of missing a failure on the
11th iteration and just do 10 instead of 10+1.
> Signed-off-by: Ian Jackson <ian.jack...@eu.citrix.com>
> ---
> sg-run-job | 8 ++------
> 1 file changed, 2 insertions(+), 6 deletions(-)
>
> diff --git a/sg-run-job b/sg-run-job
> index 4f6b43a..a74d638 100755
> --- a/sg-run-job
> +++ b/sg-run-job
> @@ -374,10 +374,7 @@ proc test-guest-migr {g} {
> run-ts . =.2 ts-guest-saverestore + host $g
> }
> if {$can_migrate} {
> - run-ts . =.2 ts-guest-localmigrate + host $g
> - }
> - if {$can_migrate} {
> - run-ts . = ts-guest-localmigrate x10 + host $g
> + run-ts . =/x10 ts-guest-localmigrate + x11 host $g
> }
> }
>
> @@ -388,9 +385,8 @@ proc test-guest {g} {
>
> proc test-guest-nomigr {g} {
> run-ts . = ts-guest-stop + host $g
> - run-ts . =.2 ts-guest-start + host $g
>
> - repeat-ts 10 =.repeat \
> + repeat-ts 11 =.repeat \
When this repeat starts the guest is now stopped, whereas before it was
running. Does the body of the loop, which starts with a ts-guest-stop,
handle that?
Maybe you should remove the ts-guest-stop right at the start of this fn
too?
> + ts-guest-stop host $g \; \
> + ts-guest-start + host + $g +
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
