public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [PATCH 2/2] dim: Basic sanity check for nightly.conf
Date: Tue, 26 Sep 2017 14:57:11 +0300	[thread overview]
Message-ID: <87lgl18yg8.fsf@intel.com> (raw)
In-Reply-To: <20170926114524.19650-2-daniel.vetter@ffwll.ch>

On Tue, 26 Sep 2017, Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> Requested by Jani.

No, I didn't mean to request this. I meant, in patch 1, just do the

if [[ "${#drm_tip_repos[@]}" = "0" ]] || [[ "${#drm_tip_config[@]}" = "0" ]]; then

bit instead. That in itself will ensure the integration config is around
and contains sane data.

With the change in this patch, the read_integration_config movement
doesn't make a difference, you'll blow up on dim setup before you have
the drm-rerere repo around.

BR,
Jani.


>
> To do this properly we need to again push the reading of nightly.conf
> to be after the basic sanity checks, like it was before
>
> commit 12976ee32ae2cb97c7384ef6afde5f9076fc7d99
> Author: Jani Nikula <jani.nikula@intel.com>
> Date:   Fri Oct 28 12:40:46 2016 +0300
>
>     dim: switch to using remote agnostic integration branch config
>
> Cc: Jani Nikula <jani.nikula@intel.com>
> Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
> ---
>  dim | 12 ++++++++----
>  1 file changed, 8 insertions(+), 4 deletions(-)
>
> diff --git a/dim b/dim
> index 69109a4f8666..abc5d81f052a 100755
> --- a/dim
> +++ b/dim
> @@ -115,9 +115,12 @@ function read_integration_config
>  	declare -g -A drm_tip_repos
>  	declare -g -a drm_tip_config
>  
> -	if [ -r $DIM_PREFIX/drm-rerere/$integration_config ]; then
> -		# shellcheck source=/dev/null
> -		source $DIM_PREFIX/drm-rerere/$integration_config
> +	# shellcheck source=/dev/null
> +	source $DIM_PREFIX/drm-rerere/$integration_config
> +
> +	if [[ "${#drm_tip_repos[@]}" = "0" ]] || [[ "${#drm_tip_config[@]}" = "0" ]]; then
> +		echoerr "nightly.conf not set up correctly"
> +		exit 1
>  	fi
>  
>  	dim_branches=
> @@ -129,7 +132,6 @@ function read_integration_config
>  		fi
>  	done
>  }
> -read_integration_config
>  
>  function echoerr
>  {
> @@ -228,6 +230,8 @@ if [ "$subcommand" != "setup" ] && [ "$subcommand" != "help" ] && [ "$subcommand
>  	done
>  fi
>  
> +read_integration_config
> +
>  #
>  # Only function and alias definitions until the subcommand handling at the end.
>  #

-- 
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2017-09-26 11:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-26 11:45 [PATCH 1/2] dim: Make sure nightly.conf hasn't disappeared Daniel Vetter
2017-09-26 11:45 ` [PATCH 2/2] dim: Basic sanity check for nightly.conf Daniel Vetter
2017-09-26 11:57   ` Jani Nikula [this message]
2017-09-26 12:01 ` [PATCH 1/2] dim: Make sure nightly.conf hasn't disappeared Joonas Lahtinen

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=87lgl18yg8.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=daniel.vetter@intel.com \
    --cc=intel-gfx@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