lquirion has quit [Remote host closed the connection]
lquirion has joined #yocto
alperak has joined #yocto
frieder has quit [Ping timeout: 260 seconds]
_whitelogger has joined #yocto
MrCryo has joined #yocto
florian_kc has joined #yocto
lquirion has quit [Remote host closed the connection]
lquirion has joined #yocto
mbulut has joined #yocto
mbulut has quit [Client Quit]
mkazantsev has joined #yocto
Jones42__ has joined #yocto
mvlad has joined #yocto
Jones42_ has quit [Ping timeout: 264 seconds]
florian__ has joined #yocto
Jones42__ has quit [Ping timeout: 268 seconds]
Saur_Home86 has quit [Quit: Client closed]
Saur_Home86 has joined #yocto
ptsneves has joined #yocto
ehussain has joined #yocto
Kubu_work1 has quit [Read error: Connection reset by peer]
florian_kc is now known as florian
frieder has quit [Ping timeout: 252 seconds]
frieder has joined #yocto
mihai has quit [Quit: Leaving]
tnovotny_ has joined #yocto
tnovotny has quit [Ping timeout: 252 seconds]
<lquirion>
@Guest13 I think that the .manifest file generated by Yocto covers your needs
enok has joined #yocto
<JaMa>
anyone seeing "error[E0464]: multiple candidates for `rmeta` dependency `core` found" for various dependencies in rust recipes (after the update from yesterday), libstd-rs now provides multiple versions in incremental build (unless you explicitly rebuild from scratch after -c cleansstate) kanavin_ have you seen this before?
<JaMa>
buildhistory-diff -p buildhistory
<JaMa>
packages/raspberrypi4_64-webos-linux/libstd-rs/libstd-rs-dev: PKGSIZE changed from 304061571 to 160359626 (-47%)
<kanavin_>
JaMa, incremental builds in rust are broken
<JaMa>
ok, haven't seen this one before, so I guess I was lucky, thanks
Saur_Home86 has quit [Quit: Client closed]
Saur_Home86 has joined #yocto
manuel1985 has joined #yocto
mkazantsev has quit [Remote host closed the connection]
<RP>
kanavin_: do we know what isn't cleaned properly in the rust builds?
rob_w has quit [Remote host closed the connection]
<kanavin_>
RP: I'm not sure. If JaMa can provide a reproducer I can take a look.
Saur_Home63 has joined #yocto
Saur_Home86 has quit [Ping timeout: 250 seconds]
<JaMa>
in my case today it was libstd-rs (I had to cleansstate all its users as well after rebuilding it, but the culprint was duplicated files installed and staged by libstd-rs)
<RP>
I've seen this kind of issue before but couldn't reproduce it :/
Kubu_work has joined #yocto
<JaMa>
I'll try, because I'm pretty sure I've built libstd-rs from scratch yesterday and today it was rebuilt because of the last 4 commits currently in master (so I guess if I checkout HEAD~5, build libstd-rs, checkout master, build it again than I might see the issue)
tnovotny has joined #yocto
frieder has quit [Ping timeout: 260 seconds]
tnovotny_ has quit [Ping timeout: 240 seconds]
ehussain has quit [Quit: ehussain]
lexano has joined #yocto
enok has quit [Ping timeout: 240 seconds]
<JaMa>
hmm this trivial reproducer didn't work
frieder has joined #yocto
<JaMa>
libstd-rs-1.75.0-r0 was rebuilt from do_fetch after updating oe-core (and cleaning dirs while doing so)
Hammdist has quit [Quit: leaving]
<RP>
JaMa: sounds like what I ran into last time :/
Guest13 has quit [Ping timeout: 250 seconds]
frieder has quit [Ping timeout: 260 seconds]
* RP
doesn't know the best way to try and fix/improve the cached unihash esdk problem :(
* RP
keeps going around in circles on the right thing to do
enok has joined #yocto
frieder has joined #yocto
xmn has joined #yocto
alessioigor has quit [Quit: Client closed]
<zeddii>
JaMa: fyi. my first round of tested fixes are no master-next of m-virt as of a minute ago
ptsneves has quit [Remote host closed the connection]
ptsneves1 has joined #yocto
ptsneves1 is now known as ptsneves
alessioigor has joined #yocto
tnovotny has quit [Quit: Leaving]
frieder has quit [Remote host closed the connection]
ctraven has quit [Quit: Lost terminal]
dgriego has quit [Quit: Computer going to sleep]
dgriego has joined #yocto
enok has quit [Read error: Connection reset by peer]
enok has joined #yocto
<JaMa>
zeddii: thanks, will add that to my world builds
<JPEW>
RP: Good news! The patch to do batch processing of queries for the hash server is actually simpler than I though; it's just on the client side and pretty isolated in bitbake so, backports should be pretty easy
<JPEW>
Patches will be sent today
* JPEW
didn't have to break the server for once :)
<smurray>
sakoman: okay, I'll need to rebase our local change
<sakoman>
smurray: It will be in the patchset that I send out for review in the next day or so, so won'
florian__ has joined #yocto
<sakoman>
t merge until early next week
<smurray>
sakoman: okay. We just finished a bump to 5.0.1, I'll likely have to do an interim bump on our side to pick that up when it gets merged to scarthgap
<JaMa>
khem: is spirv-llvm-translator building for you after last few fixes? I still see failures with gcc
simonew has quit [Remote host closed the connection]
simonew has joined #yocto
lquirion has joined #yocto
lquirion has quit [Ping timeout: 255 seconds]
florian__ has joined #yocto
tlwoerner has quit [Remote host closed the connection]
tlwoerner has joined #yocto
ecdhe has quit [Read error: Connection reset by peer]
<JPEW>
RP: Can you clarify "not past init"?
<RP>
JPEW: I mean that with the batched queries, the build ran and died before the other one without the batched queries had even started executing tasks
manuel1985 has quit [Quit: Leaving]
<JPEW>
Oh, well that's promising that it's faster at least
<JPEW>
RP: Sent a V2... I couldn't see any logic bugs, but tried to handle a corner case anyway. If this still has problems, we might need to look at the server side
Notgnoshi has quit [Ping timeout: 252 seconds]
Notgnoshi has joined #yocto
<JPEW>
RP: Sent a server patch that will helpful if we are maxing out the server CPU
alperak has quit [Quit: Connection closed for inactivity]
<RP>
halstead: you might want to look at the above!
zwelch has quit [Remote host closed the connection]
<RP>
JPEW: thanks! I'll try another test
<JaMa>
khem: yes this is the latest meta-clang (5397003 libclc: Fix build errors)
zwelch has joined #yocto
<halstead>
RP: JPEW Thank you. Is this ready for testing? I have a test spot.
<JPEW>
halstead: No need to update the server for this test. The new change to the server adds support for SO_REUSEPORT so you can run multiple servers on the same port to take advantage of multiple CPUs. I don't _think_ we need it yet
<JPEW>
(unless you want to try it preemptively of course)
enok has quit [Read error: Connection reset by peer]
enok has joined #yocto
<JaMa>
khem: sending PR
vermaete has joined #yocto
<vermaete>
If I would like to add ptest to python3-flask and it runs just below 60sec at qemux86. Where should I add the test?
<vermaete>
in ptest-packagelists.inc
<vermaete>
Slow I assume? Or do I leave this to the maintainers?
<vermaete>
ok, found it: not! because it's in different layers.
mvlad has quit [Remote host closed the connection]
rfs613 has quit [Remote host closed the connection]
<JPEW>
RP: Ok, I was able to reproduce that one and fix it. V3 sent
rfs613 has joined #yocto
enok has quit [Ping timeout: 240 seconds]
<RP>
JPEW: thanks, trying another test build
<JPEW>
RP: I'm wondering if this makes the client pool (parallel code) unnecessary and we should remove it.... maybe something to think about
<JPEW>
This is way better, and probably nicer to the server :)
<RP>
JPEW: I was wondering about that too. The speed improvements should make it unneeded. It also makes my runqueue changes I can't get working obsolete too which is probably for the btest
<JPEW>
Ya
Saur_Home63 has quit [Quit: Client closed]
Saur_Home63 has joined #yocto
florian__ has quit [Ping timeout: 268 seconds]
<RP>
JPEW: currently the parallel code doesn't work so we can't use it. Removing it may be the better option
<RP>
JPEW: completed the image build in around 10 mins :)
<RP>
JPEW: I think the issue is what I was wondering about but I still don't quite understand the async code :/
<RP>
I guess a failure and reconnect is handled somewhere else I'm not quite seeing, its the missing exception handling I'm missing
Saur_Home63 has quit [Quit: Client closed]
Saur_Home63 has joined #yocto
<JPEW>
Ya, it tries to reconnect pretty aggressively, which is normally fine, except when you are trying to track multiple commands with their results
<JPEW>
State tracking was off a little bit; it was pulling a message, sending it, then adding it to the pending list. Need to add it to the pending list before trying to send in case it reconnects
<RP>
That makes sense
<RP>
JPEW: I'll see how this looks in the morning. Some meta-* failures are expected, the rest should pass
<RP>
JPEW: thanks again, this should make a huge difference to the builds