From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Stefan Weil <sw@weilnetz.de>,
QEMU Developers <qemu-devel@nongnu.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Richard Henderson <richard.henderson@linaro.org>,
Peter Maydell <peter.maydell@linaro.org>
Subject: Re: Timeouts in CI jobs
Date: Thu, 25 Apr 2024 14:30:00 +0100 [thread overview]
Message-ID: <Zipa2DPKX0Z0jXtK@redhat.com> (raw)
In-Reply-To: <ZipaNZ5JD_7pM6Xp@redhat.com>
On Thu, Apr 25, 2024 at 02:27:17PM +0100, Daniel P. Berrangé wrote:
> On Wed, Apr 24, 2024 at 08:10:19PM +0200, Stefan Weil wrote:
> >
> > I did not run tests in my GitLab fork because I still have to figure out how
> > to do that.
>
> It is quite simple:
>
> git remote add gitlab ssh://git@gitlab.com/<yourusername>/qemu
> git push gitlab -o QEMU_CI=2
Sorry, mistake, the second line should be
git push gitlab -o ci.variable=QEMU_CI=2
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 :|
prev parent reply other threads:[~2024-04-25 13:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-16 12:10 cross-i686-tci CI job is flaky again (timeouts): can somebody who cares about TCI investigate? Peter Maydell
2024-04-16 12:17 ` Stefan Weil via
2024-04-20 20:25 ` Stefan Weil via
2024-04-24 16:27 ` Timeouts in CI jobs (was: cross-i686-tci CI job is flaky again (timeouts): can somebody who cares about TCI investigate?) Stefan Weil via
2024-04-24 17:09 ` Daniel P. Berrangé
2024-04-24 18:10 ` Timeouts in CI jobs Stefan Weil via
2024-04-25 13:27 ` Daniel P. Berrangé
2024-04-25 13:30 ` Daniel P. Berrangé [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=Zipa2DPKX0Z0jXtK@redhat.com \
--to=berrange@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=sw@weilnetz.de \
/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).