Monday, 2023-01-09

*** otavio <otavio!> has quit IRC (Remote host closed the connection)00:02
*** uniqdom <uniqdom!~uniqdom@> has quit IRC (Quit: Leaving)00:09
*** BCMM <BCMM!~BCMM@user/bcmm> has quit IRC (Quit: Konversation terminated!)00:09
*** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV)00:12
*** Wouter010067 <Wouter010067!> has quit IRC (Quit: The Lounge -
*** Wouter010067 <Wouter010067!> has joined #yocto00:20
*** xmn <xmn!> has joined #yocto00:28
*** yashraj466 <yashraj466!~yashraj46@2401:4900:1b97:9606:d864:6936:3a5a:1cc6> has quit IRC (Quit: Client closed)00:32
*** florian <florian!> has quit IRC (Ping timeout: 272 seconds)00:39
*** sakoman <sakoman!> has quit IRC (Quit: Leaving.)01:01
*** otavio <otavio!> has joined #yocto01:43
*** seninha <seninha!~seninha@user/seninha> has quit IRC (Quit: Leaving)01:48
*** camus <camus!~Instantbi@> has joined #yocto01:52
*** camus1 <camus1!~Instantbi@> has joined #yocto01:55
*** seninha <seninha!~seninha@user/seninha> has joined #yocto01:56
*** camus <camus!~Instantbi@> has quit IRC (Ping timeout: 272 seconds)01:57
*** camus1 is now known as camus01:57
*** davidinux <davidinux!~davidinux@> has quit IRC (Ping timeout: 260 seconds)02:04
*** invalidopcode <invalidopcode!> has quit IRC (Read error: Connection reset by peer)02:05
*** invalidopcode <invalidopcode!> has joined #yocto02:05
*** davidinux <davidinux!~davidinux@> has joined #yocto02:06
*** seninha <seninha!~seninha@user/seninha> has quit IRC (Remote host closed the connection)02:24
*** jclsn <jclsn!~jclsn@2a04:4540:651f:f000:2ce:39ff:fecf:efcd> has quit IRC (Ping timeout: 260 seconds)03:45
*** jclsn <jclsn!~jclsn@2a04:4540:6502:9a00:2ce:39ff:fecf:efcd> has joined #yocto03:47
*** xmn <xmn!> has quit IRC (Quit: ZZZzzz…)04:18
*** amitk <amitk!~amit@> has joined #yocto04:18
*** nemik <nemik!~nemik@> has quit IRC (Ping timeout: 272 seconds)04:29
*** nemik <nemik!> has joined #yocto04:29
*** nemik <nemik!> has quit IRC (Ping timeout: 265 seconds)04:34
*** nemik <nemik!~nemik@> has joined #yocto04:34
*** olani- <olani-!> has quit IRC (Ping timeout: 260 seconds)05:26
*** Herrie|Laptop <Herrie|Laptop!> has joined #yocto06:06
*** alessioigor <alessioigor!~alessioig@> has joined #yocto06:13
*** goliath <goliath!~goliath@user/goliath> has joined #yocto06:28
*** rob_w <rob_w!> has joined #yocto06:35
*** Xagen <Xagen!> has quit IRC (Quit: Textual IRC Client:
*** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV)06:57
*** lexano <lexano!~lexano@> has quit IRC (Ping timeout: 260 seconds)07:06
*** lexano <lexano!~lexano@> has joined #yocto07:20
*** lamm1 <lamm1!~lamm@> has joined #yocto07:22
*** alessioigor <alessioigor!~alessioig@> has quit IRC (Quit: alessioigor)07:27
*** alessioigor <alessioigor!~alessioig@> has joined #yocto07:27
*** bps2 <bps2!> has joined #yocto07:38
*** amitk_ <amitk_!~amit@> has joined #yocto07:42
*** amitk <amitk!~amit@> has quit IRC (Ping timeout: 265 seconds)07:45
*** mckoan|away is now known as mckoan07:51
mckoangood morning07:51
kanavinJaMa, your patch is fine with me. The reason it wasn't defined is that I don't want to define things that aren't proven necessary :-) in my testing and on the AB it was not necessary.07:53
*** frieder <frieder!> has joined #yocto07:57
*** manuel1985 <manuel1985!~manuel198@2a02:1748:dd5c:f290:c5b2:fdff:b718:9edf> has joined #yocto07:58
lamm1wrong terminal hehehe07:58
*** money_ <money_!> has joined #yocto08:01
*** money_ <money_!> has quit IRC (Client Quit)08:02
*** goliath <goliath!~goliath@user/goliath> has joined #yocto08:02
LetoThe2ndyo dudX08:07
*** zpfvo <zpfvo!> has joined #yocto08:10
*** money_ <money_!> has joined #yocto08:15
*** money_ <money_!> has quit IRC (Client Quit)08:17
*** gho <gho!> has joined #yocto08:18
*** mvlad <mvlad!~mvlad@2a02:2f08:470d:8800:24d7:51ff:fed6:906d> has joined #yocto08:19
*** frieder <frieder!> has quit IRC (Ping timeout: 260 seconds)08:19
*** money_ <money_!> has joined #yocto08:23
*** vladest <vladest!> has quit IRC (Ping timeout: 252 seconds)08:28
LetoThe2ndanybody happen to know why python3 and nodejs by now depend on bash? IIRC that wasn't the case some time ago.08:29
JaMalet me grep it for you:08:30
JaMameta/recipes-devtools/python/${PN}-tests:append:class-target = " ${MLPREFIX}bash"08:30
JaMameta/recipes-devtools/python/${PN}-tests:append:class-nativesdk = " ${MLPREFIX}bash"08:30
*** money_ <money_!> has quit IRC (Ping timeout: 256 seconds)08:30
LetoThe2ndJaMa: yeah I found that too, but I'm not talking about the -tests package08:31
JaMahow the hell I'm supposed to guess what you're talking about? "depend on bash" sounds like build time dependency08:32
LetoThe2ndJaMa: ok, apologies. my mindset is "unless explicitly stated otherwise, refers to runtime".08:33
*** frieder <frieder!> has joined #yocto08:33
*** money_ <money_!> has joined #yocto08:33
*** money_ is now known as money08:33
LetoThe2ndso, try to improve: why does installing python3 or nodejs cause bash to also be installed? this did not use to be the case some time ago, and I cannot easily spot the reason.08:34
JaMaLetoThe2nd: then it's just not true in my builds, python3 is empty package and nodejs doesn't depend on bash (only nodejs-npm does)08:35
LetoThe2ndJaMa: hmm interesting. which release?08:35
JaMamaster from Sunday08:35
LetoThe2ndJaMa: distro?08:35
JaMathe same in langdale and kirkstone08:35
JaManodistro, LuneOS, webOS..08:36
LetoThe2ndJaMa: okay thanks. then needs more digging obviously  :(08:36 is your friend08:37
LetoThe2ndi know, but oe-depends-dot also just confirmed the chain without naming the reason.08:37
*** d-s-e <d-s-e!> has joined #yocto08:41
*** money <money!~money@user/polo> has quit IRC (Quit: late)08:42
mcfriskRDEPENDS only? one of them including a #!/bin/bash script somewhere08:42
mcfriskno yocto in !?08:46
*** d-s-e <d-s-e!> has quit IRC (Quit: Konversation terminated!)08:47
*** d-s-e <d-s-e!> has joined #yocto08:57
*** vladest <vladest!~Thunderbi@> has joined #yocto08:59
*** zpfvo <zpfvo!> has quit IRC (Quit: Leaving.)09:02
*** zpfvo <zpfvo!> has joined #yocto09:03
*** vladest <vladest!~Thunderbi@> has quit IRC (Remote host closed the connection)09:03
*** vladest <vladest!~Thunderbi@> has joined #yocto09:05
*** leon-anavi <leon-anavi!~Leon@> has joined #yocto09:06
*** vladest <vladest!~Thunderbi@> has quit IRC (Client Quit)09:07
*** vladest <vladest!~Thunderbi@> has joined #yocto09:07
*** vladest1 <vladest1!~Thunderbi@> has joined #yocto09:08
*** vladest <vladest!~Thunderbi@> has quit IRC (Read error: Connection reset by peer)09:08
*** vladest1 is now known as vladest09:08
*** vladest <vladest!~Thunderbi@> has quit IRC (Client Quit)09:10
*** vladest <vladest!~Thunderbi@> has joined #yocto09:10
*** seninha <seninha!~seninha@user/seninha> has joined #yocto09:10
*** vladest <vladest!~Thunderbi@> has quit IRC (Client Quit)09:12
*** vladest <vladest!~Thunderbi@> has joined #yocto09:12
*** Herrie|Laptop <Herrie|Laptop!> has quit IRC (Ping timeout: 260 seconds)09:19
*** Guest8400 <Guest8400!> has joined #yocto09:19
*** dmoimas_cynexo <dmoimas_cynexo!~dmoimas_c@> has joined #yocto09:26
*** vladest <vladest!~Thunderbi@> has quit IRC (Remote host closed the connection)09:27
*** dmoimas_cynexo <dmoimas_cynexo!~dmoimas_c@> has left #yocto09:27
*** vladest <vladest!~Thunderbi@> has joined #yocto09:28
*** Herrie|Laptop <Herrie|Laptop!> has joined #yocto09:31
*** invalidopcode <invalidopcode!> has quit IRC (Remote host closed the connection)09:34
*** florian <florian!> has joined #yocto09:34
*** invalidopcode <invalidopcode!> has joined #yocto09:34
*** Guest8400 <Guest8400!> has quit IRC (Quit: late)09:43
*** manuel1985 <manuel1985!~manuel198@2a02:1748:dd5c:f290:c5b2:fdff:b718:9edf> has quit IRC (Ping timeout: 260 seconds)09:46
*** azcraft <azcraft!~AzCraft@> has joined #yocto09:47
*** Wouter010067 <Wouter010067!> has quit IRC (Quit: The Lounge -
*** Wouter010067 <Wouter010067!> has joined #yocto09:50
RPmcfrisk: I don't know of anyone invited10:00
RPmcfrisk: sounds very systemd centric10:00
kanavinRP: if you're seeing gdk-pixbuf fails, I'm looking into that10:08
kanavinRP: one of the build hosts is using ivy bridge, and after moving to v3 that revealed an erroneous use of target .so with native executable in that recipe --> illegal instruction crash10:15
*** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV)10:16
*** goliath <goliath!~goliath@user/goliath> has joined #yocto10:16
*** elaye <elaye!> has joined #yocto10:17
RPkanavin: I hadn't got there yet but handy to know, thanks! :)10:24
RPabelloni: ^^^10:25
RPkanavin: I'm a bit worried we have another bitbake lockup :(10:25
kanavinRP: if that leads to something I did, I can try to help10:30
RPkanavin: it is almost certainly my threading changes10:34
*** d-s-e <d-s-e!> has quit IRC (Ping timeout: 272 seconds)10:36
kanavinRP, abelloni: I'll also check what happens in qemu on that host. It'll probably crash as well, and so needs to be excluded from kvm workers.10:43
*** d-s-e <d-s-e!> has joined #yocto10:45
*** demirok <demirok!~bell@user/demirok> has joined #yocto10:55
qschulzi'm trying to get a or whatever I can get for finding out which package brings in a package I don't want10:59
qschulzbitbake -g does not seem to be doing the trick10:59
*** alessioigor <alessioigor!~alessioig@> has quit IRC (Read error: Connection reset by peer)11:01
*** alessioigor <alessioigor!~alessioig@> has joined #yocto11:02
*** starblue <starblue!> has quit IRC (Ping timeout: 268 seconds)11:02
qschulzmmmm the file does not exist since 3.0, so we should remove this from the help section of some tools :)11:03
*** starblue <starblue!> has joined #yocto11:04
*** d-s-e <d-s-e!> has quit IRC (Ping timeout: 260 seconds)11:06
kanavinRP: where does the AB get the list of its workers from? I'm looking at, and it doesn't seem to match reality, e.g. fedora36 is not there.11:20
*** AntA <AntA!~anta@> has joined #yocto11:25
*** d-s-e <d-s-e!> has joined #yocto11:28
RPkanavin: the config on the controller is slightly out of sync11:35
RPkanavin: mostly for passwords and so on11:36
*** xmn <xmn!> has joined #yocto11:44
rfriedIs there a good way to prevent update-rc.d from running in bbappend ?11:48
rfriedI have some packages I want to install, but I don't want them starting automatically.11:48
rfriedBut I can't find a proper way of disabling it via bbappend.11:48
rfriedLooks like the updaterc.d is launched as part of the inherit of update-rc.d11:48
*** d-s-e <d-s-e!> has quit IRC (Ping timeout: 268 seconds)11:49
*** xmn_ <xmn_!> has joined #yocto11:50
RPrfried: do you want to disable update-rc.d for all packages or just one package in particular ?11:52
*** xmn <xmn!> has quit IRC (Remote host closed the connection)11:52
rfriedRP: just one package in particular11:54
RPrfried: you could set INITSCRIPT_PACKAGES explicitly?11:58
rfriedit fails because then it runs update-rc.d -r /work/ramon/bsp/bsp/build/tmp/work/aspen-poky-linux/core-image-minimal/1.0-r0/rootfs11:59
rfriedBasically it removed the two arguments and updare-rc.d fails.12:00
rfriedbasename and default is missing, that's why it fails.12:01
rfriedRP: ^12:01
RPrfried: I don't really understand what you've done or how it would result in that :/12:06
rfriedRP: the package I'm working on is ntp12:06
rfriedI created ntp_%.bbappend with the following content:12:07
rfried# Override initscripts to disable autoloading12:07
rfriedINITSCRIPT_NAME = ""12:07
rfriedINITSCRIPT_PARAMS = ""12:07
rfriedThat's it./12:07
rburtonjust set INITSCRIPT_PARAMS=disable12:09
rburtondefault is "defaults" which is enabling12:09
*** beneth <beneth!> has quit IRC (Read error: Connection reset by peer)12:14
*** alessioigor <alessioigor!~alessioig@> has quit IRC (Quit: alessioigor)12:22
*** alessioigor <alessioigor!~alessioig@> has joined #yocto12:22
rfriedrburton: works.12:24
rfriedthanks RB  rburton12:24
*** d-s-e <d-s-e!> has joined #yocto12:24
*** manuel_ <manuel_!~manuel198@2a02:1748:dd5c:f290:c553:9012:6082:a89a> has joined #yocto12:33
*** manuel <manuel!~manuel198@2a02:1748:dd5c:f290:c553:9012:6082:a89a> has quit IRC (Ping timeout: 265 seconds)12:35
*** manuel_ <manuel_!~manuel198@2a02:1748:dd5c:f290:c553:9012:6082:a89a> has quit IRC (Ping timeout: 265 seconds)12:38
*** manuel <manuel!~manuel198@2a02:1748:dd5c:f290:c553:9012:6082:a89a> has joined #yocto12:45
*** manuel <manuel!~manuel198@2a02:1748:dd5c:f290:c553:9012:6082:a89a> has quit IRC (Read error: Connection reset by peer)12:49
*** manuel_ <manuel_!~manuel198@2a02:1748:dd5c:f290:c553:9012:6082:a89a> has joined #yocto12:49
*** kscherer <kscherer!> has joined #yocto12:49
*** Wouter010067 <Wouter010067!> has quit IRC (Quit: The Lounge -
*** Wouter010067 <Wouter010067!> has joined #yocto13:00
*** xmn_ <xmn_!> has quit IRC (Quit: xmn_)13:01
*** alessioigor <alessioigor!~alessioig@> has quit IRC (Quit: alessioigor)13:02
*** alessioigor <alessioigor!~alessioig@> has joined #yocto13:02
*** xmn <xmn!> has joined #yocto13:14
elayeHi, I'm having trouble building a recipe for a Rust private crate. I generated the recipe with `cargo-bitbake`. Bitbake successfully fetches the private repo and it's private dependencies via SSH however when bitbake invokes `cargo build`, cargo is unable to fetch the private repos anymore. I adapted my recipe based on this similar issue for Go13:38
elaye,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,82558905 but to no avail. Here is the error log: and here is my recipe:
qschulzelaye: it seems your host was not able to resolve
elayeqschulz: yes that's what the cargo error seems to imply however I can build the crate on the same host outside of the bitbake environment, and bitbake is also able to fetch the crate from the private gitlab repo13:43
rburtonnetwork is disabled in do_compile, so it must be going to fetch. why can't you fetch everything via SRC_URI?13:44
elayerburton: ah I see that would make sense. Everything is actually fetched via SRC_URI, and this works since I can see the repos cloned in the build/tmp directory. So I guess the issue comes from cargo not being able to use the crates fetched by SRC_URI13:47
RPrburton: any idea what this means from debuginfod: ? :/13:51
RPrburton:  it is also spewing all those warnings which makes the logs really really annoying13:51
*** sakoman <sakoman!> has joined #yocto13:51
*** vladest <vladest!~Thunderbi@> has quit IRC (Ping timeout: 260 seconds)14:07
*** zpfvo <zpfvo!> has quit IRC (Ping timeout: 260 seconds)14:16
*** zpfvo <zpfvo!> has joined #yocto14:17
*** vladest <vladest!> has joined #yocto14:30
*** whuang0389 <whuang0389!> has joined #yocto14:32
*** zpfvo <zpfvo!> has quit IRC (Ping timeout: 256 seconds)14:39
*** zpfvo <zpfvo!> has joined #yocto14:40
*** zpfvo <zpfvo!> has quit IRC (Ping timeout: 260 seconds)14:45
*** zpfvo <zpfvo!> has joined #yocto14:46
*** Xagen <Xagen!> has joined #yocto14:56
*** |Xagen <|Xagen!> has joined #yocto14:58
*** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV)15:00
*** Xagen <Xagen!> has quit IRC (Ping timeout: 246 seconds)15:00
*** rob_w <rob_w!> has quit IRC (Quit: Leaving)15:05
*** rsalveti <rsalveti!> has joined #yocto15:07
*** d-s-e <d-s-e!> has quit IRC (Ping timeout: 252 seconds)15:20
*** d-s-e <d-s-e!> has joined #yocto15:21
qschulzmoto-timo: how bad is it to have [PATCH meta-python 0/2] instead of [meta-python][PATCH 0/2]?15:43
qschulzmoto-timo: I think b4 only supports generating patches with the first pattern15:43
qschulzjust to know if I should just edit the headers by hand/work with b4 to have something match your worflow15:43
rburtonRP: hm, give me a minute and i'll page that knowledge back in15:45
*** whuang0389 <whuang0389!> has quit IRC (Ping timeout: 260 seconds)15:45
rburtonRP: reliably failing or intermittent15:47
RPrburton: intermittent, naturally. I think the long logs are consistent though, just hidden if nothing fails in that thread15:54
rburtoni wonder if its getting mixed up with multiple testimages happening at once15:54
RPrburton: they'd be in separate build directories15:56
rburtonits a network operation to the host15:56
rburtonso it might be hitting the wrong debuginfod socket15:56
rburtonfairly easily tested, give me a bit15:57
*** Tokamak <Tokamak!~tokamak@2603:c020:4004:f00::5> has quit IRC (Quit: ZNC 1.8.2+deb2build5 -
*** goliath <goliath!~goliath@user/goliath> has joined #yocto16:04
moto-timoqschulz: that is a question for khem, as he is the one staging patches16:04
rburtonRP: the locked database thing is weird as its using an in-memory db for the selftest16:06
RPrburton: yes, I don't understand it but I've not looked :/16:07
rburton[Mon 09 Jan 2023 11:18:44 AM GMT] (3773146/3773146): upstream debuginfod servers:
rburtonwell i doubt that's the problem but that's stupid :)16:09
*** lamm1 <lamm1!~lamm@> has quit IRC (Ping timeout: 265 seconds)16:09
rburtonah i wonder if its grabbing that from the environment somehow16:10
rburtonyes, interesting16:11
*** alessioigor <alessioigor!~alessioig@> has quit IRC (Quit: alessioigor)16:12
*** alessioigor <alessioigor!~alessioig@> has joined #yocto16:13
*** manuel1985 <manuel1985!~manuel198@2a02:1748:dd5c:f290:c5b2:fdff:b718:9edf> has joined #yocto16:22
*** agrue <agrue!> has quit IRC (Quit: ZNC 1.7.5+deb4 -
*** invalidopcode <invalidopcode!> has quit IRC (Remote host closed the connection)16:31
*** invalidopcode <invalidopcode!> has joined #yocto16:32
*** florian_kc <florian_kc!> has joined #yocto16:32
*** agrue <agrue!> has joined #yocto16:32
*** Estrella <Estrella!> has joined #yocto16:34
*** Estrella__ <Estrella__!> has quit IRC (Ping timeout: 265 seconds)16:37
*** Estrella_ <Estrella_!> has quit IRC (Ping timeout: 268 seconds)16:37
*** Estrella__ <Estrella__!> has joined #yocto16:37
*** frieder <frieder!> has quit IRC (Quit: Leaving)16:41
*** d-s-e <d-s-e!> has quit IRC (Ping timeout: 252 seconds)16:45
*** Payam <Payam!> has joined #yocto16:46
*** Payam <Payam!> has quit IRC (Quit: Leaving)16:54
*** gho <gho!> has quit IRC (Quit: Leaving.)17:01
*** zpfvo <zpfvo!> has quit IRC (Remote host closed the connection)17:02
qschulzmoto-timo: your mail address is outdated here:
*** mckoan is now known as mckoan|away17:06
*** demirok <demirok!~bell@user/demirok> has quit IRC (Quit: Leaving.)17:07
*** elaye <elaye!> has quit IRC (Quit: Client closed)17:09
rburtonRP: ffs try to replicate and it just fails [Mon Jan  9 17:07:21 2023] (2119034/2119034): libmicrohttpd error: Failed to create worker inter-thread communication channel: Too many open files17:10
*** demirok <demirok!~bell@user/demirok> has joined #yocto17:10
RPrburton: sounds very strange17:11
rburton$ sysctl fs.file-nr17:12
rburtonfs.file-nr = 1385606553617:12
moto-timoqschulz:  no, that is a valid email address for non-work FOSS17:12
victoridaho[m]Anyone have any ideas on how to resolve "Error: Could not find class file for '" when trying to add "perf" to the build? Not even sure why "perf" needs java.17:12
rburtoni'll push that up maybe it needs more17:12
rburtonvictoridaho[m]: perf doesn't17:13
rburton(i built perf and don't even have java installed or meta-java added)17:13
victoridaho[m]rburton: I think it has to do with creating debug symbols etc.17:13
qschulzmoto-timo: got rejected by your mail provider then17:14
rburtonah hm perf does have some java poking17:14
rburtonso it probably found java on your host and tried to use it17:14
victoridaho[m]It's running "/workdir/build-shasta-dev/tmp/work/x86_64-linux/icedtea7-native/2.1.3-r1.0/icedtea-2.1.3/build/bootstrap/jdk1.6.0/bin/java"17:14
qschulzmoto-timo: and I stupidly deleted the mails so can't say, will try with a simple mail instead17:14
rburtonvictoridaho[m]: so our perf recipe turns off java support17:15
rburtonvictoridaho[m]: but you're enabling it as its building icedtea, so you shoud talk to the meta-java maintainers17:16
victoridaho[m]How do I find who are the maintainers?17:16
rburtonmeta-java's readme file17:16
qschulzmoto-timo: k my bad, got a reject from spam assassin or simialr17:18
*** whuang0389 <whuang0389!> has joined #yocto17:18
qschulzmoto-timo: PEBKAC, sorry17:20
*** florian_kc <florian_kc!> has quit IRC (Remote host closed the connection)17:22
*** whuang0389 <whuang0389!> has quit IRC (Ping timeout: 260 seconds)17:26
rburtonRP: would be easier to strace if debuginfod didn't spawn literally 1000 threads17:27
rburtonstrace -ff resulted in 1018 log files17:27
RPrburton: that sounds a bit crazy :/17:27
*** florian_kc <florian_kc!> has joined #yocto17:28
rburtonRP: its opening a silly number of epoll sockets and hitting the limit on this machine (the 256 core one...)17:33
*** florian <florian!> has quit IRC (Quit: Ex-Chat)17:38
*** florian_kc <florian_kc!> has quit IRC (Ping timeout: 265 seconds)17:42
*** manuel1985 <manuel1985!~manuel198@2a02:1748:dd5c:f290:c5b2:fdff:b718:9edf> has quit IRC (Ping timeout: 252 seconds)17:49
*** alessioigor <alessioigor!~alessioig@> has quit IRC (Quit: alessioigor)17:52
kanavinrburton,   -c, --concurrency=NUM      Limit scanning thread concurrency to NUM,17:53
kanavin                             default=#CPUs.17:53
kanavin  -C, --connection-pool[=NUM]   Use webapi connection pool with NUM threads,17:53
kanavin                             default=unlim.17:53
kanavinrelevant maybe?17:53
rburtonyeah just wondering why its trying to open 1000+ epoll sockets18:02
kanavinhalstead, how many pre-haswell build machines are there on the AB? I found at least one (fedora36-ty-1) with 'E5-2697 v2' - v2 is ivy bridge, and just one version short. There's a change in oe-core that requires at least haswell hardware when running qemu with kvm.18:08
kanavinRP: ^^^. I fixed gdk-pixbuf, but runqemu kvm does crash on that machine, it's just one generation too old.18:08
kanavinRP: I'd hope there is not a lot of those, we'd be seeing a lot more crashes if it was so.18:10
halsteadkanavin: I think there are quite a few ivybridge machines as well as a few ARM64 machines. I can get a count. Which AMD chips are supported?18:10
kanavinhalstead, intel: haswell and newer, amd: excavator and newer18:11
kanavinarm64 is not affected18:12
*** beneth <beneth!> has joined #yocto18:18
moto-timoqschulz: your patches aren't being picked up by lore nor patchwork... perhaps you need to use 'b4 prep --set-prefixes' differently?
moto-timoqschulz: I haven't tried using b4 to send patches yet18:45
halsteadkanavin: I emailed you the list of CPUs. It does appear everything else is haswell or newer.18:47
halsteadkanavin: Oh and is also an E5-2697 v2. Do we use qemu on the perf workers?18:49
*** vladest <vladest!> has quit IRC (Remote host closed the connection)19:02
*** invalidopcode <invalidopcode!> has quit IRC (Remote host closed the connection)19:05
*** Wouter010067 <Wouter010067!> has quit IRC (Quit: The Lounge -
*** invalidopcode <invalidopcode!> has joined #yocto19:05
*** Wouter010067 <Wouter010067!> has joined #yocto19:05
*** vladest <vladest!> has joined #yocto19:06
kanavinhalstead, thanks. perf workers are not affected either.19:06
halsteadkanavin: So do we need to limit builds on fedora36-ty-1 or retire the hardware?19:07
kanavinhalstead, I'm not sure what's best, but maybe you have a spare CPU you could swap in, or simply disable the worker.19:07
kanavinhalstead, I don't think we can easily filter builds at the moment by whether they need kvm or not, so it can't run anything from a-full or a-quck19:08
halsteadkanavin: I think we are out of spare CPUs. I can double check. We might have to retire that worker and make it a perf machine or something.19:09
*** florian_kc <florian_kc!> has joined #yocto19:10
kanavinhalstead, thanks, I don't have any particular suggestions.19:11
kanavinhalstead, not sure if you're aware, it's due to enabling level 3 instructions:
*** leon-anavi <leon-anavi!~Leon@> has quit IRC (Quit: Leaving)19:13
kanavinlevel 4 will not be happening anytime soon (or probably not so soon either)19:14
*** Haxxa <Haxxa!> has quit IRC (Quit: Haxxa flies away.)19:15
kanavin(the table is slightly out of date, qemu does support level 3 since one month ago)19:15
*** Haxxa <Haxxa!> has joined #yocto19:19
*** Estrella__ <Estrella__!> has quit IRC (Quit: - Chat comfortably. Anywhere.)19:25
*** amitk_ <amitk_!~amit@> has quit IRC (Ping timeout: 264 seconds)19:33
*** nemik <nemik!~nemik@> has quit IRC (Ping timeout: 268 seconds)19:39
*** nemik <nemik!> has joined #yocto19:39
*** nemik <nemik!> has quit IRC (Ping timeout: 272 seconds)19:44
*** nemik <nemik!~nemik@> has joined #yocto19:44
*** ferry <ferry!> has joined #yocto19:50
*** ferry <ferry!> has quit IRC (Client Quit)19:52
*** florian_kc <florian_kc!> has quit IRC (Ping timeout: 252 seconds)20:04
*** Estrella_ <Estrella_!> has joined #yocto20:18
*** Herrie|Laptop|2 <Herrie|Laptop|2!> has joined #yocto20:23
*** Herrie|Laptop <Herrie|Laptop!> has quit IRC (Ping timeout: 260 seconds)20:25
*** PhoenixMage <PhoenixMage!~phoenix@> has quit IRC (Ping timeout: 246 seconds)20:32
*** PhoenixMage <PhoenixMage!~phoenix@> has joined #yocto20:39
*** florian_kc <florian_kc!> has joined #yocto20:39
*** PhoenixMage <PhoenixMage!~phoenix@> has quit IRC (Ping timeout: 268 seconds)20:46
*** PhoenixMage <PhoenixMage!~phoenix@> has joined #yocto20:47
*** sakoman <sakoman!> has quit IRC (Quit: Leaving.)20:51
*** PhoenixMage <PhoenixMage!~phoenix@> has quit IRC (Ping timeout: 268 seconds)20:52
*** PhoenixMage <PhoenixMage!~phoenix@> has joined #yocto20:53
*** Minvera <Minvera!~Minvera@user/Minvera> has joined #yocto20:53
*** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has quit IRC (Ping timeout: 255 seconds)20:54
*** florian_kc <florian_kc!> has quit IRC (Ping timeout: 252 seconds)20:55
*** florian_kc <florian_kc!> has joined #yocto20:56
*** PhoenixMage <PhoenixMage!~phoenix@> has quit IRC (Ping timeout: 260 seconds)20:58
*** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has joined #yocto20:59
*** alessioigor <alessioigor!~alessioig@> has joined #yocto20:59
*** PhoenixMage <PhoenixMage!~phoenix@> has joined #yocto21:00
*** alessioigor <alessioigor!~alessioig@> has quit IRC (Client Quit)21:01
*** Payam <Payam!> has joined #yocto21:02
*** ferlzc <ferlzc!~ferlzc@> has joined #yocto21:03
*** ferlzc <ferlzc!~ferlzc@> has quit IRC (Quit: Leaving)21:06
RPkanavin: we might just have to drop back a tune level, we really need the hardware we have21:16
*** ferry_ <ferry_!> has joined #yocto21:21
*** jooli <jooli!> has joined #yocto21:21
*** ferry_ <ferry_!> has quit IRC (Client Quit)21:21
RPhalstead: We can probably go back to an older tune for a while as I suspect if we're hitting this, too many others will as well21:23
halsteadRP, the uninative is ready.21:24
halsteadRP, can we select the tune adaptively?21:24
RPhalstead: I saw, thanks for the that. I'll be happy if we can fix some issues with that!21:25
RPhalstead: no, this is the CPU optimisation the target binaries are built for so it needs to be the same for qemux86-64 everywhere21:25
*** vmeson <vmeson!> has quit IRC (Quit: Konversation terminated!)21:29
halsteadI suppose this is an example of our diverse build lab helping certain users.21:30
RPhalstead: right, I think that is the best way to look at it21:32
*** sakoman <sakoman!> has joined #yocto21:35
JaMaFWIW: I've changed DEFAULTTUNE to corei7-64 (instead of the original core2-64), because of VirtualBox and all seems to work
*** jooli59 <jooli59!> has joined #yocto21:37
*** jooli59 <jooli59!> has quit IRC (Client Quit)21:37
*** vvmeson <vvmeson!> has joined #yocto21:40
paulgI don't know where to look to answer this - can anyone say if qemu ppc64 boot tests are still run as part of autobuild coverage?21:44
RPpaulg: I was talking to vvmeson about this last week. We don't build or boot ppc64 at all at the moment21:51
RPpaulg: no qemuppc64 on
RPwell, not active21:52
vvmesonpaulg: Yeah, we need to convince RP and the YP TSC to drop something (mips64!) and add ppc64. I had assumed that ppc64 was being tested.21:53
paulgok - thanks - good to know.21:53
paulgand no.  I won't support adding ppc64.21:54
*** jooli512 <jooli512!> has joined #yocto21:54
*** jooli <jooli!> has quit IRC (Quit: Client closed)21:54
*** jooli512 <jooli512!> has quit IRC (Client Quit)21:54
paulgwe (RP and I) talked about this over a year ago when ppc32 was becoming problematic emulating a 1998 turd.21:55
*** jooli <jooli!> has joined #yocto21:55
vvmesonpaulg: but I bet you wouldn't mind if we drop mips64!21:55
paulgYes, I want all old crap dropped.  It is no secret.21:56
paulgIt is how software survives.21:56
paulgI'm sure RP would be thrilled to see a release blocked for a yocto-on-Amiga bug.21:57
RPpaulg: I'd be surprised it worked there in the first place :D21:59
abellonichallenge accepted!21:59
paulgyocti, tell vmeson ppc64 and mips64 should die together like Thelma and Louise.21:59
yoctipaulg: Error: I haven't seen vmeson, I'll let you do the telling.21:59
* RP does have YP building images for his AVR microcontrollers 22:00
paulgyocti, tell vvmeson ppc64 and mips64 should die together like Thelma and Louise.22:00
yoctipaulg: The operation succeeded.22:00
RPThe scary bit of my AVR support is it builds a gcc on target cross compiler :D22:00
paulgI should know better by now to simply trust tab completion on IRC nicks.22:01
RPAn x86-64 host building a cross compiler to run on an arm board generating AVR binaries22:02
paulgI might actually be able to get behind AVR since there are a zillion wifi LED bulbs out there that could run it.22:02
paulgI'm sure I own a bunch....22:03
* vvmeson waits for his ghost /nick to drift into the ether...22:03
abelloniRP: which version of gcc are you using for that? :)22:03
RPabelloni: it was a while ago22:03
paulgabelloni, don't go there.  ;-)  You'll never come back.22:03
paulgthings I call "time thief" or "slave to your possessions"22:04
abelloniI ripped out avr from the kernel so I know ;)22:04
*** jooli65 <jooli65!> has joined #yocto22:04
RPabelloni: it was for firmware for microcontrollers, not linux22:05
*** jooli65 is now known as jooli51222:05
*** jooli <jooli!> has quit IRC (Quit: Leaving)22:05
*** jooli512 is now known as jooli22:06
*** jooli <jooli!> has quit IRC (Client Quit)22:07
abelloniaren't we ready for avr128? :)22:09
*** Herrie|Laptop|2 <Herrie|Laptop|2!> has quit IRC (Ping timeout: 265 seconds)22:10
*** BCMM <BCMM!~BCMM@user/bcmm> has joined #yocto22:11
*** PhoenixMage <PhoenixMage!~phoenix@> has quit IRC (Ping timeout: 260 seconds)22:14
*** PhoenixMage <PhoenixMage!~phoenix@> has joined #yocto22:16
*** mvlad <mvlad!~mvlad@2a02:2f08:470d:8800:24d7:51ff:fed6:906d> has quit IRC (Remote host closed the connection)22:22
*** PhoenixMage <PhoenixMage!~phoenix@> has quit IRC (Ping timeout: 260 seconds)22:23
*** PhoenixMage <PhoenixMage!~phoenix@> has joined #yocto22:24
RPabelloni: skip to 256 ;-)22:24
*** Minvera <Minvera!~Minvera@user/Minvera> has quit IRC (Remote host closed the connection)22:26
*** vvmeson is now known as vmeson22:26
*** PhoenixMage <PhoenixMage!~phoenix@> has quit IRC (Ping timeout: 272 seconds)22:30
*** PhoenixMage <PhoenixMage!~phoenix@> has joined #yocto22:31
RPJPEW: are you around atm? I've found another threading issue. I think I know the answer but...22:32
JPEWSure, I've got a little time22:32
RPJPEW: I think we have a problem with the idle condition we added in that there are actually two things needed for the condition - no idle functions *and* the async command is None22:33
RPWe don't put any locking around the current async command22:33
RPJPEW: this currentAsyncCommand in command.py22:33
RPJPEW: I think the code races at the moment since the idle functions can be empty but the command hasn't been cleared22:34
JPEWAh `# FIXME Add a lock for this`22:34
RPJPEW: heh, yes22:35
RPJPEW: this was a failing log:
RPJPEW: note the second last "Registering idle function" with no "Removing idle function"22:36
RPJPEW: I think we may be able to roll this all under the same lock/condition22:37
JPEWYa, you would want to use the same lock22:38
JPEWFortunately, the condition can be as complex as you need, so you don't necessarily have to _leave_ it locked all the time22:38
RPthe condition is easy, we just check for it being None22:39
JPEWcurrentAsyncCommand == None ?22:39
JPEWerr, `is None`22:39
JPEWI write python, I swear22:39
RPheh, yes, that :)22:40
RPJPEW: should make the code a bit easier to follow too22:40
* RP remembers why we did this and is happy it isn't needed now22:40
JPEWOh, ya, this can be simplifed a lot22:41
*** seninha <seninha!~seninha@user/seninha> has quit IRC (Quit: Leaving)22:45
*** seninha <seninha!~seninha@user/seninha> has joined #yocto22:46
*** BCMM <BCMM!~BCMM@user/bcmm> has quit IRC (Quit: Konversation terminated!)22:49
JPEWRP: Yes, it needs to all be under the same condition variable; it's a little annoying that the state is split between they two classes; that makes it really hard to follow22:52
RPJPEW: yes, I was just cursing that a bit :/22:52
JPEWI was moving currentAsyncCommand to be under ProcessServer() with atomic get/set/clear functions, but I don't know how to get that object in all the calls in `class Command`22:53
JPEWPassed as an argument in runCommand... but not the others22:54
RPJPEW: I think with my patch above we can make it appear to runAsyncCommand as well22:54
RPJPEW: finishAsyncCommand is harder22:57
JPEWRP: I see that22:57
RPJPEW:  is     "buildTargets.needcache = True" the best way to put information against these functions?22:58
RPI was wondering about marking the functions which had return codes or shouldn't have finishAsyncCommand called22:58
JPEWOh, ya, you could put a boolean flag in there like that22:59'll probably need them to return their return code in that case23:01
JPEWRP: Also... buildTargets and buildFile are the only two that *don't* need it?23:01
RPJPEW: right, it isn't straightforward :/. I think we just add the process server to command.Command()23:02
JPEWin __init__ ?23:02
RPJPEW: right, those two are the only ones that don't need it but there is a return code on another23:02
JPEW(as a member)23:02
RPJPEW: yes23:02
JPEWYa, I wasn't sure if that was OK in this case, but that would be the most straight forward way23:02
RPJPEW: there were reasons it once wasn't possible. Not sure now23:02
JPEW... why don't those two call finishAsyncCommand?23:04
RPJPEW: they trigger their own idle loop handlers to be added23:05
RPJPEW: grep for idle in cooker.py23:05
JPEWAh, I see23:05
JPEWAh, and the idle function call finishAsyncCommand when they are done23:06
JPEW.... intersting23:06
RPJPEW: this is what you get to retrofitting server/client split onto really old code23:06
*** manuel1985 <manuel1985!~manuel198@2a02:1748:dd5c:f290:c5b2:fdff:b718:9edf> has joined #yocto23:06
JPEWRP: I have to go, but if you get a change, I can review it, otherwise I can try to cook up something tomorrow23:07
RPJPEW: thanks. I'll see what I can come up with. You at least agree it is likely currently quite broken? :/23:09
*** bps2 <bps2!> has quit IRC (Ping timeout: 252 seconds)23:10
*** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has quit IRC (Ping timeout: 255 seconds)23:13
*** engeugenius <engeugenius!~eugenio@> has joined #yocto23:14
*** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has joined #yocto23:16
*** seninha <seninha!~seninha@user/seninha> has quit IRC (Read error: Connection reset by peer)23:16
*** seninha <seninha!~seninha@user/seninha> has joined #yocto23:17
*** engeugenius <engeugenius!~eugenio@> has quit IRC (Quit: Leaving)23:19
JPEWRP: Seems so23:20
RPJPEW: is my attempt at a patch so far23:21
RPJPEW: there is a ton of cleanup I think we can do elsewhere but I'm not cluttering this change with it23:21
RPJPEW: I've put them on bitbake master-next23:24
*** manuel1985 <manuel1985!~manuel198@2a02:1748:dd5c:f290:c5b2:fdff:b718:9edf> has quit IRC (Ping timeout: 264 seconds)23:31
zeddiiRP: strange question. I updated master to work on my next series. After I did a bitbake core-image-minimal to get a baseline, like I normally do. Whenever I do it again, it is always finding something to build and package. I assume it is related to your latest bitbake changes and maybe something I don't have in my local.conf now ?23:34
RPzeddii: it sounds like a bug :(23:35
*** azcraft <azcraft!~AzCraft@> has quit IRC (Read error: Connection reset by peer)23:35
RPzeddii: always something different or the same thing each time?23:35
zeddiiI can answer that in a bit. I'll let it complete this time and do it again.23:36
RPzeddii: it isn't anything I'm aware of. There was one cache reparsing issue but that was just the cache and reparsing when it shouldn't, not rebuilding23:36
zeddiimaybe the image didn't really complete the first time ? it dropped me back to the prompt. I'll have to watch for that s well.23:37
zeddiisince this is what it found on the 2nd bitbake core-image-minimal23:37
zeddiiwhich seems like a lot.23:37
RPzeddii: you should have a history of build logs in tmp/log/cooker/<MACHINE> FWIW23:39
RPzeddii: those will say what happened in each previous build23:39
RPzeddii: knowing which task is the first to rebuild is the data point we need23:41
*** seninha <seninha!~seninha@user/seninha> has quit IRC (Read error: Connection reset by peer)23:58
*** seninha <seninha!~seninha@user/seninha> has joined #yocto23:59
*** dmoseley <dmoseley!> has quit IRC (Ping timeout: 272 seconds)23:59

Generated by 2.17.2 by Marius Gedminas - find it at!