506
64%
master: 66%

Ran 29 Aug 2016 02:34PM UTC

Jobs 5

Files 0

Run time –

Badge

Embed ▾

pending completion

Build # 506

Build Type

push

travis-ci

Committed by

xemul

Commit Message

rpc: Report back first error message on failure

When running criu in swrk mode the client typically wants to know
the reason of failure. Right now criu reports back NOTHING but the
fact that dump/restore/etc fails. We've tried to address this by
introducing the cr-errno engine, but it doesn't seem to be informative
enough and is hard to maintain -- adding new errno-s is boring :(

I propose to report back the first message with ERROR level upon
failrure as __typically__ the very first error message indicates
that proceeding is impossible and criu rolls back (generating more
error messages, so it's crucial to know the very first one).

If we ever meet the situation that the first pr_err/pr_perror doesn't
cause criu to exit, this printing should be fixed to be pr_warn.

Signed-off-by: Pavel Emelyanov <xemul@virtuozzo.com>
Acked-by: Andrei Vagin <avagin@virtuozzo.com>

Run Details

Jobs

ID	Job ID	Ran
2	506.2 (TR_ARCH=x86_64)	29 Aug 2016 02:34PM UTC	Travis Job 506.2
3	506.3 (TR_ARCH=armv7hf)	29 Aug 2016 02:45PM UTC	Travis Job 506.3
4	506.4 (TR_ARCH=aarch64)	29 Aug 2016 02:41PM UTC	Travis Job 506.4
5	506.5 (TR_ARCH=ppc64le)	29 Aug 2016 02:44PM UTC	Travis Job 506.5
6	506.6 (TR_ARCH=alpine)	29 Aug 2016 02:35PM UTC	Travis Job 506.6

Source Files on build 506

Coverage	∆	File	Lines	Relevant	Covered	Missed	Hits/Line

xemul / criu / 506
64%
master: 66%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 506

xemul / criu / 506 64% master: 66%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 506

xemul / criu / 506
64%
master: 66%

README BADGES
x