LetoThe2nd changed the topic of #yocto to: Welcome to the Yocto Project | Learn more: https://www.yoctoproject.org | Community: https://www.yoctoproject.org/community | IRC logs: http://irc.yoctoproject.org/irc/ | Having difficulty on the list, with someone on the list or on IRC, contact Yocto Project Community Manager Letothe2nd | CoC: https://www.yoctoproject.org/community/code-of-conduct
Danct12 has quit [Quit: ZNC 1.9.1 - https://znc.in]
Danct12 has joined #yocto
Daanct12 has joined #yocto
Danct12 has quit [Killed (NickServ (GHOST command used by Daanct12))]
Daanct12 is now known as Danct12
Danct12 has quit [Quit: ZNC 1.9.1 - https://znc.in]
Danct12 has joined #yocto
vthor has quit [Quit: kill -9 $pid]
vthor has joined #yocto
vthor has quit [Changing host]
vthor has joined #yocto
druppy has joined #yocto
druppy has quit [Quit: druppy]
druppy has joined #yocto
josuedhg has joined #yocto
rcwoolley has joined #yocto
bjdooks has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
bjdooks has joined #yocto
josuedhg has quit [Ping timeout: 240 seconds]
<Ch^W> Yup... confirmed... EdgeOS is, and as far as I can tell always has been, Debian based. TIL...
<Ch^W> Given all the work they did to hack in Vyatta... it feels like an odd choice.
<Ch^W> RP: I should be able to do a deep dive on the setup tools stuff, but not until after OSSNA in June. Not sure how the fits with scheduling, but that is the best I can do at the moment.
bjdooks has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
sudip_ has quit [Quit: ZNC - http://znc.in]
sudip has joined #yocto
bjdooks has joined #yocto
reatmon_ has quit [Remote host closed the connection]
rcwoolley has quit [Ping timeout: 240 seconds]
<RP> Ch^W: I'd love to think I'd have it resolved by then but we'll see...
* RP will take help where/when he can
ello_ has quit [Read error: Connection reset by peer]
ello has quit [Read error: Connection reset by peer]
ello has joined #yocto
<khem> RP: I am seeing one reproduciblility failure with clang merge - https://autobuilder.yoctoproject.org/valkyrie/api/v2/logs/2145966/raw_inline
ello_ has joined #yocto
<khem> openmp-src is built with one of clang runtime recipes, is there an easy way for me to look into data to see what could have changed in the package between two runs ?
<khem> basically diffoscope output
<RP> khem: if you look at the logs you'll see an path with a url in it
<RP> valkyrie.yocto.io/pub/repro-fail/oe-reproducible-20250423-7uds3lh5
<RP> khem: that is diffoscope output
<khem> ah yes I see there now thanks
<khem> yeah I see there is a date embedded in there with one of generated files
Chaser has joined #yocto
<RP> khem: that looks to be the issue
<khem> RP: I have another issue in nativesdk-clang to fix and then we are good with a-quick
goliath has quit [Quit: SIGSEGV]
<RP> khem: sounds good. I've not looked at those patches yet. Struggling with 5.2 :/
florian_kc has joined #yocto
Jones42 has quit [Ping timeout: 252 seconds]
Kubu_work has joined #yocto
<tgamblin> how does one adjust the size of /var/volatile in a Yocto image? I'm building core-image-minimal and there's only 4.0K available. Is this possible to configure in local.conf?
druppy has quit [Ping timeout: 265 seconds]
* tgamblin wonders if this is even something he wants to do
wmills_ has quit [Remote host closed the connection]
wmills_ has joined #yocto
fullstop has quit [Quit: ZNC - http://znc.in]
fullstop has joined #yocto
<rburton> tgamblin: its a tmpfs isn't it?
fullstop has quit [Quit: ZNC - http://znc.in]
<tgamblin> rburton: what I'm trying to do ultimately is fix the numpy ptests, but it looks like ~100 (or somewhere south of that many) ptests are trying to write to files... but since that's happening in /var/volatile/tmp, there's not enough space
goliath has joined #yocto
<rburton> ah fun, probably following a link from /tmp
<rburton> try creating a temporary directory under cwd and redirecting TMPDIR, if it respects that
<tgamblin> rburton: thanks, will try it
<rburton> also fwiw core-image-ptest adds a lot more space to the rootfs for this reason
<rburton> and you can bitbake core-image-ptest-python3-numpy to get an image with just the numpy tests in
<tgamblin> rburton: right
<tgamblin> rburton: looks like it just ends up using 2G of storage created. core-image-ptest.bb suggests that there's a functional upper limit for the image size, so I'm not sure if specifying a much larger IMAGE_ROOTFS_EXTRA_SPACE in there for python3-numpy?
zeemate has joined #yocto
fullstop has joined #yocto
fullstop has quit [Quit: ZNC - http://znc.in]
fullstop has joined #yocto
ello has quit [Quit: ZNC 1.9.1 - https://znc.in]
ello_ has quit [Read error: Connection reset by peer]
ello has joined #yocto
ello_ has joined #yocto
Chaser has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
enok has joined #yocto
cyxae has joined #yocto
cyxae has quit [Remote host closed the connection]
cyxae has joined #yocto
cyxae has quit [Client Quit]
enok has quit [Ping timeout: 245 seconds]
sakoman has quit [Ping timeout: 265 seconds]
sakoman has joined #yocto
druppy has joined #yocto
Kubu_work has quit [Quit: Leaving.]
<rburton> tgamblin: only because it’s trying to fit in specific image type limits. Easily ignored if you use wic images. Surely you don’t need gigabytes?
angrysiamese has left #yocto [#yocto]
sotaoverride_ is now known as sotaoverride
druppy has quit [Ping timeout: 265 seconds]
zeemate has quit [Ping timeout: 272 seconds]
Kubu_work has joined #yocto
florian_kc has quit [Ping timeout: 248 seconds]
sotaoverride is now known as Guest8241