[CRIU] [PATCH v1] zdtm: implement testing of --leave-stopped criu option

Pavel Emelyanov xemul at virtuozzo.com
Fri Aug 19 05:16:27 PDT 2016


On 08/19/2016 03:03 PM, Eugene Batalov wrote:
> Would this --rstop option be used in CI?

Of course!

> Maybe I also need to add it to some jenkins scripts?

That'd be awesome :)

> 2016-08-19 13:40 GMT+03:00 Pavel Emelyanov <xemul at virtuozzo.com <mailto:xemul at virtuozzo.com>>:
> 
>     On 08/12/2016 05:49 PM, Eugene Batalov wrote:
>     > Test does its checking both after dump and after restore.
>     > Checking is done in the following way:
>     > 1. Check that every ps tree process is stopped or dead
>     > 2a. SIGKILL every ps tree process if checking after dump
>     > 2b. SIGCONT every ps tree process if checking after restore
> 
>     It's > < that close to getting merged :) One comment inline
> 
>     > diff --git a/test/zdtm/transition/fork.desc b/test/zdtm/transition/fork.desc
>     > new file mode 100644
>     > index 0000000..843347e
>     > --- /dev/null
>     > +++ b/test/zdtm/transition/fork.desc
>     > @@ -0,0 +1 @@
>     > +{'opts': '--leave-stopped'}
>     >
> 
>     Instead of making the --leave-stopped be an option of a single test,
>     add the --rstop option to zdtm.py itself, so that this engine could
>     restore __any__ sub-test in stopped state.
> 
> 
> 
> 
> -- 
> Best regards,
> Eugene Batalov.



More information about the CRIU mailing list