qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "罗勇刚(Yonggang Luo)" <luoyonggang@gmail.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 09:39:06 +0100	[thread overview]
Message-ID: <YuJLKn8y7LrjnBjK@redhat.com> (raw)
In-Reply-To: <CAE2XoE_Ki5QJSH9LNkFOzOwMFJdS=y6=bb2g=9ODawuFymADdA@mail.gmail.com>

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


> 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 :|



  parent reply	other threads:[~2022-07-28  9:17 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é [this message]
2022-07-28  9:28   ` 罗勇刚(Yonggang Luo)
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=YuJLKn8y7LrjnBjK@redhat.com \
    --to=berrange@redhat.com \
    --cc=luoyonggang@gmail.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 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).