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
Daanct12 has joined #yocto
mjm has quit [Quit: mjm]
davidinux has quit [Ping timeout: 252 seconds]
davidinux has joined #yocto
Emantor has quit [Quit: ZNC - http://znc.in]
Emantor has joined #yocto
ablu has quit [Ping timeout: 260 seconds]
alejandrohs has quit [Ping timeout: 260 seconds]
jclsn has quit [Ping timeout: 245 seconds]
jclsn has joined #yocto
ablu has joined #yocto
gspbirel56 has quit [Ping timeout: 248 seconds]
goliath has quit [Quit: SIGSEGV]
merit has quit [Remote host closed the connection]
Minvera has quit [Ping timeout: 245 seconds]
GNUmoon has quit [Remote host closed the connection]
GNUmoon has joined #yocto
Xagen has quit [Ping timeout: 260 seconds]
Xagen has joined #yocto
Wouter01002 has quit [Quit: The Lounge - https://thelounge.chat]
Wouter01002 has joined #yocto
warthog9 has quit [Ping timeout: 252 seconds]
warthog9 has joined #yocto
gspbirel56 has joined #yocto
merit has joined #yocto
roussinm has quit [Ping timeout: 252 seconds]
amitk has joined #yocto
dkc_ has quit [Read error: Connection reset by peer]
dkc has joined #yocto
tec has quit [Quit: bye!]
tec has joined #yocto
Ad0 has quit [Ping timeout: 276 seconds]
Ad0 has joined #yocto
Haxxa has quit [Ping timeout: 252 seconds]
Haxxa has joined #yocto
Haxxa has quit [Excess Flood]
Haxxa has joined #yocto
Haxxa has quit [Excess Flood]
Haxxa has joined #yocto
Wouter01002 has quit [Quit: The Lounge - https://thelounge.chat]
Wouter01002 has joined #yocto
roussinm has joined #yocto
Daanct12 has quit [Quit: WeeChat 4.4.2]
roussinm has quit [Quit: WeeChat 3.3-dev]
florian has joined #yocto
prabhakalad has quit [Quit: Konversation terminated!]
prabhakalad has joined #yocto
Saur_Home84 has joined #yocto
Saur_Home48 has quit [Ping timeout: 256 seconds]
Saur_Home68 has joined #yocto
florian has quit [Ping timeout: 252 seconds]
Saur_Home84 has quit [Ping timeout: 256 seconds]
xmn has quit [Ping timeout: 248 seconds]
goliath has joined #yocto
dl9pf has quit [Quit: Connection closed for inactivity]
thomas25 has joined #yocto
<thomas25> I've enabled Shared State Cache for my yocto builds and I'm following the official documentation and doing the same stuff but still looks like not much is pulled from SSC, instead almost all is being built, is that normal?
<thomas25> building on crops/poky:ubuntu-22.04 container on macos host
Guest65 has joined #yocto
<Guest65> strange problem flashing an orin nx 16gb : the root filesystem on the nvme is not refreshed, examined all I could think of but to no avail
<Scorpi> thomas25: bitbake -S printdiff <recipe> might help
<thomas25> Scorpi ok, this is hello world yocto for me, so I printed tasks for given target via `bitbake -g` now I'm troubleshooting for a random target in there via `bitbake -S printdiff <recipe>`
<thomas25> btw, am i right to expect to get most of the objects from cache server if i target yocto 5.0.4 on crops/poky:ubuntu-22 image? i.e. i'm guess a popular target with a popular dev container
<thomas25> as for target arch, i've tried aarch64 and x64 both require a lot of build (i was expecting the opposite)
Saur_Home21 has joined #yocto
brgl has quit [Quit: The Lounge - https://thelounge.chat]
jetm has quit [Quit: ZNC 1.8.1 - https://znc.in]
ablu-linaro has quit [Quit: ZNC 1.8.1 - https://znc.in]
Saur_Home68 has quit [Ping timeout: 256 seconds]
ablu-linaro has joined #yocto
brgl has joined #yocto
jetm has joined #yocto
amitk has quit [Remote host closed the connection]
davidinux has quit [Ping timeout: 255 seconds]
Saur_Home57 has joined #yocto
Guest65 has quit [Quit: Client closed]
Saur_Home21 has quit [Ping timeout: 256 seconds]
dl9pf has joined #yocto
xmn has joined #yocto
Saur_Home34 has joined #yocto
Saur_Home57 has quit [Ping timeout: 256 seconds]
<rber|res> @thomas25 - you mean the first time it builds a lot right? If you build the same thing again it does not.
Wouter01002 has quit [Quit: The Lounge - https://thelounge.chat]
Wouter01002 has joined #yocto
dmoseley has quit [Quit: ZNC 1.9.1 - https://znc.in]
Saur_Home60 has joined #yocto
Saur_Home34 has quit [Ping timeout: 256 seconds]
Saur_Home15 has joined #yocto
mrpelotazo has quit [Read error: Connection reset by peer]
Saur_Home60 has quit [Ping timeout: 256 seconds]
mrpelotazo has joined #yocto
Saur_Home21 has joined #yocto
Saur_Home15 has quit [Ping timeout: 256 seconds]
mrpelotazo has quit [Ping timeout: 252 seconds]
mrpelotazo has joined #yocto
Bardon has quit [Ping timeout: 264 seconds]
<thomas25> rber|res yes, but, isn't there a remote shared artifact cache server? it's what i understand from the docs and the local.conf ?
<thomas25> it also sounds weirds because who are eligible to store cache information? how is it trusted? etc
druppy has joined #yocto
<rber|res> I am not sure it's up and running yet.
aduskett has quit [Ping timeout: 246 seconds]
aduskett has joined #yocto
druppy has quit [Ping timeout: 255 seconds]
<thomas25> I mean, isn't this a public shared build artefact server SSTATE_MIRRORS ?= "file://.* http://cdn.jsdelivr.net/yocto/sstate/all/PATH;downloadfilename=PATH"
dmoseley has joined #yocto
amitk has joined #yocto
Bardon has joined #yocto
Bardon_ has joined #yocto
Bardon has quit [Ping timeout: 244 seconds]
Bardon_ has quit [Ping timeout: 255 seconds]
xmn has quit [Ping timeout: 260 seconds]
Bardon has joined #yocto
<rber|res> do you set PRSERV_UPSTREAM?
Bardon has quit [Ping timeout: 246 seconds]
Bardon has joined #yocto
davidinux has joined #yocto
Ad0 has quit [Ping timeout: 252 seconds]
Ad0 has joined #yocto
aduskett has quit [Quit: Konversation terminated!]
warthog9 has quit [Ping timeout: 252 seconds]
warthog9 has joined #yocto
Bardon_ has joined #yocto
Bardon has quit [Ping timeout: 252 seconds]
rber|res has quit [Remote host closed the connection]
rber|res has joined #yocto
Bardon has joined #yocto
Guest-fermion has joined #yocto
Bardon_ has quit [Ping timeout: 252 seconds]
Bardon_ has joined #yocto
Bardon has quit [Ping timeout: 252 seconds]
Bardon_ has quit [Ping timeout: 246 seconds]
joaohf has joined #yocto
joaohf has quit [Changing host]
joaohf has joined #yocto
Bardon has joined #yocto
florian has joined #yocto
amitk has quit [Ping timeout: 265 seconds]
reatmon_ has quit [Remote host closed the connection]
reatmon_ has joined #yocto
Bardon_ has joined #yocto
Bardon has quit [Ping timeout: 276 seconds]
Bardon_ has quit [Ping timeout: 252 seconds]
Bardon has joined #yocto
Bardon_ has joined #yocto
Bardon has quit [Ping timeout: 264 seconds]
Bardon_ has quit [Ping timeout: 276 seconds]
Bardon has joined #yocto
<RP> mcfrisk_: https://valkyrie.yoctoproject.org//#/builders/23/builds/246/steps/14/logs/stdio - I wonder if this is the same issue the barebox patches ran into and we need to disable kvm on arm ?
Bardon_ has joined #yocto
Bardon has quit [Ping timeout: 246 seconds]
Bardon has joined #yocto
Bardon_ has quit [Ping timeout: 265 seconds]
olani- has joined #yocto
Wouter01002 has quit [Quit: The Lounge - https://thelounge.chat]
Wouter01002 has joined #yocto
gspbirel56 has quit [Ping timeout: 252 seconds]
Guest-fermion has quit [Ping timeout: 256 seconds]
olani- has quit [Ping timeout: 252 seconds]
florian has quit [Ping timeout: 252 seconds]