<JaMa>
RP: any bad memories about top 4 commits in https://git.openembedded.org/bitbake-contrib/log/?h=jansa/1.46-cooker-backports ? It seems to fix parser deadlock I'm seeing quite often with dunfell after parsing exceptions (maybe only the last commit is needed), I'll do more testing and then would like to suggest them to Steve
<RP>
JaMa: I think it may lead to more autobuilder hangs/timeouts due to the hanging writer thread we wait on :/
<RP>
JaMa: but I can understand why they may be a good idea
erbo has joined #yocto
erbo has quit [Client Quit]
erbo has joined #yocto
hpsy has joined #yocto
chezgi has joined #yocto
<chezgi>
hi, is there any resource for stateless yocto?
<chezgi>
for stateless distro, we need clean /etc and /var directories for first time. and all applications must use other places like /usr/etc for initial configs and override user configs from /etc/
<chezgi>
erbo: thanks for suggestion. i have used this sometime ago but it removes some packages like user management from final image.
tnovotny has joined #yocto
chezgi has quit [Ping timeout: 250 seconds]
<erbo>
chezgi: are you sure? I though it only changed how the file system was mounted, and added some extra volatile-binds.
chezgi has joined #yocto
davidinux has joined #yocto
chezgi has quit [Quit: Client closed]
ejoerns[m] has quit [Ping timeout: 244 seconds]
cody has quit [Ping timeout: 244 seconds]
Andrei[m] has quit [Ping timeout: 244 seconds]
jordemort has quit [Ping timeout: 244 seconds]
shoragan[m] has quit [Ping timeout: 268 seconds]
khem has quit [Ping timeout: 272 seconds]
BCMM has joined #yocto
ejoerns[m] has joined #yocto
kanavin has joined #yocto
pidge has joined #yocto
davidinux has quit [Ping timeout: 252 seconds]
davidinux has joined #yocto
tnovotny has quit [Read error: Connection reset by peer]
tnovotny_ has joined #yocto
tnovotny has joined #yocto
tnovotny_ has quit [Ping timeout: 244 seconds]
manuel1985 has quit [*.net *.split]
mranostaj has quit [*.net *.split]
Jari[m] has quit [*.net *.split]
zeddii has quit [*.net *.split]
Emantor has quit [*.net *.split]
Fanfwe has quit [*.net *.split]
marex has quit [*.net *.split]
tnovotny has quit [Read error: Connection reset by peer]
tnovotny has joined #yocto
dev1990 has joined #yocto
mranostaj has joined #yocto
Jari[m] has joined #yocto
zeddii has joined #yocto
marex has joined #yocto
manuel1985 has joined #yocto
Fanfwe has joined #yocto
Emantor has joined #yocto
tnovotny_ has joined #yocto
tnovotny has quit [Ping timeout: 245 seconds]
Fanfwe has quit [Ping timeout: 265 seconds]
Fanfwe has joined #yocto
goliath has joined #yocto
Tazura has joined #yocto
hpsy has quit [Quit: Client closed]
* RP
suspects the lttng-tools ptests are hanging with newer kernels. Is it the kernel upgrade, the lttng-tools upgrade or both though? :(
hpsy has joined #yocto
amitk has joined #yocto
amitk has quit [Client Quit]
amitk has joined #yocto
angolini has joined #yocto
hpsy has quit [Quit: Client closed]
Guest97 has joined #yocto
Andrei[m] has joined #yocto
cody has joined #yocto
hpsy has joined #yocto
Guest97 has quit [Quit: Client closed]
yocton has joined #yocto
pbergin has quit [Quit: Leaving]
troth has joined #yocto
davidinux has quit [Ping timeout: 268 seconds]
rber|res has joined #yocto
davidinux has joined #yocto
Jari[m] has quit [Quit: node-irc says goodbye]
ndec[m] has quit [Quit: node-irc says goodbye]
Emantor[m] has quit [Quit: node-irc says goodbye]
shoragan|m has quit [Quit: node-irc says goodbye]
alex88[m] has quit [Quit: node-irc says goodbye]
ejoerns[m] has quit [Quit: node-irc says goodbye]
AlessandroTaglia has quit [Quit: node-irc says goodbye]
cody has quit [Quit: node-irc says goodbye]
Andrei[m] has quit [Quit: node-irc says goodbye]
Andrei[m] has joined #yocto
troth has quit [Quit: Leaving]
rber|res has quit [Ping timeout: 250 seconds]
troth has joined #yocto
troth_ has joined #yocto
troth_ has quit [Remote host closed the connection]
rber|res6 has joined #yocto
jordemort has joined #yocto
Jari[m] has joined #yocto
ndec[m] has joined #yocto
khem has joined #yocto
Emantor[m] has joined #yocto
shoragan[m] has joined #yocto
ejoerns[m] has joined #yocto
shoragan|m has joined #yocto
alex88[m] has joined #yocto
cody has joined #yocto
AlessandroTaglia has joined #yocto
rber|res6 has quit [Ping timeout: 250 seconds]
rber|res21 has joined #yocto
kayterina[m] has joined #yocto
vmeson has quit [Ping timeout: 272 seconds]
vmeson has joined #yocto
rber|res21 has quit [Ping timeout: 250 seconds]
sakoman has joined #yocto
paulg has joined #yocto
chrfle has joined #yocto
<chrfle>
Hello, I'm inheriting the core-image recipe and want to add signing of the image. My idea was to do this as a postfunc to do_image_complete.. My functions seems to be called, but I can't figure out how to properly get the path to the image file just created. Any advice?
<rber|res>
@dti: Do you need to update all the image if you modify the kernel?
<dti>
no dont need update the image all the time
<rber|res>
@dti: Then you don't need to build the image every time
davidinux has quit [Ping timeout: 268 seconds]
<rber|res>
@dti: You could even build an SDK and do all your kernel hacking without bitbaking and once it's stable add it to your recipes.
<rber|res>
@dti: all this is a question of your workflow
davidinux has joined #yocto
<dti>
ok i will check
<dti>
many thanks
<dti>
rber|res
<rber|res>
@dti: if you tell me your preferred workflow we can see how this can be done.
lexano has quit [Ping timeout: 244 seconds]
amitk has quit [Ping timeout: 268 seconds]
lexano has joined #yocto
dti has quit [Quit: Leaving]
prabhakarlad has joined #yocto
davidinux has quit [Ping timeout: 272 seconds]
dev1990 has quit [Ping timeout: 252 seconds]
Guest38 has quit [Quit: Client closed]
Tazura has quit [Quit: Client closed]
BCMM has quit [Read error: Connection reset by peer]
rewitt has joined #yocto
rewitt has quit [Client Quit]
rewitt has joined #yocto
ecdhe has joined #yocto
ecdhe has quit [Changing host]
ecdhe has joined #yocto
Dorinda has joined #yocto
adelcast has quit [Remote host closed the connection]
Tazura has joined #yocto
<RP>
zeddii: one build down and no kernel crashes/hangs, just a selftest fail with an unfortunately named tmpfile
<RP>
zeddii: in fact the problematic lttng-ptest started working too
BCMM has joined #yocto
Tazura has quit [Quit: Client closed]
Tazura has joined #yocto
nerdboy_ has joined #yocto
nerdboy has quit [Ping timeout: 252 seconds]
<zeddii>
interesting. I'll start looking at some of the changes in the tree. There's a bunch of things we can try.
<zeddii>
a) disable the configs b) revert the changes c) set different SRCREVs (pseudo bisect).
<zeddii>
if we think it is better, then I'd start with a). I'll ponder the cleanest way to do that.
<zeddii>
if I do b), it also implies a new import of the features, since they are used. but only after we prove the revert works.
nerdboy_ is now known as nerdboy
nerdboy has quit [Changing host]
nerdboy has joined #yocto
pidge has quit [Ping timeout: 244 seconds]
<RP>
zeddii: I've triggered more builds, I'll keep pushing it, see if I can make it break at all
pidge has joined #yocto
<RP>
zeddii: I was surprised that lttng-tools started behaving though as it hadn't been at all. Have a think and let me know if you want me to adjust testing to something different
<RP>
zeddii: https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/2214 was the build. We had a selftest failure from a bad temp file name (fix sent to the list), a build-appliance issue with kernel fetching which was just horrible, some kind of fetcher race and a valgrind ptest issue
<RP>
zeddii: but nothing runtime kernel for qemux86-64
<zeddii>
I'll cook up a config disable for aufs/yaffs2 next. we can try that one tomorrow.
<RP>
zeddii: I'd not say this is definitive yet, just thought I'd share that as we usually see something odd in a build atm...
<RP>
you know what debugging this stuff is like...
<zeddii>
yup. I'd like to think it is a thread to pull on though
<RP>
zeddii: definitely. If this is the issue I'd likely be wanting those patches out the way entirely, not just config'd out
<RP>
we can't afford this kind of instability :(
<zeddii>
agreed. if the disabling of the configs fix it, that tells me it is in the feature components of those changes. and I can revert -> reimport, since there are users of them and I can't yank them out of the released tree like that.
<RP>
zeddii: when you say config, is this kernel fragment/patch removal or just defconfig?
<zeddii>
the fragments that go along with those patches enable the configs by default.
<zeddii>
aufs/yaffs2, etc, are enabled in the standard kernel type.
<zeddii>
so I'd just spin another fragment that turns them off.
<RP>
zeddii: does that remove the patching of the kernel though?
<RP>
zeddii: sorry, just trying to make sure I understand :)
<zeddii>
nope. the patching only actually happens at tree generation time. the changes are just in the branch. At our build time, those same fragments only provide the config options to enable them.
<zeddii>
so I'd provide a new one that turns them off.
<RP>
zeddii: right, that was what I was thinking the result would be
<zeddii>
right. the changes would still be in the tree, but config disabled. That at least tells us that the patches are not vandalizing core kernel routines.
<zeddii>
or if they have issues, they are inside #ifdefs
<zeddii>
which narrows the search area.
<zeddii>
to fix it fully, I'd need to isolate the actual broken code, either through inspection or a revert -> re-merge.
<RP>
zeddii: right, just ensuring I was on the right page :)
<zeddii>
we had some twiddling with aufs in the past month, so it is actually what I'm guessing it is. I'm going to start there.
* RP
worries there may be core vandalism :(
<zeddii>
I've threatened to drop it before, now that docker, etc, have all moved to overlayfs, so this is probably what I'll do for 5.13 and see if anyone notices.
<RP>
maybe a new branch in 5.10 with it jettisoned if this does prove to be the issue? :)
<RP>
anyway, one step at a time
<zeddii>
that would fix one bsp, but it is of course in all of the 5.10 branches. so it has to be a revert to clean them up, or we are vandalizing the git history.
<RP>
zeddii: hmm, right
* RP
aborts the current build and tries again, was looking far too orange
<zeddii>
I'll see if I can trick paulg to look at the patches with me and eyeball a problem :D
nerdboy has quit [Ping timeout: 264 seconds]
<RP>
zeddii: I'm sure you know his weaknesses by now :D