<eFfeM>
(oh btw the channel message seems a bit outdated, it is quite hard to join a summit that is already passed)
<LetoThe2nd>
eFfeM: don't confuse us with facts!
<qschulz>
yannholo: can you send us a mail or open a ticket on bugzilla to tell us what was the issue and how it seems you fixed it? pretty important to catch corner cases and fix them but if we're not aware of them, it's going to be difficult to fix them
<qschulz>
eFfeM: this is typically something you'd put in a .inc included by the image recipe and not a recipe itself
<qschulz>
because it's basically a completely empty package just to set up users
<qschulz>
also, since you're migrating to dunfell, try to use the new override syntax so that the upgrade to later versions in a few months/years will be less painful
<qschulz>
(the override syntax was backported to dunfell a few months back)
<eFfeM>
qschulz yeah I kinda inherited this recipe
<eFfeM>
I am already on dunfell, but I was still at .16 or .17; didn't get the covered and notcovered error there)
<Alban[m]>
Hi! I'm looking for the scc tool used by the kernel-yocto class to create the kernel config, but I just can't find anything in oe-core. Where is it hiding?
<eFfeM>
actually that error "do_populate_sysroot in both covered and notcovered" is either not well documented or I did not find the documentation
<qschulz>
eFfeM: I have absolutely no idea what this error means, never seen it before and don't know what "covered" is supposed to say
<wkawka>
Hi, is it possible that git repo somehow affects the build? I am migrating repo from gitlab to github, the original one works fine, but the github one, which is now identical gets an error on base-files do_package (uid 1000 not found, cleaning didn't help). They are identical, excluding .git folder which is normal. I checked them with `diff -r`
<eFfeM>
RP should the warning on covered/not covered be documented somewhere (preferably with a suggestion on how to resolve it)
<qschulz>
Alban[m]: very good question, maybe zeddii will be able to tell us where the scc host/native binary comes from :)
<qschulz>
eFfeM: better error messages are always welcome :)
<qschulz>
the question is what it should say :D
<eFfeM>
qschulz definitely but as I have not really a clue on what this means it is quite hard to submit a patch, mabye I should file a ticket for this
<kayterina[m]>
qschulz: when you say that the syntax for overrides was backported to dunfell (3.1) what about hardknott(3.3)? I have a poky version of 3.3.2, should I push for an update in our syntax? Generally, I do not think the client likes to change versions regularly.
<mcfrisk_>
hi, boost fiber shared library is missing from kirkstone boost 1.78.0. it seems that it is compiled but not installed. only cmake files are installed. boost 1.79.0 in master is ok and fiber shared libs get installed. Anyone else seen this?
<qschulz>
kayterina[m]: you should not be using hardknott anymore :)
nemik has quit [Ping timeout: 245 seconds]
<mcfrisk_>
in dunfell, if boost fiber is enabled (not the default), it gets correcly installed too
nemik has joined #yocto
<qschulz>
kayterina[m]: it seems it was backported too, you can check in your bitbake git repo/directory if there's something mentioning new override syntax
ardo has quit [Read error: Connection reset by peer]
<qschulz>
michaelo: I think we should add mention to this new override syntax support in the migration manuals of older releases?
<qschulz>
e.g. for dunfell when it was actually supported
ardo has joined #yocto
wkawka has quit [Ping timeout: 252 seconds]
fray has joined #yocto
<RP>
eFfeM: it should never happen. Can you reliably reproduce it?
<qschulz>
kayterina[m]: if your version does not appear on the docs website dropdown menu, it means your release is outdated and you should update soon to something else
<kayterina[m]>
Thanks
<kayterina[m]>
"you should select the latest release version in this series, 3.3.6." since it is older version, this will never see a 3.3.7?
<qschulz>
kayterina[m]: correct
thumbcore[m] has quit [Quit: You have been kicked for being idle]
protu[m] has quit [Quit: You have been kicked for being idle]
nemik has quit [Ping timeout: 245 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 245 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 268 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 252 seconds]
nemik has joined #yocto
<eFfeM>
RP was afk for a while, but if you were referring to my issue when you wrote this:
<eFfeM>
If I can get a reproducer and some time to work on it, I can probably fix it
<eFfeM>
I know what the error means, it effectively means the internal runqueue state is corrupt. What I don't know is how it got there
<eFfeM>
didn't get to submitting a ticket, note that this happened with the latest yocto/dunfell, I haven't seen it before
<eFfeM>
(that is what I wanted to double-check before submitting the ticket)
<RP>
eFfeM: I was referring to your issue. You're saying putting that in a file, something like a_1.0.bb and then "bitbake a" should reproduce?
ardo has quit [Read error: Connection reset by peer]
ardo has joined #yocto
jmiehe has joined #yocto
pgowda_ has joined #yocto
mihai has joined #yocto
florian_kc has joined #yocto
florian has quit [Killed (NickServ (GHOST command used by florian_kc))]
florian_kc is now known as florian
<RP>
eFfeM: If that was dunfell, it is possible master did get some fixes too :/
<RP>
some things weren't easily backportable
goliath has quit [Quit: SIGSEGV]
goliath has joined #yocto
DvorkinDmitry has joined #yocto
<DvorkinDmitry>
why may I have "host key verification failed" problem for SRC_URI=git://... and what should I do? https://pastebin.com/ynHpzf9L
alicef has quit [Quit: install gentoo]
<qschulz>
DvorkinDmitry: are you able to git clone this repo via SSH outside of bitbake?
alicef has joined #yocto
<DvorkinDmitry>
qschulz, yes, I do
<DvorkinDmitry>
case I have ~/.ssh/id_rsa in user homedir. I am running bitbake being logged in as the same user
seninha has joined #yocto
<qschulz>
DvorkinDmitry: are you using a container for building with bitbake?
<DvorkinDmitry>
qschulz, no, I am not
<qschulz>
DvorkinDmitry: remove git@ from yuour URL and remove user=git too
<qschulz>
and try again
<qschulz>
nevermind, I think you need the git@
<DvorkinDmitry>
when I am running the same command (export ...) in plain CLI, without bitbake, it just says about new key (for what reason?! I have a github key in my known_hosts already!) and says: "Are you sure you want to continue connecting?"
<qschulz>
and user= will not be used I think
<qschulz>
DvorkinDmitry: ah well, that's the issue
<qschulz>
bitbake runs in non-interactive mode so IIRC, it'll fail if you SSH asks some question
<DvorkinDmitry>
I have id_rsa key cached in my known_hosts. It offers ECDSA key. What should I do?
<mihai>
DvorkinDmitry: test if you get the same if you "ssh git@github.com" yourself
<neverpanic>
DvorkinDmitry: .ssh/known_hosts is the file you should be concerned with. .ssh/id_rsa is your RSA private key, and should never contain an ECDSA key.
<neverpanic>
Ensure that your .ssh/known_hosts has a correct entry for github.com
<DvorkinDmitry>
neverpanic, I added: `ssh-keyscan github.com >> ~/.ssh/known_hosts`, but it did not help
<yannholo>
qschulz: I have asked for an access to the yocto bugzilla
ardo has quit [Read error: Connection reset by peer]
<vmeson>
If you plan to merge that Sundeep could work with upstream to see if there's a way to keep us and upstream happy. I'll open a bug if needed.
<JaMa>
vmeson: I did first few build tests with langdale and -l 64 to compare pressure data with kirkston (without -l 64) and it had very small impact on max total delta, see https://pastebin.com/raw/AMsAC2zX will upload the graphs later when more builds are finished
<JaMa>
vmeson: it's also surprising that with just 2 BB_THREADS I'm seeing the total delta of 3M5 while with 16 BB_THEADS 10M (which makes sense to me), but then with 64 BB_THEADS it's only 2M and with 8 less than 1M, either the max value isn't very intesting (maybe matching some strange spike) or something doesn't work well on my machine, you did you get to 500-2000 cpu pressure value for regulation? do you see
<JaMa>
something in the graphs or is it just the range you were experimenting with on your builders?
roussinm has joined #yocto
yannholo_ has joined #yocto
yannholo__ has quit [Read error: Connection reset by peer]
<vmeson>
JaMa: 500-2000 is just what we saw on our builders. I think you shouldn't be looking at the maxium but rather the full set of data and pick a threshold by eye .
yannholo__ has joined #yocto
yannholo_ has quit [Ping timeout: 240 seconds]
ptsneves has quit [Ping timeout: 252 seconds]
brazuca has quit [Ping timeout: 252 seconds]
vladest has quit [Ping timeout: 268 seconds]
amitk has quit [Ping timeout: 268 seconds]
vladest has joined #yocto
<JaMa>
vmeson: ok, I've added the maximum in the graph caption to at least know the scale when looking at it :)
<JaMa>
it was showing only maximum avg10
yannholo_ has joined #yocto
yannholo__ has quit [Ping timeout: 252 seconds]
<kergoth>
Hmm bitbake var expansion logic hits some hiccups if you try to use string.format style syntax inside inline python. i.e. `${@' '.join('%s' % l for l in d.getVar('BBFILE_COLLECTIONS'))}` works, but `${@' '.join('{}'.format(l) for l in d.getVar('BBFILE_COLLECTIONS'))}` does not. It seems like it sees that closing } and as a result the ${@} isn't evaluated at all
yannholo__ has joined #yocto
yannholo_ has quit [Ping timeout: 268 seconds]
yannholo_ has joined #yocto
zpfvo has quit [Quit: Leaving.]
yannholo__ has quit [Read error: Connection reset by peer]
yannholo__ has joined #yocto
yannholo_ has quit [Ping timeout: 240 seconds]
Guest14 has joined #yocto
Guest14 is now known as brazuca
nemik has quit [Ping timeout: 245 seconds]
nemik has joined #yocto
goliath has joined #yocto
yannholo__ has quit [Remote host closed the connection]
nemik has quit [Ping timeout: 240 seconds]
brazuca has quit [Quit: Client closed]
pgowda_ has quit [Quit: Connection closed for inactivity]
<JaMa>
vmeson: -l 64 added around 10 minutes to build time (from 2:15 to 2:25), but the swap use spike is much smaller now 17.2G instead of 40G
<RP>
vmeson: if it works my plan is probably to merge and then allow incremental improvement. I'm not overly concerned since it doesn't build/work at all before my patch ;-)
<RP>
vmeson: it also highlights/confirms exactly which bits of code break
seninha has joined #yocto
florian has joined #yocto
zkrx has quit [Ping timeout: 264 seconds]
<JaMa>
vmeson: but surprisingly it made memory pressure much higher (and swap spike much bigger) for 8 bb threads
<vmeson>
JaMa: they don't call it performance tuning for nothing! too high over here, oops, too low over here...
zkrx has joined #yocto
Guest14 has joined #yocto
Guest14 is now known as brazuca
leon-anavi has quit [Quit: Leaving]
<vmeson>
JaMa: do you have a buildchard of that?
<vmeson>
*buildchart
<JaMa>
just the pressure graphs and grafana in the repo
<JaMa>
cannot open browser now to share exact link, because another build is already running (with 1000 cpu pressure limit)
<Guest87>
do i need to do something special if i am generating the PV variable with conditionals?
<R0b0t1>
so somehow the serial on my board (lovingly named ttySTM0 to remind you who you bought it from) isn't getting a login prompt. I'm trying a util-linux package to fix it, but is there another way?
<Guest87>
nevermind, my formula was backwards from what it should have been
frieder has quit [Remote host closed the connection]
an_sensr[m] has joined #yocto
<R0b0t1>
found it, it's trying to mount by guid and the guid doesn't get set properly somehow