From: Tom Rini <trini@konsulko.com>
To: Joel Stanley <joel@jms.id.au>
Cc: "Eugen Hristev" <eugen.hristev@linaro.org>,
"open list" <u-boot@lists.denx.de>,
"Simon Glass" <sjg@chromium.org>,
"Cédric Le Goater" <clg@kaod.org>,
"Andrew Jeffery" <andrew@codeconstruct.com.au>
Subject: Re: Gitlab runner timeout on evb-ast2600 ?
Date: Thu, 10 Apr 2025 17:14:44 -0600 [thread overview]
Message-ID: <20250410231444.GK5495@bill-the-cat> (raw)
In-Reply-To: <CACPK8XeCDU+-6+zzJe4=uj=Lduh8nGx6pNr=yWCsM+k-rov2UQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 985 bytes --]
On Fri, Apr 11, 2025 at 08:07:15AM +0930, Joel Stanley wrote:
> On Mon, 7 Apr 2025 at 23:25, Eugen Hristev <eugen.hristev@linaro.org> wrote:
> >
> > Hi everyone,
> >
> > I keep getting an error on running the CI loop on -next on my tree :
> >
> > https://source.denx.de/u-boot/custodians/u-boot-at91/-/jobs/1090517
>
> Thanks for the report.
>
> >
> > ! _pytest.outcomes.Exit: Lab timeout: Marking connection bad - no other
> > tests will run !
> >
> > Any clue ? It's been like this for few days. It doesn't look like a
> > faulty patch.
>
> I can't see that link you sent me, it 403s.
>
> Do you have any other traces or information to share?
It's been intermittent recently. I was able to put qemu + gdb together
and see it's one of the early initcalls that fails and hang()s but
didn't see why. You should be able to use commit 1f0281294d8b ("Merge
patch series "Annotate switch/case fallthrough cases"") as a starting
point of failure.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2025-04-10 23:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-07 13:55 Gitlab runner timeout on evb-ast2600 ? Eugen Hristev
2025-04-07 14:01 ` Tom Rini
2025-04-10 22:37 ` Joel Stanley
2025-04-10 23:14 ` Tom Rini [this message]
2025-04-11 7:23 ` Cédric Le Goater
2025-04-11 7:56 ` Joel Stanley
2025-04-11 15:05 ` Tom Rini
2025-04-11 15:01 ` Tom Rini
2025-04-11 15:26 ` Cédric Le Goater
2025-04-11 16:42 ` Tom Rini
2025-04-11 16:59 ` Tom Rini
2025-04-15 7:12 ` Cédric Le Goater
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=20250410231444.GK5495@bill-the-cat \
--to=trini@konsulko.com \
--cc=andrew@codeconstruct.com.au \
--cc=clg@kaod.org \
--cc=eugen.hristev@linaro.org \
--cc=joel@jms.id.au \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.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 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.