Re: [PATCH v2 17/17] scripts/vm_smoke_test: double the timeout we wait for qemus

[Henning Schild <henning.schild@siemens.com>]

Am Mon, 16 Apr 2018 12:47:57 +0200
schrieb Andreas Reichel <andreas.reichel.ext@siemens.com>:

> On Fri, Apr 13, 2018 at 04:19:06PM +0200, Henning Schild wrote:
> > If the CI server is busy or our image boots slowly we might kill
> > qemu too early. Wait a little longer, will not make CI much slower.
> > 
> > Signed-off-by: Henning Schild <henning.schild@siemens.com>
> > ---
> >  scripts/vm_smoke_test | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/scripts/vm_smoke_test b/scripts/vm_smoke_test
> > index fde0e05..274ec1d 100755
> > --- a/scripts/vm_smoke_test
> > +++ b/scripts/vm_smoke_test
> > @@ -51,7 +51,7 @@ run_test () {
> >  
> >      # Start QEMU with Isar image
> >      start_vm -a $ARCH -d $DISTRO -o $CONSOLE_OUTPUT -p $PID_FILE
> > > /dev/null 2>&1 &
> > -    sleep 30
> > +    sleep 60  
> Just an idea without knowing what start_vm actually is: Why not
> working with the console output and wait for a login prompt?

That is exactly what it is doing. But at some point you will have to
decide that the image does not boot and that prompt will never come.
And that is this sleep.

Henning

> >      kill `cat $PID_FILE`
> >  
> >      # Check login prompt
> > -- 
> > 2.16.1
> >   
>