[CRIU] few remaining s390 zdtm failures (for me)

[Adrian Reber]

On Thu, Aug 10, 2017 at 02:37:55PM +0300, Pavel Emelyanov wrote:
> On 08/09/2017 09:32 PM, Adrian Reber wrote:
> > On Wed, Aug 09, 2017 at 07:11:45PM +0300, Pavel Emelyanov wrote:
> >> On 08/08/2017 02:40 PM, Adrian Reber wrote:
> >>> Running on RHEL s390x I have few zdtm test cases failing which do not
> >>> fail on x86_64 and ppc64le.
> >>>
> >>>   * zdtm/static/vdso02(ns)
> >>>   * zdtm/static/stopped(h)
> >>>   * zdtm/static/stopped01(h)
> >>>   * zdtm/static/stopped02(h)
> >>>   * zdtm/static/stopped12(ns)
> >>>
> >>> Error messages are all the same like:
> >>>
> >>> (01.503563) cg: Set 1 is criu one
> >>> (01.503686) Seized task 24, state 1
> >>> (01.503715) Collected (4 attempts, 0 in_progress)
> >>> (01.503728) Seized task 25, state 0
> >>> (01.503912) Error (compel/src/lib/infect.c:180): SEIZE 25: task not stopped after seize
> >>
> >> Can you put task_is_trapped()-like messages in this place so that we could
> >> see what's wrong with this task?
> > 
> > Like this?
> > 
> > (00.034673) Error (compel/src/lib/infect.c:1446): Task 25 is in unexpected state: 200
> > (00.034675) Error (compel/src/lib/infect.c:1448): Task exited with 2
> 
> Looks like yes, but ... hm ... exited. Which exact test is that? Or any of the above
> behaves like that?

Console output: https://lisas.de/~adrian/s390-zdtm-failures

		Adrian