qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: Thomas Huth <thuth@redhat.com>, Cornelia Huck <cohuck@redhat.com>,
	Richard Henderson <richard.henderson@linaro.org>,
	qemu-devel@nongnu.org,
	Wainer dos Santos Moschetta <wainersm@redhat.com>,
	f4bug@amsat.org, Willian Rampazzo <willianr@redhat.com>
Subject: Re: [RFC PATCH] gitlab: add special rule for the hexagon container
Date: Mon, 24 May 2021 16:04:37 +0100	[thread overview]
Message-ID: <87lf8441ez.fsf@linaro.org> (raw)
In-Reply-To: <YKu86ptxc4FomsuI@redhat.com>


Daniel P. Berrangé <berrange@redhat.com> writes:

> On Mon, May 24, 2021 at 07:35:59AM -0700, Richard Henderson wrote:
>> On 5/20/21 8:19 AM, Alex Bennée wrote:
>> > The hexagon container is always manually built but of course not
>> > everyone will be building it themselves and pushing to their
>> > registries. We still need to create a "local" registry copy for the
>> > actual gitlab tests to run. We don't build it in this case, just pull
>> > it across from the upstream registry. We disable this rule from
>> > running on the qemu-project itself so it doesn't accidentally wipe out
>> > our master copy.
>> > 
>> > Fixes: 910c40ee94 ("gitlab: add build-user-hexagon test")
>> > Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
>> > Cc: Cornelia Huck <cohuck@redhat.com>
>> > ---
>> 
>> I get
>> 
>> Found errors in your .gitlab-ci.yml:
>> jobs:build-user-hexagon:needs config uses invalid types: bridge
>
> Bizarre message, but the problem looks like this:
>
>
>> > diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
>> > index f718b61fa7..a04cca9db0 100644
>> > --- a/.gitlab-ci.yml
>> > +++ b/.gitlab-ci.yml
>> > @@ -421,6 +421,8 @@ build-user-static:
>> >   # declared. The image is manually uploaded.
>> >   build-user-hexagon:
>> >     extends: .native_build_job_template
>> > +  needs:
>> > +    hob: hexagon-cross-container
>
> Indent and syntax is wrong - should be
>
>    needs:
>      - job: hexagon-cross-container
>
> with indent at same level as 'extends'

This is why v2 was posted fairly quickly :-/

Also in the rolled up series I posted on Thursday:

  Subject: [PATCH  v1 0/8] various misc fixes (gitlab, gdbstub, plugins)
  Date: Thu, 20 May 2021 18:42:55 +0100
  Message-Id: <20210520174303.12310-1-alex.bennee@linaro.org>

>
>> >     variables:
>> >       IMAGE: debian-hexagon-cross
>> >       TARGETS: hexagon-linux-user
>> > 
>> 
>> 
>
> Regards,
> Daniel


-- 
Alex Bennée


      reply	other threads:[~2021-05-24 15:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-20 15:19 [RFC PATCH] gitlab: add special rule for the hexagon container Alex Bennée
2021-05-24 14:35 ` Richard Henderson
2021-05-24 14:49   ` Daniel P. Berrangé
2021-05-24 15:04     ` Alex Bennée [this message]

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=87lf8441ez.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=berrange@redhat.com \
    --cc=cohuck@redhat.com \
    --cc=f4bug@amsat.org \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --cc=thuth@redhat.com \
    --cc=wainersm@redhat.com \
    --cc=willianr@redhat.com \
    /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;
as well as URLs for NNTP newsgroup(s).