From: Anthony PERARD <anthony.perard@vates.tech>
To: Jan Beulich <jbeulich@suse.com>
Cc: xen-devel@lists.xenproject.org
Subject: Re: xen | Failed pipeline for staging-4.19 | 2d7b6170
Date: Wed, 24 Jul 2024 15:36:44 +0000 [thread overview]
Message-ID: <ZqEfi3WkRTzDqRWi@l14> (raw)
In-Reply-To: <24be503c-7c8a-4db9-aee4-04b0c872c0dc@suse.com>
On Wed, Jul 24, 2024 at 03:18:50PM +0200, Jan Beulich wrote:
> On 24.07.2024 15:15, GitLab wrote:
> >
> >
> > Pipeline #1385987377 has failed!
> >
> > Project: xen ( https://gitlab.com/xen-project/hardware/xen )
> > Branch: staging-4.19 ( https://gitlab.com/xen-project/hardware/xen/-/commits/staging-4.19 )
> >
> > Commit: 2d7b6170 ( https://gitlab.com/xen-project/hardware/xen/-/commit/2d7b6170cc69f8a1a60c52d87ba61f6b1f180132 )
> > Commit Message: hotplug: Restore block-tap phy compatibility (a...
> > Commit Author: Jason Andryuk ( https://gitlab.com/jandryuk-amd )
> > Committed by: Jan Beulich ( https://gitlab.com/jbeulich )
> >
> >
> > Pipeline #1385987377 ( https://gitlab.com/xen-project/hardware/xen/-/pipelines/1385987377 ) triggered by Jan Beulich ( https://gitlab.com/jbeulich )
> > had 3 failed jobs.
> >
> > Job #7415912260 ( https://gitlab.com/xen-project/hardware/xen/-/jobs/7415912260/raw )
> >
> > Stage: test
> > Name: qemu-alpine-x86_64-gcc
>
> This is the one known to fail more often than not, I think, but ...
>
> > Job #7415912175 ( https://gitlab.com/xen-project/hardware/xen/-/jobs/7415912175/raw )
> >
> > Stage: build
> > Name: ubuntu-24.04-x86_64-clang
> > Job #7415912173 ( https://gitlab.com/xen-project/hardware/xen/-/jobs/7415912173/raw )
> >
> > Stage: build
> > Name: ubuntu-22.04-x86_64-gcc
>
> ... for these two I can't spot any failure in the referenced logs. What's going on
> there?
They are crutial information missing in that email, the actual reason
given by gitlab for the failures: "There has been a timeout failure or
the job got stuck." (That message can be seen when going to the url,
removing "/raw" part, and scrolling to the top. Or looking at the side
bar and seen a duration that well above 1h)
Communication between gitlab and the runner might be broken in those
cases, or the runner stop working.
Cheers,
--
Anthony Perard | Vates XCP-ng Developer
XCP-ng & Xen Orchestra - Vates solutions
web: https://vates.tech
next prev parent reply other threads:[~2024-07-24 15:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <66a0fe638f16a_33beeb0103995@gitlab-sidekiq-catchall-v2-96b77f447-9jjmp.mail>
2024-07-24 13:18 ` xen | Failed pipeline for staging-4.19 | 2d7b6170 Jan Beulich
2024-07-24 15:36 ` Anthony PERARD [this message]
2024-07-24 22:21 ` Marek Marczykowski-Górecki
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=ZqEfi3WkRTzDqRWi@l14 \
--to=anthony.perard@vates.tech \
--cc=jbeulich@suse.com \
--cc=xen-devel@lists.xenproject.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.