.gitlab-ci.d/base.yml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
The following changes since commit 8967b2fe1b2aaae3c29e207d85fab901d580a2dc:
Merge tag 'pull-9p-20261019' of https://github.com/cschoenebeck/qemu into staging (2026-10-20 07:04:06 +0200)
are available in the Git repository at:
https://gitlab.com/p-b-o/qemu tags/pbouvier/pr/ci_gitlab-20261021
for you to fetch changes up to 3a6d37c9883d21529a01e3615960696f91499153:
ci: add automatic retry (2026-10-21 18:18:33 +0000)
----------------------------------------------------------------
Changes:
- [PATCH] ci: add automatic retry (Pierrick Bouvier <pierrick.bouvier@oss.qualcomm.com>)
Link: https://lore.kernel.org/qemu-devel/20261020231602.24344-1-pierrick.bouvier@oss.qualcomm.com
----------------------------------------------------------------
Pierrick Bouvier (1):
ci: add automatic retry
.gitlab-ci.d/base.yml | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
On 10/21/26 20:19, Pierrick Bouvier wrote: > The following changes since commit 8967b2fe1b2aaae3c29e207d85fab901d580a2dc: > > Merge tag 'pull-9p-20261019' of https://github.com/cschoenebeck/qemu into staging (2026-10-20 07:04:06 +0200) > > are available in the Git repository at: > > https://gitlab.com/p-b-o/qemu tags/pbouvier/pr/ci_gitlab-20261021 > > for you to fetch changes up to 3a6d37c9883d21529a01e3615960696f91499153: > > ci: add automatic retry (2026-10-21 18:18:33 +0000) > > ---------------------------------------------------------------- > Changes: > - [PATCH] ci: add automatic retry (Pierrick Bouvier <pierrick.bouvier@oss.qualcomm.com>) > Link: https://lore.kernel.org/qemu-devel/20261020231602.24344-1-pierrick.bouvier@oss.qualcomm.com > > ---------------------------------------------------------------- > Pierrick Bouvier (1): > ci: add automatic retry > > .gitlab-ci.d/base.yml | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) Applied, thanks. FWIW, the first pipeline containing this was entirely green without intervention, which otherwise has not happened this month. I don't know how (or if it's possible) to see which jobs may have been retried. r~
On 10/22/2026 12:33 AM, Richard Henderson wrote: > On 10/21/26 20:19, Pierrick Bouvier wrote: >> The following changes since commit >> 8967b2fe1b2aaae3c29e207d85fab901d580a2dc: >> >> Merge tag 'pull-9p-20261019' of https://github.com/cschoenebeck/ >> qemu into staging (2026-10-20 07:04:06 +0200) >> >> are available in the Git repository at: >> >> https://gitlab.com/p-b-o/qemu tags/pbouvier/pr/ci_gitlab-20261021 >> >> for you to fetch changes up to 3a6d37c9883d21529a01e3615960696f91499153: >> >> ci: add automatic retry (2026-10-21 18:18:33 +0000) >> >> ---------------------------------------------------------------- >> Changes: >> - [PATCH] ci: add automatic retry (Pierrick Bouvier >> <pierrick.bouvier@oss.qualcomm.com>) >> Link: https://lore.kernel.org/qemu-devel/20261020231602.24344-1- >> pierrick.bouvier@oss.qualcomm.com >> >> ---------------------------------------------------------------- >> Pierrick Bouvier (1): >> ci: add automatic retry >> >> .gitlab-ci.d/base.yml | 3 ++- >> 1 file changed, 2 insertions(+), 1 deletion(-) > > Applied, thanks. > > FWIW, the first pipeline containing this was entirely green without > intervention, which otherwise has not happened this month. I don't know > how (or if it's possible) to see which jobs may have been retried. > That's encouraging. Yes, you can see it from list of "Related jobs" on a pipeline (right of the screen, scroll down). For instance, on this recent pipeline: https://gitlab.com/qemu-project/qemu/-/jobs/17378918262 We can see that build-user failed the first time. Probably it's possible to extract this data using GitLab API is we want to build long term statistics. Regards, Pierrick
On 10/22/2026 10:31 AM, Pierrick Bouvier wrote: > On 10/22/2026 12:33 AM, Richard Henderson wrote: >> On 10/21/26 20:19, Pierrick Bouvier wrote: >>> The following changes since commit >>> 8967b2fe1b2aaae3c29e207d85fab901d580a2dc: >>> >>> Merge tag 'pull-9p-20261019' of https://github.com/cschoenebeck/ >>> qemu into staging (2026-10-20 07:04:06 +0200) >>> >>> are available in the Git repository at: >>> >>> https://gitlab.com/p-b-o/qemu tags/pbouvier/pr/ci_gitlab-20261021 >>> >>> for you to fetch changes up to 3a6d37c9883d21529a01e3615960696f91499153: >>> >>> ci: add automatic retry (2026-10-21 18:18:33 +0000) >>> >>> ---------------------------------------------------------------- >>> Changes: >>> - [PATCH] ci: add automatic retry (Pierrick Bouvier >>> <pierrick.bouvier@oss.qualcomm.com>) >>> Link: https://lore.kernel.org/qemu-devel/20261020231602.24344-1- >>> pierrick.bouvier@oss.qualcomm.com >>> >>> ---------------------------------------------------------------- >>> Pierrick Bouvier (1): >>> ci: add automatic retry >>> >>> .gitlab-ci.d/base.yml | 3 ++- >>> 1 file changed, 2 insertions(+), 1 deletion(-) >> >> Applied, thanks. >> >> FWIW, the first pipeline containing this was entirely green without >> intervention, which otherwise has not happened this month. I don't know >> how (or if it's possible) to see which jobs may have been retried. >> > > That's encouraging. > Yes, you can see it from list of "Related jobs" on a pipeline (right of > the screen, scroll down). > > For instance, on this recent pipeline: > https://gitlab.com/qemu-project/qemu/-/jobs/17378918262 > We can see that build-user failed the first time. > Wrong link. From this pipeline: https://gitlab.com/qemu-project/qemu/-/pipelines/2976077103 Click on any job from build stage, and you'll see the Related jobs on the right side of screen. > Probably it's possible to extract this data using GitLab API is we want > to build long term statistics. > > Regards, > Pierrick
© 2016 - 2026 Red Hat, Inc.