----- Original Message -----
> From: "Peter Maydell" <peter.mayd...@linaro.org>
> To: "Cleber Rosa" <cr...@redhat.com>
> Cc: "Alex Bennée" <alex.ben...@linaro.org>, "QEMU Developers"
> <qemu-devel@nongnu.org>, "Fam Zheng" <f...@euphon.net>,
> "Eduardo Habkost" <ehabk...@redhat.com>, "Beraldo Leal" <bl...@redhat.com>,
> "Philippe Mathieu-Daudé"
> <phi...@redhat.com>, "Thomas Huth" <th...@redhat.com>, "Wainer dos Santos
> Moschetta" <waine...@redhat.com>, "Erik
> Skultety" <eskul...@redhat.com>, "Willian Rampazzo" <wramp...@redhat.com>,
> "Wainer Moschetta" <wmosc...@redhat.com>
> Sent: Monday, March 16, 2020 7:57:33 AM
> Subject: Re: [PATCH 0/5] QEMU Gating CI
>
> On Thu, 12 Mar 2020 at 22:16, Cleber Rosa <cr...@redhat.com> wrote:
> > The quick answer is:
> >
> > $ git push g...@gitlab.com:qemu-project/qemu.git my-branch:staging
>
> So I did this bit...
>
> > Once that push happens, you could use:
> >
> > $ contrib/ci/scripts/gitlab-pipeline-status --verbose --wait
>
> ...but this script just says:
>
> $ ./contrib/ci/scripts/gitlab-pipeline-status --verbose --wait
> ERROR: No pipeline found
> failure
>
Hi Peter,
A few possible reasons come to my mind:
1) It usually takes a few seconds after the push for the pipeline to
2) If you've pushed to a repo different than gitlab.com/qemu-project/qemu,
you'd have to tweak the project ID (-p|--project-id).
3) The local branch is not called "staging", so the script can not find the
commit ID, in that case you can use -c|--commit.
> thanks
> -- PMM
>
>
Please let me know if any of these points helps.
Cheers,
- Cleber.
