Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mauro.chehab@linux.intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t] runner: Fix handling of per-test-timeout
Date: Mon, 28 Mar 2022 12:02:33 +0200	[thread overview]
Message-ID: <20220328120233.12e172eb@maurocar-mobl2> (raw)
In-Reply-To: <20220328091329.16009-1-petri.latvala@intel.com>

On Mon, 28 Mar 2022 12:13:29 +0300
Petri Latvala <petri.latvala@intel.com> wrote:

> Instead of stopping execution on resume-init success, stop on
> resume-init failure like intended.
> 
> Fixes: 4b88a9253443 ("runner: check if it has root permissions")
> Signed-off-by: Petri Latvala <petri.latvala@intel.com>
> Cc: Mauro Carvalho Chehab <mchehab@kernel.org>
Reviewed-by: Mauro Carvalho Chehab <mchehab@kernel.org>
> ---
>  runner/executor.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/runner/executor.c b/runner/executor.c
> index b4efc4fd..6e6ca9cc 100644
> --- a/runner/executor.c
> +++ b/runner/executor.c
> @@ -2043,7 +2043,7 @@ bool execute(struct execute_state *state,
>  			}
>  			close(sigfd);
>  			close(testdirfd);
> -			if (initialize_execute_state_from_resume(resdirfd, state, settings, job_list))
> +			if (!initialize_execute_state_from_resume(resdirfd, state, settings, job_list))
>  				return false;
>  			state->time_left = time_left;
>  			return execute(state, settings, job_list);

  parent reply	other threads:[~2022-03-28 10:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-28  9:13 [igt-dev] [PATCH i-g-t] runner: Fix handling of per-test-timeout Petri Latvala
2022-03-28  9:52 ` Mauro Carvalho Chehab
2022-03-28 10:02 ` Mauro Carvalho Chehab [this message]
2022-03-28 11:24 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2022-03-28 13:07 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220328120233.12e172eb@maurocar-mobl2 \
    --to=mauro.chehab@linux.intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox