Re: Gitlab runner timeout on evb-ast2600 ?

[Tom Rini <trini@konsulko.com>]

[-- Attachment #1: Type: text/plain, Size: 2705 bytes --]

On Fri, Apr 11, 2025 at 05:26:49PM +0930, Joel Stanley wrote:
> On Fri, 11 Apr 2025 at 16:54, Cédric Le Goater <clg@kaod.org> wrote:
> >
> > Hi,
> >
> > On 4/11/25 01:14, Tom Rini wrote:
> > > 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.
> > >
> >
> > Do you have logs ?
> >
> > Things look ok from the QEMU side (latest 10.0.0-rc and 9.1) :
> 
> I brefily tried to run the steps from CI locally, but couldn't work
> out how to get the flash image built. Instead I used the instructions
> from 154cffa16a7b6647e180ed6cef55342b39580aff.

It's a bit of abstractions, sorry. It's this:
https://source.denx.de/u-boot/u-boot-test-hooks/-/blob/master/bin/flash.qemu_gen_padded_image?ref_type=heads
with variables filled from:
https://source.denx.de/u-boot/u-boot-test-hooks/-/blob/master/bin/travis-ci/conf.evb-ast2600_qemu?ref_type=heads

> Testing master with Debian's qemu 9.2.2:
> 
> makearm evb-ast2600_defconfig
> make u-boot-with-spl.bin
> truncate -s 64M u-boot-with-spl.bin
> qemu-system-arm -nographic -M ast2600-evb \
>         -drive file=u-boot-with-spl.bin,if=mtd,format=raw
> 
> 
> U-Boot SPL 2025.04-00921-gcb7555e93075 (Apr 11 2025 - 17:05:20 +0930)
> Trying to boot from RAM
> ## Checking hash(es) for config conf-1 ... OK
> ## Checking hash(es) for Image firmware-1 ... crc32+ OK
> ## Checking hash(es) for Image fdt-1 ... crc32+ OK
> 
> 
> U-Boot 2025.04-00921-gcb7555e93075 (Apr 11 2025 - 17:05:20 +0930)

Just please note I don't know if this rev of U-Boot was a failing one,
or not. That's part of the challenge here is seemingly arbitrary changes
lead to this platform passing/failing.

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]