All of lore.kernel.org
 help / color / mirror / Atom feed
From: "罗勇刚(Yonggang Luo)" <luoyonggang@gmail.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: qemu-level <qemu-devel@nongnu.org>
Subject: Re: When create a new qemu fork, can not run pipeline, what I need to do?
Date: Thu, 28 Jul 2022 17:28:59 +0800	[thread overview]
Message-ID: <CAE2XoE-KfoKtcepFgT9zSj6TDtu+T04=TA=4eDxumF6RNrPYyA@mail.gmail.com> (raw)
In-Reply-To: <YuJLKn8y7LrjnBjK@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1049 bytes --]

On Thu, Jul 28, 2022 at 4:39 PM Daniel P. Berrangé <berrange@redhat.com>
wrote:
>
> On Wed, Jul 27, 2022 at 07:20:51PM +0800, 罗勇刚(Yonggang Luo) wrote:
> > ···
> > Pipeline cannot be run.
> >
> > No stages / jobs for this pipeline.
>
> No jobs are created until you set 'QEMU_CI=1', which creates jobs and
> lets them be manually started, or set 'QEMU_CI=2' which creates jobs
> and runs them all immediately. Please see:
>
>   docs/devel/ci-jobs.rst.inc
>

Thanks, I've tried to locate this but not found it

>
> > The form contains the following warning:
> >
> > 121 warnings found: showing first 25
>
> The warnings are harmless since we don't use merge requests.
>
> With regards,
> Daniel
> --
> |: https://berrange.com      -o-
https://www.flickr.com/photos/dberrange :|
> |: https://libvirt.org         -o-
https://fstop138.berrange.com :|
> |: https://entangle-photo.org    -o-
https://www.instagram.com/dberrange :|
>


--
         此致
礼
罗勇刚
Yours
    sincerely,
Yonggang Luo

[-- Attachment #2: Type: text/html, Size: 1652 bytes --]

  reply	other threads:[~2022-07-28  9:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-27 11:20 When create a new qemu fork, can not run pipeline, what I need to do? 罗勇刚(Yonggang Luo)
2022-07-27 21:15 ` Philippe Mathieu-Daudé via
2022-07-28  8:39 ` Daniel P. Berrangé
2022-07-28  9:28   ` 罗勇刚(Yonggang Luo) [this message]
2022-07-28 10:56     ` Philippe Mathieu-Daudé via

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='CAE2XoE-KfoKtcepFgT9zSj6TDtu+T04=TA=4eDxumF6RNrPYyA@mail.gmail.com' \
    --to=luoyonggang@gmail.com \
    --cc=berrange@redhat.com \
    --cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.