Thursday, 2024-03-28

*** mattsm <mattsm!~mattsm@104-189-170-210.lightspeed.austtx.sbcglobal.net> has quit IRC (Ping timeout: 268 seconds)00:07
*** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV)00:15
*** Daanct12 <Daanct12!~danct12@user/danct12> has joined #yocto00:59
*** lexano <lexano!~lexano@174.119.69.134> has quit IRC (Ping timeout: 256 seconds)01:02
*** prabhakalad <prabhakalad!~prabhakar@147.161.225.85> has quit IRC (Ping timeout: 260 seconds)01:11
*** prabhakalad <prabhakalad!~prabhakar@147.161.225.85> has joined #yocto01:11
*** Daanct12 <Daanct12!~danct12@user/danct12> has quit IRC (Ping timeout: 264 seconds)01:26
*** Daanct12 <Daanct12!~danct12@user/danct12> has joined #yocto01:28
*** olani- <olani-!~olani@134.238.48.37> has quit IRC (Ping timeout: 268 seconds)01:39
*** davidinux <davidinux!~davidinux@45.11.82.23> has quit IRC (Ping timeout: 268 seconds)02:04
*** davidinux <davidinux!~davidinux@45.11.82.23> has joined #yocto02:04
*** rm5248 <rm5248!~rm5248@c-76-100-95-162.hsd1.va.comcast.net> has quit IRC (Quit: Leaving.)02:08
*** jclsn <jclsn!~jclsn@2a04:4540:6543:4e00:2ce:39ff:fecf:efcd> has quit IRC (Ping timeout: 272 seconds)02:10
*** jclsn <jclsn!~jclsn@2a04:4540:6515:3500:2ce:39ff:fecf:efcd> has joined #yocto02:12
*** Daanct12 <Daanct12!~danct12@user/danct12> has quit IRC (Quit: WeeChat 4.2.1)03:26
*** simonew <simonew!~ile@2a02:810d:a940:35fc:9b82:dc7b:e7d0:af24> has quit IRC (Ping timeout: 256 seconds)03:32
*** raghavgururajan_ <raghavgururajan_!ea769b8000@2a03:6000:1812:100::242> has quit IRC (Ping timeout: 256 seconds)03:33
*** starblue <starblue!~juergen@87.122.38.116> has quit IRC (Ping timeout: 256 seconds)03:35
*** davidinux <davidinux!~davidinux@45.11.82.23> has quit IRC (Ping timeout: 256 seconds)03:36
*** starblue <starblue!~juergen@87.122.38.116> has joined #yocto03:36
*** ablu <ablu!~m-bfyrfh@user/Ablu> has quit IRC (Read error: Connection reset by peer)03:36
*** davidinux <davidinux!~davidinux@45.11.82.23> has joined #yocto03:36
*** raghavgururajan <raghavgururajan!ea769b8000@user/raghavgururajan> has joined #yocto03:36
*** Daanct12 <Daanct12!~danct12@user/danct12> has joined #yocto03:39
*** ablu <ablu!~m-bfyrfh@user/Ablu> has joined #yocto03:41
*** Daanct12 <Daanct12!~danct12@user/danct12> has quit IRC (Ping timeout: 268 seconds)03:45
*** Daanct12 <Daanct12!~danct12@user/danct12> has joined #yocto03:46
*** xmn <xmn!~xmn@pool-108-46-142-76.nycmny.fios.verizon.net> has joined #yocto03:51
*** simonew <simonew!~ile@2a02:810d:a940:35fc:cc7d:fdc2:8d3f:4e71> has joined #yocto03:55
*** simonew <simonew!~ile@2a02:810d:a940:35fc:cc7d:fdc2:8d3f:4e71> has quit IRC (Ping timeout: 255 seconds)04:05
*** starblue <starblue!~juergen@87.122.38.116> has quit IRC (Ping timeout: 272 seconds)04:06
*** starblue <starblue!~juergen@87.122.38.46> has joined #yocto04:07
*** amitk <amitk!~amit@58.84.60.136> has joined #yocto04:07
*** starblue <starblue!~juergen@87.122.38.46> has quit IRC (Ping timeout: 256 seconds)04:17
*** starblue <starblue!~juergen@87.122.126.178> has joined #yocto04:21
*** starblue <starblue!~juergen@87.122.126.178> has quit IRC (Ping timeout: 256 seconds)04:36
*** starblue <starblue!~juergen@87.122.37.186> has joined #yocto04:38
*** xmn <xmn!~xmn@pool-108-46-142-76.nycmny.fios.verizon.net> has quit IRC (Ping timeout: 268 seconds)04:43
*** enok <enok!~Thunderbi@c-da42e655.06-290-73746f71.bbcust.telenor.se> has joined #yocto05:04
*** jmd <jmd!~user@2001:a61:2aa0:ea01:fcec:2373:8649:cf16> has joined #yocto05:15
*** simonew <simonew!~ile@2a02:810d:a940:35fc:bd9d:9f76:64f4:2498> has joined #yocto05:16
*** amitk <amitk!~amit@58.84.60.136> has quit IRC (Remote host closed the connection)05:20
*** amitk <amitk!~amit@58.84.60.136> has joined #yocto05:26
*** simonew <simonew!~ile@2a02:810d:a940:35fc:bd9d:9f76:64f4:2498> has quit IRC (Remote host closed the connection)05:57
*** rburton <rburton!rburton@user/rburton> has quit IRC (Ping timeout: 256 seconds)05:57
*** rburton <rburton!rburton@user/rburton> has joined #yocto06:01
*** davidinux <davidinux!~davidinux@45.11.82.23> has quit IRC (Ping timeout: 256 seconds)06:05
*** davidinux <davidinux!~davidinux@45.11.82.23> has joined #yocto06:08
*** alperak <alperak!uid641238@id-641238.ilkley.irccloud.com> has joined #yocto06:11
*** enok <enok!~Thunderbi@c-da42e655.06-290-73746f71.bbcust.telenor.se> has quit IRC (Ping timeout: 268 seconds)06:12
*** jmd <jmd!~user@2001:a61:2aa0:ea01:fcec:2373:8649:cf16> has quit IRC (Remote host closed the connection)06:13
*** sakman_ <sakman_!~sakman@99.209.85.164> has joined #yocto06:15
*** sakman <sakman!~sakman@208.111.77.233> has quit IRC (Ping timeout: 268 seconds)06:18
*** sakman_ is now known as sakman06:19
*** jmd <jmd!~user@2001:a61:2aa0:ea01:fcec:2373:8649:cf16> has joined #yocto06:19
*** sakman_ <sakman_!~sakman@208.111.77.233> has joined #yocto06:20
*** sakman <sakman!~sakman@99.209.85.164> has quit IRC (Ping timeout: 256 seconds)06:23
*** khem <khem!uid220931@id-220931.helmsley.irccloud.com> has joined #yocto06:23
*** starblue <starblue!~juergen@87.122.37.186> has quit IRC (Ping timeout: 255 seconds)06:44
*** starblue <starblue!~juergen@87.122.126.56> has joined #yocto06:45
*** rob_w <rob_w!~bob@host-82-135-31-73.customer.m-online.net> has joined #yocto06:47
*** Kubu_work <Kubu_work!~kubu@arennes-654-1-262-155.w2-13.abo.wanadoo.fr> has joined #yocto06:57
*** vladest <vladest!~Thunderbi@adsl-89-217-204-83.adslplus.ch> has quit IRC (Ping timeout: 268 seconds)07:04
*** alessioigor <alessioigor!~alessioig@185.178.95.238> has joined #yocto07:08
*** starblue <starblue!~juergen@87.122.126.56> has quit IRC (Ping timeout: 256 seconds)07:23
*** starblue <starblue!~juergen@87.122.126.93> has joined #yocto07:25
*** starblue <starblue!~juergen@87.122.126.93> has quit IRC (Ping timeout: 246 seconds)07:32
*** mckoan|away is now known as mckoan07:34
*** starblue <starblue!~juergen@87.122.37.182> has joined #yocto07:35
*** vladest <vladest!~Thunderbi@217.192.139.41> has joined #yocto07:39
*** mvlad <mvlad!~mvlad@2a02:2f05:850d:7800:331a:a9f1:116:31f7> has joined #yocto07:49
*** tgamblin <tgamblin!~tgamblin@abordeaux-651-1-78-161.w90-5.abo.wanadoo.fr> has joined #yocto07:56
*** rfuentess <rfuentess!~rfuentess@adijon-159-1-11-151.w92-161.abo.wanadoo.fr> has joined #yocto08:04
*** manuel1985 <manuel1985!~manuel198@62.99.131.178> has joined #yocto08:05
*** zpfvo <zpfvo!~fvo@i59F5CFAD.versanet.de> has joined #yocto08:07
*** starblue <starblue!~juergen@87.122.37.182> has quit IRC (Ping timeout: 268 seconds)08:25
*** starblue <starblue!~juergen@87.122.36.3> has joined #yocto08:27
*** rob_w <rob_w!~bob@host-82-135-31-73.customer.m-online.net> has quit IRC (Ping timeout: 256 seconds)08:51
*** prabhakar <prabhakar!~prabhakar@217.163.141.10> has joined #yocto08:56
*** khem <khem!uid220931@id-220931.helmsley.irccloud.com> has quit IRC (Quit: Connection closed for inactivity)08:59
*** leon-anavi <leon-anavi!~Leon@46.55.231.62> has joined #yocto09:00
*** florian <florian!~florian@dynamic-078-049-013-053.78.49.pool.telefonica.de> has joined #yocto09:00
*** tgamblin <tgamblin!~tgamblin@abordeaux-651-1-78-161.w90-5.abo.wanadoo.fr> has quit IRC (Ping timeout: 268 seconds)09:02
*** rob_w <rob_w!~bob@host-82-135-31-73.customer.m-online.net> has joined #yocto09:04
*** enok <enok!~Thunderbi@c-da42e655.06-290-73746f71.bbcust.telenor.se> has joined #yocto09:31
*** tgamblin <tgamblin!~tgamblin@laubervilliers-658-1-213-31.w90-63.abo.wanadoo.fr> has joined #yocto09:37
*** thomas_34 <thomas_34!~thomas_34@host-80-81-12-253.static.customer.m-online.net> has joined #yocto09:41
*** starblue <starblue!~juergen@87.122.36.3> has quit IRC (Ping timeout: 252 seconds)09:48
*** starblue <starblue!~juergen@87.122.36.3> has joined #yocto09:48
*** tgamblin <tgamblin!~tgamblin@laubervilliers-658-1-213-31.w90-63.abo.wanadoo.fr> has quit IRC (Remote host closed the connection)09:58
*** tgamblin <tgamblin!~tgamblin@laubervilliers-658-1-213-31.w90-63.abo.wanadoo.fr> has joined #yocto09:58
*** enok <enok!~Thunderbi@c-da42e655.06-290-73746f71.bbcust.telenor.se> has quit IRC (Ping timeout: 268 seconds)10:07
*** enok <enok!~Thunderbi@94.191.136.31.mobile.tre.se> has joined #yocto10:08
*** jmd <jmd!~user@2001:a61:2aa0:ea01:fcec:2373:8649:cf16> has quit IRC (Remote host closed the connection)10:08
*** jmd <jmd!~user@2001:a61:2aa0:ea01:fcec:2373:8649:cf16> has joined #yocto10:09
*** jmd <jmd!~user@2001:a61:2aa0:ea01:fcec:2373:8649:cf16> has quit IRC (Remote host closed the connection)10:13
*** jmd <jmd!~user@2001:a61:2aa0:ea01:fcec:2373:8649:cf16> has joined #yocto10:14
*** rob_w <rob_w!~bob@host-82-135-31-73.customer.m-online.net> has quit IRC (Remote host closed the connection)10:15
*** rob_w <rob_w!~bob@host-82-135-31-73.customer.m-online.net> has joined #yocto10:17
*** tgamblin_ <tgamblin_!~tgamblin@abordeaux-651-1-78-161.w90-5.abo.wanadoo.fr> has joined #yocto10:24
*** tgamblin <tgamblin!~tgamblin@laubervilliers-658-1-213-31.w90-63.abo.wanadoo.fr> has quit IRC (Ping timeout: 268 seconds)10:25
*** enok <enok!~Thunderbi@94.191.136.31.mobile.tre.se> has quit IRC (Ping timeout: 268 seconds)10:51
*** starblue <starblue!~juergen@87.122.36.3> has quit IRC (Ping timeout: 272 seconds)10:59
*** starblue <starblue!~juergen@87.122.126.117> has joined #yocto11:00
*** xmn <xmn!~xmn@pool-108-46-142-76.nycmny.fios.verizon.net> has joined #yocto11:07
*** flom84 <flom84!~flom84@user/flom84> has joined #yocto11:19
*** prabhakar <prabhakar!~prabhakar@217.163.141.10> has quit IRC (Ping timeout: 255 seconds)11:22
*** jmiehe <jmiehe!~Thunderbi@user/jmiehe> has joined #yocto11:23
*** flom84 <flom84!~flom84@user/flom84> has quit IRC (Remote host closed the connection)11:27
*** starblue <starblue!~juergen@87.122.126.117> has quit IRC (Ping timeout: 256 seconds)11:31
*** lexano <lexano!~lexano@174.119.69.134> has joined #yocto11:31
*** starblue <starblue!~juergen@87.122.126.173> has joined #yocto11:33
*** starblue <starblue!~juergen@87.122.126.173> has quit IRC (Ping timeout: 268 seconds)11:38
*** starblue <starblue!~juergen@87.122.126.30> has joined #yocto11:39
*** florian <florian!~florian@dynamic-078-049-013-053.78.49.pool.telefonica.de> has quit IRC (Ping timeout: 255 seconds)11:55
*** Danct12 <Danct12!~danct12@user/danct12> has quit IRC (Quit: ZNC 1.9.0 - https://znc.in)11:56
*** vladest <vladest!~Thunderbi@217.192.139.41> has quit IRC (Quit: vladest)11:56
*** Danct12 <Danct12!~danct12@user/danct12> has joined #yocto11:59
*** starblue <starblue!~juergen@87.122.126.30> has quit IRC (Ping timeout: 264 seconds)12:05
*** starblue <starblue!~juergen@87.122.126.64> has joined #yocto12:07
*** rob_w <rob_w!~bob@host-82-135-31-73.customer.m-online.net> has quit IRC (Ping timeout: 260 seconds)12:12
*** rm5248 <rm5248!~rm5248@50.58.90.130> has joined #yocto12:27
*** vladest <vladest!~Thunderbi@adsl-89-217-204-83.adslplus.ch> has joined #yocto12:31
*** goliath <goliath!~goliath@user/goliath> has joined #yocto12:42
*** starblue <starblue!~juergen@87.122.126.64> has quit IRC (Ping timeout: 255 seconds)12:49
*** starblue <starblue!~juergen@87.122.126.173> has joined #yocto12:50
*** starblue <starblue!~juergen@87.122.126.173> has quit IRC (Ping timeout: 256 seconds)12:58
*** starblue <starblue!~juergen@87.122.126.24> has joined #yocto12:59
*** florian <florian!~florian@dynamic-078-049-013-053.78.49.pool.telefonica.de> has joined #yocto13:04
rm5248Has anybody seen random build failures before when building the eSDK?  My eSDK builds keep failing on my build server, but I'm wondering if it's something to do with resources.  I'm trying a build now by lowering BB_NUMBER_THREADS to see if that makes it more reliable13:04
*** starblue <starblue!~juergen@87.122.126.24> has quit IRC (Ping timeout: 255 seconds)13:04
*** starblue <starblue!~juergen@87.122.39.66> has joined #yocto13:06
rm5248Most of the time the failure results in a pseudo abort failure with a path mismatch on a .ipk file, but one time it failed during the tar process(File removed before we read it), where the file the symlink was pointing to did not exist13:06
*** starblue <starblue!~juergen@87.122.39.66> has quit IRC (Ping timeout: 246 seconds)13:15
*** florian <florian!~florian@dynamic-078-049-013-053.78.49.pool.telefonica.de> has quit IRC (Ping timeout: 255 seconds)13:18
*** enok <enok!~Thunderbi@c-da42e655.06-290-73746f71.bbcust.telenor.se> has joined #yocto13:28
*** Daanct12 <Daanct12!~danct12@user/danct12> has quit IRC (Quit: WeeChat 4.2.1)13:30
*** Starfoxxes <Starfoxxes!~Starfoxxe@2a02:8070:5381:8b40:774e:f62c:f37f:e2ab> has quit IRC (Ping timeout: 272 seconds)13:34
*** starblue <starblue!~juergen@87.122.126.47> has joined #yocto13:38
*** bunk <bunk!~bunk@debian/bunk> has joined #yocto13:39
*** vladest1 <vladest1!~Thunderbi@adsl-89-217-204-83.adslplus.ch> has joined #yocto13:46
*** vladest <vladest!~Thunderbi@adsl-89-217-204-83.adslplus.ch> has quit IRC (Ping timeout: 264 seconds)13:47
*** vladest1 is now known as vladest13:47
RPrm5248: that sounds like files being rmoved out of pseudo's context so I doubt its a resource problem, more an intermittent race13:55
rm5248If it is an intermittent race though, I'm wondering if it's because there are /too many/ resources(e.g. threads) running.  I wasn't sure if it could have something to do with ulimits14:00
*** rfs613 <rfs613!~rfs613@bras-base-otwaon1102w-grc-09-184-147-116-200.dsl.bell.ca> has quit IRC (Ping timeout: 260 seconds)14:04
*** rfs613 <rfs613!~rfs613@184.147.116.200> has joined #yocto14:05
RPrm5248: path mismatch pseudo aborts are not resource problems14:08
RPI say this as someone who worked on that pseudo code14:08
*** florian <florian!~florian@dynamic-078-049-013-053.78.49.pool.telefonica.de> has joined #yocto14:09
rm5248ah.  what might cause a path mismatch?  It seems to affect different packages14:15
*** Xagen <Xagen!~Xagen@098-006-114-013.biz.spectrum.com> has joined #yocto14:21
RPrm5248: imagine pseudo things "a" and inode 123 are the same file. Imagine something deletes "a" outside of pseudo and then creates "b" which the kernel gives inode 123. Then you view "b" under pseudo14:21
RPs/things/thinks/14:22
rm5248So the likely cause is that there is a rogue process of some kind deleting files in the yocto build folder?  Is that correct?14:27
frayor your build folder is on a filesystem w/o persistent inodes14:28
fraypseudo inode mismatch is almost always a real bug somewhere in the code (outside of pseudo).  The only other time I've seen it is on a filesystem that doesn't have persistent inodes (like NFS).14:28
rm5248Unfortunately I don't really know how that helps.  The build is failing on an ubuntu 22.04 machine, it is using ext4.  The one potential odd thing about it is that it runs on an EC2 instance, so I'm not sure if AWS could be doing something special14:35
frayI don't have much experience w/ building on EC2, was always too expensive to play with it.   With that said, the normal cause if it says the filesystem is ext4, there is something running that is NOT in pseudo context that is manipulating files (which removes or changes their inode in some way)..   I've seen this happen w/ scripts that run to copy something in and end up overwriting existing files..  these14:37
frayscripts would be outside the normal YP recipe context.14:37
fullstopI'm adding a package in my yocto layer, and it builds with cmake.  I can build it with the sdk generated from yocto, but not from within yocto itself, and I'm hoping that someone here knows where I've gone astray.14:40
rburtonfullstop: does your recipe just inherit cmake and almost do nothing else?14:41
fullstopIt's not finding simple includes, such as unistd.h, so it's likely not finding the sysroot14:41
rburtonif you inherit cmake then congratulations you've got a broken cmakelists.txt14:41
fullstopit inherits cmake and adds a do_install14:41
rburtoncmake has a do_install, so you only need that if your cmakelists don't know how to install14:42
frayAll I can sugges tis be sure to use the cmake class.  It sounds like not finding unistd.h means that your software isn't invoking everything with $CC (from the environment), often ends up with hard coded gcc, which isn't right..14:42
fullstopit does not know how to install14:42
fraythe value of $CC from the environment contains the references to the header files14:42
rburtonfullstop: but the usual problem is that the cmakelists.txt thinks its okay to overwrite CMAKE_C_FLAGS or something, when it should be appending14:42
fullstopThe log shows the appropriate compiler, so I believe it to be using $CC14:42
rburtondoes it show the compiler passing --sysroot?14:43
fullstopoh, wait I think that I see it.14:43
fullstopthere is a SET(CMAKE_CXX_FLAGS) which is wrong.14:43
fullstopmy apologies, I should have seen that.14:43
rburtonthat would be it14:44
*** sotaoverride <sotaoverride!~ctraven@139.68.81.2> has quit IRC (Killed (copper.libera.chat (Nickname regained by services)))14:44
*** sotaover1ide is now known as sotaoverride14:44
*** enok <enok!~Thunderbi@c-da42e655.06-290-73746f71.bbcust.telenor.se> has quit IRC (Ping timeout: 268 seconds)14:44
rburtonfray: cmake is 'fun' and demands that the compiler argument is just the binary, so we have to pass sysroot through CMAKE_C_CFLAGS etc.14:44
fullstop....and built.14:45
frayas I've said for years.. cmake is "broken by design"14:45
rburtonabsolutely14:45
rburtonterrible build system14:45
fullstopguess I'll go back to gnu make.  :-)14:45
rburtonfullstop: also terrible14:45
rburtonmeson14:45
fullstopone of these years14:45
thomas_34what? why is cmake terrible? I'm have to use it since years... :S14:46
rburtonthomas_34: my main reason is that it basically hates the idea of cross compiling, ironically14:46
rburtonwell its also got hundreds of other flaws, but thats the dealbreaker14:46
thomas_34Huh? I'm using it to compile my stuff for 4 different architectures?14:47
rburtonthomas_34: can you build a binary in your cmake that you run on the build machine whilst cross-compiling?14:47
*** enok <enok!~Thunderbi@c-da42e655.06-290-73746f71.bbcust.telenor.se> has joined #yocto14:47
rburtoncmake _can_ cross, it's just that its horrible14:47
rburtonhttps://mesonbuild.com/Cross-compilation.html#mixing-host-and-build-targets <-- how meson does "build me a native binary so I can run it during the build"14:49
*** ThomasRoos <ThomasRoos!~ThomasRoo@ip5b43ff2a.dynamic.kabel-deutschland.de> has joined #yocto14:49
thomas_34well... I don't know what you mean exactly - but yes. I have a toolchain-definition for every architecture (also for build machine for example) and just build the stuff14:49
rburtonso you have a project. you have a small xcode generator written in C that you need to compile with the native compiler and then run, and that produces code that you then cross-compile14:50
rburton(not sure where that x came from)14:50
zeddiiI can't get past the sea of incomprehensible includes and mixed functions. but it shares that issue with every other build framework.14:51
rburtoncmake's solution is https://cmake.org/cmake/help/book/mastering-cmake/chapter/Cross%20Compiling%20With%20CMake.html#running-executables-built-in-the-project which is yucky14:51
frayevery cmake implementation I've seen, people end up hard coding compiler definitions into it, cause using the environment or other standard is too difficult..  GNU make people do similar, but in those cases it's often easier for me to just remove the offending lines and everything works.. but in cmake remove lines and the next bit breaks.. it's a horrible mess..14:51
thomas_34Actually, I'm kinda have something like this. I define that in a extra cmake task and execute that.14:51
frayI've never used meson for any development, so I've no comment there..14:51
ThomasRoosrm5248 I build with EC2 - using https://github.com/aws4embeddedlinux/meta-aws-buildbot - that works great14:52
JaMaevery build system is terrible, I'm looking forward for AI to skip the source code completely and pulling executable binaries from pixie dust14:53
fraypixie dust = dubious plagerism.. YEP14:54
rm5248ThomasRoos: Thanks, I will check it out.  Do you build the eSDK at all when you build?  The build works fine apart from that14:54
thomas_34rburton, I just know cmake for c/c++. I don't know if anything else does a better job for particular thingy but I'm so far impressed what you can do with that.14:54
rburtonthomas_34: meson is much better :)14:54
ThomasRoosrm5248 - no did miss that information - I do not use eSDK at all by now.14:55
JaMafray: I was just joking, but if it makes my threadripper to spit out real unicorns, then my kids will be happier with my work14:55
fraylol I don't have an issue with 'ai', especially in helping coding.. BUT I have a huge problem with the way Microsoft and others have trained their AI against open source and other people's work w/o any attribution or paying attention to licensing..14:56
fullstopOne other question, as I'm moving things from dunfell to mickledore.. it looks like SRCREV pointing to a tag is no longer accepted.  Do I really have to figure out the commit sha instead of using a tag?14:56
frayyou always have had to use the sha directly..  if tag worked before it was not intentional14:57
JaMawhy moving from one EOL LTS release to different EOL release and not-LTS?14:57
fullstopbecause bsp14:57
frayreason being, only the sha is deterministic/reproducible..  a tag can move, a branch can move, etc.14:57
*** florian <florian!~florian@dynamic-078-049-013-053.78.49.pool.telefonica.de> has quit IRC (Ping timeout: 240 seconds)14:58
frayya, mickledore is very much dead at this point.. nanbield and upcoming scarthgap is what most people should be targeting.. (nanbield as a stepping stone to scarthgap)14:58
fullstopI'm kind of at the mercy of NXP at the moment14:59
JaMafullstop: using tag "worked" by using git ls-remote while parsing to convert tag name to sha, now it asks you to convert it yourself in advance to make it more reliable (when tag moves) and to avoid network access to remote repos while parsing (as it cannot be resolved in DL_DIR)14:59
*** enok <enok!~Thunderbi@c-da42e655.06-290-73746f71.bbcust.telenor.se> has quit IRC (Ping timeout: 260 seconds)15:00
fullstopI'll have to be careful, I guess. I could bump packages by git mv before, but now I need to edit the recipe and supply the sha.15:00
fullstopIt's not horrible, but I need to be careful.15:00
JaMafor our components in webOS we extend this _after_the_do_fetch_ to check that the SHA matches with expected tag name in the repo15:00
fraywe use scripting here to update recipes automatically..  loads the 'next sha' (from a set of rules we have) and then automatically updates the recipes, verifies they build and checks them in..15:00
fullstopThat's probably worth doing.  I could see the tag name not matching the sha.15:01
frayya, we only tag after release.. during development we have a next and stable branch, and again automation rules on promoting code15:01
*** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Ping timeout: 268 seconds)15:03
*** Vonter <Vonter!~Vonter@user/vonter> has joined #yocto15:03
*** khem <khem!uid220931@id-220931.helmsley.irccloud.com> has joined #yocto15:09
*** wacke <wacke!~user1@82.220.33.162> has joined #yocto15:19
*** simonew <simonew!~ile@2a02:810d:a940:35fc:26aa:5f0f:3295:11dc> has joined #yocto15:21
wackedear all, doc[1] says tc.d is the bitbake datastore, but when i try to use it i get: 'OERuntimeTestContext' object has no attribute 'd', [1] https://docs.yoctoproject.org/dev/dev-manual/runtime-testing.html#class-attributes15:21
wackeanyone an idea what is wrong?15:22
*** rfuentess <rfuentess!~rfuentess@adijon-159-1-11-151.w92-161.abo.wanadoo.fr> has quit IRC (Remote host closed the connection)15:24
simonewHi, is this in a situation where testimage class is inherited?15:28
wackeyes15:28
*** rfuentess <rfuentess!~rfuentess@adijon-159-1-11-151.w92-161.abo.wanadoo.fr> has joined #yocto15:29
wackei start the test with bitbake -c testimage <image-name>15:32
*** enok <enok!~Thunderbi@c-da42e655.06-290-73746f71.bbcust.telenor.se> has joined #yocto15:33
wackecalling datastore like this:15:34
wacke        cls.swupdate_target = cls.tc.target.ip+':8888'15:34
wackeups, wrong line15:34
wacke    @classmethod15:34
wacke    def setUpClass(cls):15:34
wacke        cls.deploy_dir_image = cls.tc.d.getVar("DEPLOY_DIR_IMAGE")15:34
simonewoeRuntimeTest vs  OERuntimeTestContext Seems there are two similiar named clases15:37
simonewIs cls correct done?15:38
wackehmm, i inherit OERuntimeTestCase15:40
wacketried with oeRuntimeTest (by guess), got an error: AttributeError: type object 'oeRuntimeTest' has no attribute 'tc'15:41
wackeok, thx for your help so far simonew, i'm afk now, if anyone has some ideas, please write, i'll check later15:43
*** 082AAVV6M <082AAVV6M!~Tyaku@bub62-h03-89-84-109-199.dsl.sta.abo.bbox.fr> has joined #yocto15:45
*** ThomasRoos <ThomasRoos!~ThomasRoo@ip5b43ff2a.dynamic.kabel-deutschland.de> has quit IRC (Quit: Client closed)15:56
*** simonew <simonew!~ile@2a02:810d:a940:35fc:26aa:5f0f:3295:11dc> has quit IRC (Remote host closed the connection)16:04
*** simonew <simonew!~ile@2a02:810d:a940:35fc:d2c:f96d:dbaa:8201> has joined #yocto16:04
*** enok <enok!~Thunderbi@c-da42e655.06-290-73746f71.bbcust.telenor.se> has quit IRC (Ping timeout: 255 seconds)16:06
*** 082AAVV6M <082AAVV6M!~Tyaku@bub62-h03-89-84-109-199.dsl.sta.abo.bbox.fr> has quit IRC (Quit: Lost terminal)16:13
*** rfuentess <rfuentess!~rfuentess@adijon-159-1-11-151.w92-161.abo.wanadoo.fr> has quit IRC (Read error: Connection reset by peer)16:14
*** tgamblin_ is now known as tgamblin16:19
*** noyez <noyez!~noyez@pool-74-104-154-58.bstnma.fios.verizon.net> has joined #yocto16:20
*** vladest <vladest!~Thunderbi@adsl-89-217-204-83.adslplus.ch> has quit IRC (Remote host closed the connection)16:30
*** tgamblin <tgamblin!~tgamblin@abordeaux-651-1-78-161.w90-5.abo.wanadoo.fr> has quit IRC (Quit: Leaving)16:31
*** zpfvo <zpfvo!~fvo@i59F5CFAD.versanet.de> has quit IRC (Remote host closed the connection)16:33
*** zpfvo <zpfvo!~fvo@i59F5CFAD.versanet.de> has joined #yocto16:33
*** vladest <vladest!~Thunderbi@adsl-89-217-204-83.adslplus.ch> has joined #yocto16:34
*** Starfoxxes <Starfoxxes!~Starfoxxe@2a02:8070:5381:8b40:ba73:27d:9373:f502> has joined #yocto16:40
*** thomas_34 <thomas_34!~thomas_34@host-80-81-12-253.static.customer.m-online.net> has quit IRC (Ping timeout: 250 seconds)16:53
*** starblue <starblue!~juergen@87.122.126.47> has quit IRC (Ping timeout: 260 seconds)16:56
*** vladest <vladest!~Thunderbi@adsl-89-217-204-83.adslplus.ch> has quit IRC (Remote host closed the connection)16:59
*** starblue <starblue!~juergen@87.122.36.148> has joined #yocto17:00
*** zpfvo <zpfvo!~fvo@i59F5CFAD.versanet.de> has quit IRC (Quit: Leaving.)17:03
*** rm5248 <rm5248!~rm5248@50.58.90.130> has quit IRC (Ping timeout: 260 seconds)17:09
*** mckoan is now known as mckoan|away17:15
*** manuel1985 <manuel1985!~manuel198@62.99.131.178> has quit IRC (Ping timeout: 268 seconds)17:22
*** rm5248 <rm5248!~rm5248@50.58.90.130> has joined #yocto17:23
*** vladest <vladest!~Thunderbi@adsl-89-217-204-83.adslplus.ch> has joined #yocto17:26
*** starblue <starblue!~juergen@87.122.36.148> has quit IRC (Ping timeout: 246 seconds)17:39
*** jmiehe <jmiehe!~Thunderbi@user/jmiehe> has quit IRC (Quit: jmiehe)17:41
*** starblue <starblue!~juergen@87.122.126.56> has joined #yocto17:41
*** prabhakarlad <prabhakarlad!~prabhakar@217.163.141.10> has joined #yocto17:42
*** leon-anavi <leon-anavi!~Leon@46.55.231.62> has quit IRC (Quit: Leaving)17:42
*** starblue <starblue!~juergen@87.122.126.56> has quit IRC (Ping timeout: 255 seconds)17:49
*** starblue <starblue!~juergen@87.122.126.25> has joined #yocto17:51
*** leon-anavi <leon-anavi!~Leon@46.55.231.62> has joined #yocto17:51
*** leon-anavi <leon-anavi!~Leon@46.55.231.62> has quit IRC (Client Quit)17:52
*** simonew <simonew!~ile@2a02:810d:a940:35fc:d2c:f96d:dbaa:8201> has quit IRC (Ping timeout: 268 seconds)18:05
*** starblue <starblue!~juergen@87.122.126.25> has quit IRC (Ping timeout: 256 seconds)18:06
*** starblue <starblue!~juergen@87.122.126.37> has joined #yocto18:08
*** florian <florian!~florian@dynamic-078-049-013-053.78.49.pool.telefonica.de> has joined #yocto18:17
*** geoffhp <geoffhp!~geoff@023-241-067-081.res.spectrum.com> has joined #yocto18:35
*** prabhakar <prabhakar!~prabhakar@217.163.141.10> has joined #yocto18:35
*** enok <enok!~Thunderbi@c-da42e655.06-290-73746f71.bbcust.telenor.se> has joined #yocto18:36
*** florian <florian!~florian@dynamic-078-049-013-053.78.49.pool.telefonica.de> has quit IRC (Ping timeout: 272 seconds)18:40
*** mvlad <mvlad!~mvlad@2a02:2f05:850d:7800:331a:a9f1:116:31f7> has quit IRC (Remote host closed the connection)18:46
*** amitk <amitk!~amit@58.84.60.136> has quit IRC (Ping timeout: 268 seconds)18:54
*** amitk <amitk!~amit@58.84.62.242> has joined #yocto19:11
*** starblue <starblue!~juergen@87.122.126.37> has quit IRC (Ping timeout: 268 seconds)19:15
*** rm5248 <rm5248!~rm5248@50.58.90.130> has quit IRC (Quit: Leaving.)19:19
*** Saur_Home85 <Saur_Home85!~Saur_Home@94-137-113-31.customers.ownit.se> has quit IRC (Quit: Client closed)19:20
*** Saur_Home85 <Saur_Home85!~Saur_Home@94-137-113-31.customers.ownit.se> has joined #yocto19:20
noyezHi -- i use `source poke/oe-init-build-env` to source the the needed variables. Is there a way to "unsource" those variables, i.e. i want to get back my previous shell. is that possible with completely exiting the shell? thx.19:21
*** starblue <starblue!~juergen@87.122.37.162> has joined #yocto19:22
*** paw <paw!~afong@198-84-204-38.cpe.teksavvy.com> has quit IRC (Ping timeout: 264 seconds)19:40
*** starblue <starblue!~juergen@87.122.37.162> has quit IRC (Ping timeout: 268 seconds)19:43
*** florian <florian!~florian@dynamic-078-049-013-053.78.49.pool.telefonica.de> has joined #yocto19:45
*** starblue <starblue!~juergen@87.122.39.101> has joined #yocto19:45
*** starblue <starblue!~juergen@87.122.39.101> has quit IRC (Ping timeout: 268 seconds)19:58
*** DvorkinDmitry <DvorkinDmitry!~dvorkin@5.167.98.73> has joined #yocto20:01
*** starblue <starblue!~juergen@87.122.39.101> has joined #yocto20:05
DvorkinDmitryI need an advice. I have 32GB RAM and 12/24 cores/threads now with Ryzen 7900. My build speed is good, but I'm thinking about adding more memory. What is your opinion, will it increase the build speed and how much If I'll add 32GB? How much memory would you recommend? (I saw 2GB core recommendation).20:06
DvorkinDmitryI'm watching at my build with TOP command and I see at the most hard steps (php/mysql/nodejs build it runs one or two tasks in parallel only and memory is mostly taken (80%) by the HDD cache.20:07
rburtonDvorkinDmitry: as much as you can afford20:10
rburtonDvorkinDmitry: if you can, 128gb would be great20:10
rburtonbut watch the memory usage during a build to see if you'll actually get any use from it20:10
DvorkinDmitryrburton, will it speedup my build and how much, do you think?20:10
rburtonabout fix googleflips20:10
rburtonthat's unknowable20:10
rburtonwatch memory usage during a build, see how much of your ram is disk cache and how much is actually spare20:11
DvorkinDmitryrburton, by looking at TOP output I see at the most hardest build steps it uses 80% of RAM for hdd cache...20:11
rburtonif you swap at all, then more ram would help. if you have no free ram and its all cache then more ram means more cache20:11
*** prabhakalad <prabhakalad!~prabhakar@147.161.225.85> has quit IRC (Quit: Konversation terminated!)20:12
*** prabhakalad <prabhakalad!~prabhakar@147.161.225.85> has joined #yocto20:12
DvorkinDmitryrburton, I do not use the SWAP at my build machine20:12
rburtondepending on budget then 64 or 128.  unless you can borrow ram you'll never know in advance how much - if any - improvement you'll get20:13
rburtonyou might be entirely IO bound, for example20:13
rburtona fast nvme disk makes a massive difference20:13
DvorkinDmitryrburton, I'm using the fastest ssd available, so my IO is not a problem20:13
rburtonnvme or sata ssd?20:14
DvorkinDmitrynvme20:14
rburtonIO is _always_ a problem, it's the slowest thing on a computer20:14
DvorkinDmitryI know, that's why I'm using ssd gen420:14
rburtonwe need a wiki page for standardised build time reporting20:15
rburtonreport your ram, processor, storage, standardised kirkstone core-image-sato build time20:16
rburton(personal record: 22 minutes)20:16
DvorkinDmitryI'm just thinking about the RAM size influece on such tasks as mysql/php/nodejs build. Case I see it does everything else in 24 threads in parallel, but the mysql or php or nodejs build is running along20:16
DvorkinDmitryrburton, ok. I'll do the test20:17
rburtonmy ghetto benchmark is literally git clone -b kirkstone https://git.yoctoproject.org/poky; cd poky; . oe-init-build-env; bitbake core-image-sato --runall fetch ; time bitbake core-image-sato20:18
rburtonno tuning for processor count, fetch first, time build20:18
rburtonsuper dumb but also repeatable trivially20:18
*** jmd <jmd!~user@2001:a61:2aa0:ea01:fcec:2373:8649:cf16> has quit IRC (Remote host closed the connection)20:18
rburtonthe 22 minutes was a beefy threadripper with 256gb ram and very fast nvme.  it did a sato from sstate in about 40 seconds.20:19
DvorkinDmitryrburton, started!20:19
moto-timorburton: we need to include PCIe bus generation and MoBo bus speeds (memory, etc.). These are the things that start making an old dual Xeon look like a waste of time.20:47
* moto-timo stares at the Broadwell era dual Xeon (total of 12C/24T) with the dead spinning rust.20:48
* moto-timo gives it the evil eye.20:48
moto-timoSome kind of peak electricity usage would also be a valuable insight in our modern life. Extra disks cost extra power consumption ;)20:50
moto-timoBBOPS/Watt my new metric :)20:51
*** alessioigor <alessioigor!~alessioig@185.178.95.238> has quit IRC (Quit: alessioigor)20:53
*** starblue <starblue!~juergen@87.122.39.101> has quit IRC (Ping timeout: 268 seconds)21:00
*** starblue <starblue!~juergen@87.122.39.101> has joined #yocto21:03
*** noyez <noyez!~noyez@pool-74-104-154-58.bstnma.fios.verizon.net> has quit IRC (Ping timeout: 250 seconds)21:05
*** alperak <alperak!uid641238@id-641238.ilkley.irccloud.com> has quit IRC (Quit: Connection closed for inactivity)21:10
*** wacke <wacke!~user1@82.220.33.162> has quit IRC (Ping timeout: 256 seconds)21:11
*** Xagen <Xagen!~Xagen@098-006-114-013.biz.spectrum.com> has quit IRC (Ping timeout: 268 seconds)21:22
khemNVME SSDs consume more power than a spinning rust so you are good Moro-timo on that front at least21:26
mischiefmoto-timo: some PSUs do provide power monitoring21:30
mischieffrom what i've seen they can give pretty detailed info on each power rail, but you could also just get a cheap smart plug if you only wanted to see V/A/W21:32
*** starblue <starblue!~juergen@87.122.39.101> has quit IRC (Ping timeout: 268 seconds)21:35
JaMapower total: 112.00 W21:36
JaMapower +12v:   72.00 W21:36
JaMapower +5v:    24.00 W21:36
JaMapower +3.3v:  17.50 W21:36
JaMaand this is idle threadripper21:36
JaMaLoad average: 0.04 0.03 0.0021:36
*** starblue <starblue!~juergen@87.122.126.236> has joined #yocto21:37
DvorkinDmitryRyzen 7900, RAM: 32GB, SSD gen4 core-image-sato: 45m 40 s21:38
JaMawith amd_pstate fix backported to properly lower consumption when idle21:38
JaManot bad, but core-image-sato is "tiny" target :)21:39
*** rm5248 <rm5248!~rm5248@50.58.90.130> has joined #yocto21:39
JaMaand https://github.com/shr-project/test-oe-build-time is a bit extreme (to simulate our bigger builds with just publicly available recipes)21:40
DvorkinDmitryrburton, Ryzen 7900, RAM: 32GB, SSD gen4 core-image-sato: 45m 40 s. hdd cache in RAM is about 22GB, no swap.21:41
DvorkinDmitryis there are any published results?21:41
*** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Ping timeout: 256 seconds)21:42
*** Vonter <Vonter!~Vonter@user/vonter> has joined #yocto21:43
DvorkinDmitryI mean cpu-ram-hdd-time table?21:43
*** starblue <starblue!~juergen@87.122.126.236> has quit IRC (Ping timeout: 256 seconds)21:44
DvorkinDmitryah, I see. there are the link to goodle doc21:45
rburtonJaMa 112W idle? That’s more than our entire house idling!21:48
JaMarburton: POW  20 / 350 W from it is the gpu21:50
*** starblue <starblue!~juergen@87.122.38.137> has joined #yocto21:52
JaMasaves 4W if I stop sddm.service :)21:52
*** rm5248 <rm5248!~rm5248@50.58.90.130> has quit IRC (Quit: Leaving.)21:52
*** DvorkinDmitry <DvorkinDmitry!~dvorkin@5.167.98.73> has quit IRC (Quit: KVIrc 5.0.0 Aria http://www.kvirc.net/)21:54
*** olani- <olani-!~olani@78-70-50-116-no2811.tbcn.telia.com> has joined #yocto21:56
RPrburton: https://autobuilder.yoctoproject.org/typhoon/#/builders/20/builds/9184/steps/12/logs/stdio :(22:00
RPbut the glib fix wasn't in that build? :/22:02
RPI wonder if that was ntp doing something22:03
*** Kubu_work <Kubu_work!~kubu@arennes-654-1-262-155.w2-13.abo.wanadoo.fr> has quit IRC (Quit: Leaving.)22:03
moto-timoI don't need no stinking GPU.22:21
moto-timolol22:21
JPEWHeh, the "basic" SPDX 3 for the Linux Kernel from Yocto is 1.2 MB; 99% of that is reporting the CVE22:24
JPEWCVEs22:24
*** starblue <starblue!~juergen@87.122.38.137> has quit IRC (Ping timeout: 268 seconds)22:47
*** starblue <starblue!~juergen@87.122.37.160> has joined #yocto22:49
*** simonew <simonew!~ile@2a02:810d:a940:35fc:7a2d:3af5:c552:873f> has joined #yocto22:56
RPJPEW: nice, ouch :)22:56
*** simonew <simonew!~ile@2a02:810d:a940:35fc:7a2d:3af5:c552:873f> has quit IRC (Ping timeout: 272 seconds)23:01
jwinarskIs beaglebone-yocto in master expected to work with GPU?  Running a vanilla core-image-weston image, weston fails to load with: `failed to create gbm surface`23:07
*** starblue <starblue!~juergen@87.122.37.160> has quit IRC (Ping timeout: 255 seconds)23:10
*** starblue <starblue!~juergen@87.122.39.169> has joined #yocto23:12
jwinarskweston is reporting `GL renderer: softpipe` prior to the error23:13
*** olani- <olani-!~olani@78-70-50-116-no2811.tbcn.telia.com> has quit IRC (Ping timeout: 252 seconds)23:14
*** jmiehe <jmiehe!~Thunderbi@user/jmiehe> has joined #yocto23:23
*** jmiehe <jmiehe!~Thunderbi@user/jmiehe> has quit IRC (Quit: jmiehe)23:31
*** starblue <starblue!~juergen@87.122.39.169> has quit IRC (Ping timeout: 255 seconds)23:38
*** starblue <starblue!~juergen@87.122.39.169> has joined #yocto23:41
*** enok <enok!~Thunderbi@c-da42e655.06-290-73746f71.bbcust.telenor.se> has quit IRC (Ping timeout: 268 seconds)23:57

Generated by irclog2html.py 4.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!