Tartarus changed the topic of #u-boot to: SOURCE MOVED TO https://source.denx.de/u-boot/u-boot.git / U-Boot v2023.04, v2023.07-rc2 are OUT / Merge Window is CLOSED, next branch is OPEN / Release v2023.07 is scheduled for 03 July 2023 / Channel archives at https://libera.irclog.whitequark.org/u-boot
teejay has quit [Ping timeout: 240 seconds]
teejay has joined #u-boot
apritzel_ has quit [Ping timeout: 240 seconds]
pgreco has joined #u-boot
pgreco_ has quit [Ping timeout: 240 seconds]
thopiekar_ has quit [Ping timeout: 268 seconds]
thopiekar has joined #u-boot
<rfs613> marex: for the "unknwon document" warning, even after removing the .rst suffix, and the extranous back-quote, it still doesn't build.
<marex> rfs613: hm ?
<rfs613> I'm thinking that links outside of the doc/ subdirectory might not be possible
<marex> sjg1: ^
<rfs613> marex: working on dumpimage failure right now, but I cribbed that from mtk_image.c, so I suspect it would have the same issue. Any idea if the testsuite covers that?
<marex> rfs613: hold on
<marex> tools/binman/ftest.py: out = tools.run('dumpimage', '-l', fname)
<marex> maybe ?
<rfs613> yep that's what I'm using to test it... wondering if those gitlab pipelines are exercising that same 'dumpimage -l <name>' on other formats such as mkt_image ?
<marex> rfs613: try it locally on that fit_data.fit
<marex> maybe when you added new format, the autodetection of formats got broken
<rfs613> marex: ah, the check_image_types, yes this was brought up loooong ago in a code review, and I was told I didn't need it... but seems that we in fact do!
<rfs613> okay so i have that fixed
<rfs613> and the mtk_image.c does indeed have the same problem
<rfs613> well actually I am not 100% sure as I don't have a valid mtk image for testing with
<marex> I think you can build some arm mtk board to find out, but , separate patch please
<rfs613> indeed and maybe not tonight ;-)
<marex> so we have like 1 outstanding issue ?
<rfs613> just the htmldocs warning (which is treated as an error).
<rfs613> I think I either drop that link, or use a https:// link to readthedocs. Thoughts?
<marex> rfs613: the former, unless sjg1 can provide a better hint
<marex> RTD link does not work for people who do local rendering
<rfs613> true. But I tested liniking to ../../index , which points to u-boot/doc/index.rst, that works fine.
<rfs613> then i copied index.rst one level higher up, and linked to ../../index -> doesn't work
<rfs613> so it seems it won't allow links outside of doc subdir
thopiekar has quit [Ping timeout: 240 seconds]
<marex> rfs613: common/spl/Kconfig.vpl: See tools/binman/binman.rst for a detailed explanation.
<marex> rfs613: so yeah, I think the RTD docs are generated only from doc/
thopiekar has joined #u-boot
<rfs613> ah sure, that works for me
<rfs613> right, so both fixes done, series bumped to v7.. what else am I forgetting?
<marex> I think that's it
WoC has quit [Remote host closed the connection]
<marex> rfs613: ping me when you have it, then I can push it into the CI again
<rfs613> marex: just tweaking the cover letter, will be posted in a few moments.
camus has quit [Remote host closed the connection]
WoC has joined #u-boot
<rfs613> marex: it's sent now
<marex> rfs613: did you forget to collect RB tags from v5 and v5.2 ?
<rfs613> marex: I should have them all.. let me check again...
WoC has quit [Remote host closed the connection]
WoC has joined #u-boot
<rfs613> marex: okay there are three from you missing... 5/10, 7/10 and 8/10
<marex> yeah
WoC has quit [Remote host closed the connection]
camus has joined #u-boot
WoC has joined #u-boot
WoC has quit [Remote host closed the connection]
WoC has joined #u-boot
<marex> sjg1: xypron: ^
<rfs613> marex: hmm, that failure doesn't seem like it is rz/n1 related... no efi and no e1000... am I missing something?
WoC has quit [Remote host closed the connection]
<marex> likely something with the lab
Leopold_ has joined #u-boot
WoC has joined #u-boot
<rfs613> marex: do we need a v8 with the RB tags? i'm going to call it a night fairly soon
Leopold has quit [Ping timeout: 240 seconds]
<marex> rfs613: no, I sent them again
<marex> rfs613: https://source.denx.de/u-boot/custodians/u-boot-sh/-/pipelines/16351 the final builds might take a bit longer
<rfs613> marex: ok. Seems like that qemu-x86 job passed this time around
<marex> yes
<marex> now for the bulk builds, something might still surface
<marex> but those take a while
<rfs613> ok, thanks, i'll check back tomorrow...
thopiekar has quit [Ping timeout: 268 seconds]
thopiekar_ has joined #u-boot
macromorgan has quit [Read error: Connection reset by peer]
macromorgan has joined #u-boot
camus has quit [Ping timeout: 268 seconds]
camus has joined #u-boot
WoC has quit [Remote host closed the connection]
macromorgan has quit [Ping timeout: 240 seconds]
macromorgan has joined #u-boot
macromorgan has quit [Ping timeout: 256 seconds]
macromorgan has joined #u-boot
persmule has quit [Remote host closed the connection]
cryptonix has joined #u-boot
rvalue has quit [Ping timeout: 265 seconds]
rvalue has joined #u-boot
cryptonix has quit [Ping timeout: 240 seconds]
Wouter0100670440 has quit [Quit: The Lounge - https://thelounge.chat]
Wouter0100670440 has joined #u-boot
rfs613 has quit [Ping timeout: 264 seconds]
rfs613 has joined #u-boot
apritzel_ has joined #u-boot
Wouter0100670440 has quit [Quit: The Lounge - https://thelounge.chat]
Wouter0100670440 has joined #u-boot
apritzel_ has quit [Ping timeout: 240 seconds]
jag has joined #u-boot
WoC has joined #u-boot
runcom has joined #u-boot
runcom has quit [Ping timeout: 240 seconds]
vagrantc has quit [Quit: leaving]
___nick___ has joined #u-boot
camus has quit [Quit: camus]
mmu_man has joined #u-boot
___nick___ has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
___nick___ has joined #u-boot
___nick___ has quit [Client Quit]
___nick___ has joined #u-boot
mmu_man has quit [Ping timeout: 268 seconds]
runcom has joined #u-boot
<xypron> marex: e1000_reset() failing seems not be related to EFI. I would simply retry the job.
runcom has quit [Ping timeout: 240 seconds]
goliath has joined #u-boot
apritzel_ has joined #u-boot
rvalue has quit [Read error: Connection reset by peer]
rvalue has joined #u-boot
hanetzer has quit [Ping timeout: 256 seconds]
hanetzer has joined #u-boot
apritzel_ has quit [Ping timeout: 240 seconds]
mmu_man has joined #u-boot
runcom has joined #u-boot
runcom has quit [Ping timeout: 240 seconds]
mmu_man has quit [Ping timeout: 264 seconds]
mmu_man has joined #u-boot
mmu_man has quit [Ping timeout: 265 seconds]
mmu_man has joined #u-boot
ilunev has joined #u-boot
runcom has joined #u-boot
runcom has quit [Ping timeout: 240 seconds]
Wouter0100670440 has quit [Quit: The Lounge - https://thelounge.chat]
Wouter0100670440 has joined #u-boot
<marex> xypron: it shouldnt be failing in CI, right ?
<rfs613> marex: looks like pipeline 16351 passed (unlike my internet which dropped again last night...)
<xypron> marex: sure
stipa_ has joined #u-boot
stipa has quit [Ping timeout: 240 seconds]
stipa_ is now known as stipa
<Tartarus> A few of the QEMU jobs feel more fragile than they used to
<Tartarus> But I'm not sure if it's host problems, or code changes introducing races
<Tartarus> Sadly if any of the first two stages fail for non-obvious reasons (which they do, sometimes) hitting retry is always the first step
<xypron> Tartarus: https://source.denx.de/u-boot/custodians/u-boot-efi/-/jobs/628423 showed the same error on the same runner: #110 (wgFtTy4zM) kaka
<xypron> When repeated on a different runner the problem does not show up.
<xypron> Tartarus: is it possible to show a list of failed jobs per runner?
<xypron> https://source.denx.de/u-boot/u-boot/-/jobs/627404 - #110 (wgFtTy4zM) kaka DHCP again
<xypron> https://source.denx.de/u-boot/u-boot/-/jobs/624054 - #110 (wgFtTy4zM) kaka DHCP failure
<xypron> https://source.denx.de/u-boot/u-boot/-/jobs/625157 - #110 (wgFtTy4zM) kaka DHCP failure
<xypron> Tartarus: what is special about this runner?
<xypron> Tartarus: the return code -E1000_ERR_TIMEOUT indicates that the link negotiation took more than 80 seconds.
WoC has quit [Remote host closed the connection]
WoC has joined #u-boot
apritzel_ has joined #u-boot
persmule has joined #u-boot
goliath has quit [Quit: SIGSEGV]
hanetzer has quit [Ping timeout: 240 seconds]
runcom has joined #u-boot
hanetzer has joined #u-boot
runcom has quit [Ping timeout: 240 seconds]
runcom has joined #u-boot
apritzel_ has quit [Ping timeout: 256 seconds]
<Tartarus> I think all that's special about kaka is that, ahem it sometimes is https://www.urbandictionary.com/define.php?term=Kaka :( I don't know if it's a memory issue or just overloaded sometimes or what
runcom has quit [Ping timeout: 250 seconds]
runcom has joined #u-boot
runcom has quit [Ping timeout: 240 seconds]
ilunev has quit [Quit: Textual IRC Client: www.textualapp.com]
mmu_man has quit [Ping timeout: 256 seconds]
wkawka has joined #u-boot
apritzel_ has joined #u-boot
___nick___ has quit [Ping timeout: 240 seconds]
runcom has joined #u-boot
<marex> rfs613: PR is out, thanks !
<marex> rfs613: and, again, sorry for the abysmal delays
wkawka has quit [Quit: Client closed]
mmu_man has joined #u-boot
runcom has quit [Ping timeout: 240 seconds]
mmu_man has quit [Ping timeout: 268 seconds]
ikarso has joined #u-boot
mmu_man has joined #u-boot
goliath has joined #u-boot
kettenis has quit [Ping timeout: 240 seconds]
kettenis has joined #u-boot
Wouter0100670440 has quit [Quit: The Lounge - https://thelounge.chat]
Wouter0100670440 has joined #u-boot
mmu_man has quit [Ping timeout: 264 seconds]
mmu_man has joined #u-boot
ikarso has quit [Quit: Connection closed for inactivity]
mmu_man has quit [Ping timeout: 264 seconds]