| *** lexano <lexano!~lexano@174.119.69.134> has quit IRC (Ping timeout: 245 seconds) | 00:30 | |
| *** DvorkinDmitry <DvorkinDmitry!~dvorkin@5.167.98.73> has quit IRC (Quit: KVIrc 5.0.0 Aria http://www.kvirc.net/) | 00:35 | |
| *** davidinux <davidinux!~davidinux@194.34.233.222> has quit IRC (Ping timeout: 245 seconds) | 01:03 | |
| *** Wouter0100670440 <Wouter0100670440!~Wouter010@entry.nbg.netvos.nl> has quit IRC (Quit: The Lounge - https://thelounge.chat) | 01:06 | |
| *** Wouter0100670440 <Wouter0100670440!~Wouter010@entry.nbg.netvos.nl> has joined #yocto | 01:07 | |
| *** davidinux <davidinux!~davidinux@host-87-9-16-97.retail.telecomitalia.it> has joined #yocto | 01:10 | |
| *** khem <khem!uid220931@id-220931.helmsley.irccloud.com> has quit IRC (Quit: Connection closed for inactivity) | 01:20 | |
| *** Ablu <Ablu!~Ablu@user/Ablu> has quit IRC (Ping timeout: 246 seconds) | 01:31 | |
| *** Ablu <Ablu!~Ablu@user/Ablu> has joined #yocto | 01:33 | |
| *** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV) | 01:37 | |
| *** jclsn <jclsn!~jclsn@2a04:4540:6533:6700:2ce:39ff:fecf:efcd> has quit IRC (Ping timeout: 245 seconds) | 02:23 | |
| *** jclsn <jclsn!~jclsn@2a04:4540:653a:de00:2ce:39ff:fecf:efcd> has joined #yocto | 02:25 | |
| *** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Ping timeout: 246 seconds) | 02:41 | |
| *** Vonter <Vonter!~Vonter@user/vonter> has joined #yocto | 02:43 | |
| *** tgamblin <tgamblin!~tgamblin@2001:1970:5b1f:ab00:71eb:b8e9:8589:9ca5> has quit IRC (Ping timeout: 248 seconds) | 03:09 | |
| *** amitk <amitk!~amit@58.84.61.208> has joined #yocto | 03:52 | |
| *** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Ping timeout: 260 seconds) | 04:55 | |
| *** Vonter <Vonter!~Vonter@user/vonter> has joined #yocto | 04:56 | |
| *** davidinux <davidinux!~davidinux@host-87-9-16-97.retail.telecomitalia.it> has quit IRC (Ping timeout: 248 seconds) | 04:58 | |
| *** davidinux <davidinux!~davidinux@194.34.233.25> has joined #yocto | 04:59 | |
| *** Marmottus <Marmottus!~marmottus@2001:bc8:1820:2715::1> has quit IRC (Quit: The Lounge - https://thelounge.chat) | 05:03 | |
| *** camus <camus!~Instantbi@58.246.136.203> has quit IRC (Read error: Connection reset by peer) | 05:30 | |
| *** camus1 <camus1!~Instantbi@58.246.136.203> has joined #yocto | 05:30 | |
| *** camus1 is now known as camus | 05:33 | |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto | 05:53 | |
| *** manuel_ <manuel_!~manuel198@2a02:1748:dd5c:f290:2c48:2c2f:7902:cd27> has joined #yocto | 06:01 | |
| *** manuel1985 <manuel1985!~manuel198@2a02:1748:dd5c:f290:2c48:2c2f:7902:cd27> has quit IRC (Remote host closed the connection) | 06:02 | |
| *** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has quit IRC (Remote host closed the connection) | 06:05 | |
| *** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has joined #yocto | 06:05 | |
| *** Herrie <Herrie!~Herrie@110-31-146-85.ftth.glasoperator.nl> has quit IRC (Ping timeout: 255 seconds) | 06:05 | |
| *** ecdhe_ <ecdhe_!~ecdhe@user/ecdhe> has quit IRC (Ping timeout: 246 seconds) | 06:10 | |
| *** ecdhe <ecdhe!~ecdhe@user/ecdhe> has joined #yocto | 06:17 | |
| *** wooosaiiii1 <wooosaiiii1!~Thunderbi@89-212-21-243.static.t-2.net> has joined #yocto | 06:18 | |
| *** ajfriesen84730 <ajfriesen84730!~ajfriesen@p5b27ab3c.dip0.t-ipconnect.de> has joined #yocto | 06:18 | |
| *** Wenqing_ <Wenqing_!~wenqingzo@78.40.148.178> has joined #yocto | 06:20 | |
| *** mckoan_ <mckoan_!~marco@host-95-229-48-41.business.telecomitalia.it> has joined #yocto | 06:21 | |
| *** hrberg_ <hrberg_!~quassel@171.79-160-161.customer.lyse.net> has joined #yocto | 06:21 | |
| *** Vonter_ <Vonter_!~Vonter@user/vonter> has joined #yocto | 06:23 | |
| *** xmn_ <xmn_!~xmn@2600:4040:9390:8c00:96c:839a:49cb:654a> has joined #yocto | 06:24 | |
| *** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (*.net *.split) | 06:25 | |
| *** hrberg <hrberg!~quassel@171.79-160-161.customer.lyse.net> has quit IRC (*.net *.split) | 06:25 | |
| *** xmn <xmn!~xmn@pool-71-105-152-109.nycmny.fios.verizon.net> has quit IRC (*.net *.split) | 06:25 | |
| *** mckoan|away <mckoan|away!~marco@host-95-229-48-41.business.telecomitalia.it> has quit IRC (*.net *.split) | 06:25 | |
| *** wooosaiiii <wooosaiiii!~Thunderbi@89-212-21-243.static.t-2.net> has quit IRC (*.net *.split) | 06:25 | |
| *** Wenqing <Wenqing!~wenqingzo@78.40.148.178> has quit IRC (*.net *.split) | 06:25 | |
| *** ajfriesen8473 <ajfriesen8473!~ajfriesen@p5b27ab3c.dip0.t-ipconnect.de> has quit IRC (*.net *.split) | 06:25 | |
| *** wooosaiiii1 is now known as wooosaiiii | 06:25 | |
| *** ajfriesen84730 is now known as ajfriesen8473 | 06:25 | |
| *** Wouter0100670440 <Wouter0100670440!~Wouter010@entry.nbg.netvos.nl> has quit IRC (Quit: The Lounge - https://thelounge.chat) | 06:26 | |
| *** Wouter0100670440 <Wouter0100670440!~Wouter010@entry.nbg.netvos.nl> has joined #yocto | 06:27 | |
| *** Marmottus <Marmottus!~marmottus@2001:bc8:1820:2715::1> has joined #yocto | 06:30 | |
| *** rfuentess <rfuentess!~rfuentess@static-5-51-117-151.ftth.abo.bbox.fr> has joined #yocto | 06:33 | |
| *** Marmottus <Marmottus!~marmottus@2001:bc8:1820:2715::1> has quit IRC (Quit: The Lounge - https://thelounge.chat) | 06:37 | |
| *** Marmottus <Marmottus!~marmottus@2001:bc8:1820:2715::1> has joined #yocto | 06:38 | |
| *** Schlumpf <Schlumpf!~Schlumpf@62.157.232.203> has joined #yocto | 06:40 | |
| *** kayterina <kayterina!~kayterina@athedsl-115860.home.otenet.gr> has joined #yocto | 06:43 | |
| *** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has quit IRC (Ping timeout: 246 seconds) | 06:43 | |
| *** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has joined #yocto | 06:50 | |
| *** khem <khem!uid220931@id-220931.helmsley.irccloud.com> has joined #yocto | 06:51 | |
| *** ptsneves <ptsneves!~Thunderbi@031011128011.dynamic-3-poz-k-0-2-0.vectranet.pl> has joined #yocto | 06:53 | |
| *** mvlad <mvlad!~mvlad@2a02:2f08:4c00:5d00:7656:3cff:fe3f:7ce9> has joined #yocto | 06:53 | |
| *** varjag <varjag!~user@188.95.241.196> has joined #yocto | 07:00 | |
| *** olani_ <olani_!~olani@66.159.215.7> has quit IRC (Ping timeout: 258 seconds) | 07:04 | |
| *** olani <olani!~olani@66.159.215.7> has quit IRC (Ping timeout: 258 seconds) | 07:04 | |
| *** ptsneves1 <ptsneves1!~Thunderbi@031011128011.dynamic-3-poz-k-0-2-0.vectranet.pl> has joined #yocto | 07:16 | |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Quit: alessioigor) | 07:23 | |
| *** rusam <rusam!~rusam@94.204.221.73> has joined #yocto | 07:23 | |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto | 07:23 | |
| *** slimak <slimak!~slimak@eu242.internetdsl.tpnet.pl> has joined #yocto | 07:28 | |
| *** rfuentess_ <rfuentess_!~rfuentess@static-5-51-117-151.ftth.abo.bbox.fr> has joined #yocto | 07:36 | |
| *** dvergatal <dvergatal!~dvergatal@185.53.145.32> has quit IRC (Ping timeout: 255 seconds) | 07:37 | |
| *** dvergatal <dvergatal!~dvergatal@88-199-105-73.tktelekom.pl> has joined #yocto | 07:37 | |
| *** rfuentess <rfuentess!~rfuentess@static-5-51-117-151.ftth.abo.bbox.fr> has quit IRC (Ping timeout: 245 seconds) | 07:38 | |
| *** vladest <vladest!~Thunderbi@adsl-89-217-204-83.adslplus.ch> has quit IRC (Ping timeout: 248 seconds) | 07:47 | |
| *** rfuentess_ is now known as rfuentess | 07:49 | |
| *** vladest <vladest!~Thunderbi@adsl-89-217-204-83.adslplus.ch> has joined #yocto | 07:51 | |
| *** dvergatal <dvergatal!~dvergatal@88-199-105-73.tktelekom.pl> has quit IRC (Ping timeout: 255 seconds) | 07:58 | |
| *** Guest61 <Guest61!~Guest61@ip5f5bf4de.dynamic.kabel-deutschland.de> has joined #yocto | 08:00 | |
| *** dvergatal <dvergatal!~dvergatal@185.53.145.32> has joined #yocto | 08:00 | |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Quit: alessioigor) | 08:03 | |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto | 08:03 | |
| *** rob_w <rob_w!~rob@2001:a61:6079:5301:c5f9:27b8:af3f:bb1d> has joined #yocto | 08:04 | |
| *** florian <florian!~florian@port-217-146-132-69.static.as20676.net> has joined #yocto | 08:11 | |
| *** mbulut <mbulut!~mbulut@ip1f128f36.dynamic.kabel-deutschland.de> has joined #yocto | 08:12 | |
| *** gsalazar <gsalazar!~gsalazar@107.105.60.94.rev.vodafone.pt> has joined #yocto | 08:20 | |
| *** ptsneves <ptsneves!~Thunderbi@031011128011.dynamic-3-poz-k-0-2-0.vectranet.pl> has quit IRC (Read error: Connection reset by peer) | 08:35 | |
| *** ptsneves1 is now known as ptsneves | 08:35 | |
| *** ptsneves2 <ptsneves2!~Thunderbi@031011128011.dynamic-3-poz-k-0-2-0.vectranet.pl> has joined #yocto | 08:36 | |
| *** ptsneves2 is now known as ptsneves1 | 08:38 | |
| *** justache is now known as reddit-bot | 08:39 | |
| *** reddit-bot is now known as justache | 08:39 | |
| *** Guest61 <Guest61!~Guest61@ip5f5bf4de.dynamic.kabel-deutschland.de> has quit IRC (Quit: Client closed) | 09:01 | |
| *** wooosaiiii <wooosaiiii!~Thunderbi@89-212-21-243.static.t-2.net> has quit IRC (Ping timeout: 258 seconds) | 09:06 | |
| *** olani <olani!~olani@31-208-215-228.cust.bredband2.com> has joined #yocto | 09:14 | |
| *** olani_ <olani_!~olani@31-208-215-228.cust.bredband2.com> has joined #yocto | 09:14 | |
| *** Schlumpf <Schlumpf!~Schlumpf@62.157.232.203> has quit IRC (Quit: Client closed) | 09:18 | |
| *** goliath <goliath!~goliath@user/goliath> has joined #yocto | 09:33 | |
| *** linfax <linfax!~linfax@eumail.topcon.com> has joined #yocto | 10:01 | |
| *** dvergatal <dvergatal!~dvergatal@185.53.145.32> has quit IRC (Ping timeout: 246 seconds) | 10:06 | |
| *** dvergatal <dvergatal!~dvergatal@88-199-105-73.tktelekom.pl> has joined #yocto | 10:07 | |
| *** leon-anavi <leon-anavi!~Leon@46.55.231.62> has joined #yocto | 10:20 | |
| *** florian_kc <florian_kc!~florian@dynamic-093-133-189-142.93.133.pool.telefonica.de> has joined #yocto | 10:32 | |
| *** florian_kc <florian_kc!~florian@dynamic-093-133-189-142.93.133.pool.telefonica.de> has quit IRC (Ping timeout: 245 seconds) | 10:45 | |
| mcfrisk | could "calculating shlib requirements" be skipped for kernel modules? 10 minutes of that after every kernel compile seems excessive.. | 10:53 |
|---|---|---|
| *** florian_kc <florian_kc!~florian@port-217-146-132-69.static.as20676.net> has joined #yocto | 10:59 | |
| RP | mcfrisk: maybe, or maybe there is performance bug in there. What is it actually doing in that time? | 11:00 |
| RP | We did at least used to have special casing of kernel modules | 11:00 |
| *** Guest61 <Guest61!~Guest61@ip5f5bf4de.dynamic.kabel-deutschland.de> has joined #yocto | 11:02 | |
| RP | khem: FWIW it has come back suggesting https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=2fb12bbd092b0c10f1f2083216e723d2406e21c4 was the triggering change | 11:03 |
| RP | I noticed malloc fixes on the top of the stable branch and those may help, still trying to confirm | 11:03 |
| mcfrisk | RP: doing kernel debugging work by applying an efi debug patch and the kernel compile is really slow with do_package and do_package_qa both running for 10 minutes | 11:04 |
| mcfrisk | alse all actions with stripping, shlib analysys are in series, one file at a time. I feel like generating a Makefile for the task.. | 11:09 |
| *** rfuentess <rfuentess!~rfuentess@static-5-51-117-151.ftth.abo.bbox.fr> has quit IRC (Remote host closed the connection) | 11:12 | |
| RP | mcfrisk: there is supposed to be parallelism in at least some of the code | 11:14 |
| RP | mcfrisk: people don't often pay attention to performance and it has been a while since I last optimised that code | 11:15 |
| mcfrisk | RP: yea on normal builds this is hidden in noise, but I'm just changing a kernel patch and rebuilding, and end up waiting a bit too much. I'll try some fixes/workarounds.. | 11:17 |
| *** dvergatal <dvergatal!~dvergatal@88-199-105-73.tktelekom.pl> has quit IRC (Ping timeout: 246 seconds) | 11:17 | |
| *** dmoseley <dmoseley!~dmoseley@d4-50-9-187.evv.wideopenwest.com> has quit IRC (Ping timeout: 246 seconds) | 11:18 | |
| *** dvergatal <dvergatal!~dvergatal@185.53.145.32> has joined #yocto | 11:19 | |
| RP | mcfrisk: I'd be interested in knowing more about where the time is spent. bitbake -P can help with that btw | 11:31 |
| RP | the task should have a profile log generated with that | 11:31 |
| *** tgamblin <tgamblin!~tgamblin@2001:1970:5b1f:ab00:d875:6297:4e81:e577> has joined #yocto | 11:35 | |
| mcfrisk | RP: bitbake -P :( https://pastebin.com/raw/AtrwVURL | 11:41 |
| RP | mcfrisk: strange. We should work out what is wrong and fix that, the profile data is useful | 11:46 |
| *** amitk_ <amitk_!~amit@58.84.61.208> has joined #yocto | 11:50 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #yocto | 11:54 | |
| *** dmoseley <dmoseley!~dmoseley@d4-50-9-187.evv.wideopenwest.com> has joined #yocto | 11:55 | |
| *** slimak <slimak!~slimak@eu242.internetdsl.tpnet.pl> has quit IRC (Ping timeout: 250 seconds) | 12:09 | |
| *** camus <camus!~Instantbi@58.246.136.203> has quit IRC (Ping timeout: 248 seconds) | 12:32 | |
| *** Xagen <Xagen!~Xagen@99-135-179-142.lightspeed.austtx.sbcglobal.net> has joined #yocto | 12:36 | |
| *** GillesM <GillesM!~gilles@116.79.123.78.rev.sfr.net> has quit IRC (Ping timeout: 250 seconds) | 12:37 | |
| *** amitk_ <amitk_!~amit@58.84.61.208> has quit IRC (Quit: Lost terminal) | 12:38 | |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Quit: alessioigor) | 12:38 | |
| *** GillesM <GillesM!~gilles@116.79.123.78.rev.sfr.net> has joined #yocto | 12:38 | |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto | 12:38 | |
| *** GillesMM <GillesMM!~gilles@116.79.123.78.rev.sfr.net> has joined #yocto | 12:39 | |
| *** GillesM <GillesM!~gilles@116.79.123.78.rev.sfr.net> has quit IRC (Client Quit) | 12:39 | |
| *** GillesMM <GillesMM!~gilles@116.79.123.78.rev.sfr.net> has quit IRC (Remote host closed the connection) | 12:39 | |
| *** GillesM <GillesM!~gilles@116.79.123.78.rev.sfr.net> has joined #yocto | 12:39 | |
| *** rob_w <rob_w!~rob@2001:a61:6079:5301:c5f9:27b8:af3f:bb1d> has quit IRC (Read error: Connection reset by peer) | 12:46 | |
| *** rusam <rusam!~rusam@94.204.221.73> has quit IRC (Quit: Leaving...) | 13:07 | |
| *** yannd <yannd!~yann@88.120.44.86> has quit IRC (Remote host closed the connection) | 13:14 | |
| *** Guest61 <Guest61!~Guest61@ip5f5bf4de.dynamic.kabel-deutschland.de> has quit IRC (Quit: Client closed) | 13:29 | |
| *** slimak <slimak!~slimak@eu242.internetdsl.tpnet.pl> has joined #yocto | 13:29 | |
| *** prabhakar <prabhakar!~prabhakar@pc.renesas.eu> has joined #yocto | 13:30 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed) | 13:30 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #yocto | 13:31 | |
| *** prabhakar <prabhakar!~prabhakar@pc.renesas.eu> has quit IRC (Client Quit) | 13:31 | |
| *** prabhakar <prabhakar!~prabhakar@149.11.182.26> has joined #yocto | 13:31 | |
| *** Wouter0100670440 <Wouter0100670440!~Wouter010@entry.nbg.netvos.nl> has quit IRC (Quit: The Lounge - https://thelounge.chat) | 13:31 | |
| *** Wouter0100670440 <Wouter0100670440!~Wouter010@entry.nbg.netvos.nl> has joined #yocto | 13:32 | |
| *** lexano <lexano!~lexano@174.119.69.134> has joined #yocto | 13:35 | |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Quit: alessioigor) | 13:54 | |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto | 13:54 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed) | 14:06 | |
| *** prabhakar <prabhakar!~prabhakar@149.11.182.26> has quit IRC (Quit: Connection closed) | 14:06 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #yocto | 14:12 | |
| *** prabhakar <prabhakar!~prabhakar@pc.renesas.eu> has joined #yocto | 14:12 | |
| *** xmn_ <xmn_!~xmn@2600:4040:9390:8c00:96c:839a:49cb:654a> has quit IRC (Quit: xmn_) | 14:18 | |
| *** zelgomer <zelgomer!~jake@gateway/tor-sasl/zelgomer> has quit IRC (Ping timeout: 246 seconds) | 14:23 | |
| *** xmn <xmn!~xmn@2600:4040:9390:8c00:95aa:e2e5:6d90:9e68> has joined #yocto | 14:23 | |
| *** zelgomer <zelgomer!~jake@gateway/tor-sasl/zelgomer> has joined #yocto | 14:25 | |
| *** linfax <linfax!~linfax@eumail.topcon.com> has quit IRC (Ping timeout: 246 seconds) | 14:41 | |
| *** kayterina <kayterina!~kayterina@athedsl-115860.home.otenet.gr> has quit IRC (Quit: Client closed) | 14:55 | |
| *** florian_kc <florian_kc!~florian@port-217-146-132-69.static.as20676.net> has quit IRC (Ping timeout: 246 seconds) | 15:12 | |
| *** dvergatal <dvergatal!~dvergatal@185.53.145.32> has quit IRC (Quit: Lost terminal) | 15:12 | |
| *** florian <florian!~florian@port-217-146-132-69.static.as20676.net> has quit IRC (Quit: Ex-Chat) | 15:15 | |
| *** varjag <varjag!~user@188.95.241.196> has quit IRC (Quit: ERC (IRC client for Emacs 27.1)) | 15:19 | |
| RP | rburton: any luck with the mmu tweaks? | 15:32 |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Quit: alessioigor) | 15:34 | |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto | 15:34 | |
| *** mbulut <mbulut!~mbulut@ip1f128f36.dynamic.kabel-deutschland.de> has quit IRC (Ping timeout: 244 seconds) | 15:52 | |
| *** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV) | 15:54 | |
| khem | RP: that change was in 2.37 too isnt it | 15:58 |
| RP | khem: it is :/ | 15:59 |
| RP | khem: although only fairly recently | 15:59 |
| RP | khem: I'm going to suggest we pull in the latest glibc fixes on stable, rebuild uninative and see if that works | 16:00 |
| khem | sure is there anything interesting in the 2.38 delta so far | 16:12 |
| *** Vonter_ <Vonter_!~Vonter@user/vonter> has quit IRC (Read error: Connection reset by peer) | 16:14 | |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Quit: alessioigor) | 16:17 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed) | 16:20 | |
| *** Vonter <Vonter!~Vonter@user/vonter> has joined #yocto | 16:20 | |
| *** wmills <wmills!~wmills@pool-108-31-156-225.washdc.fios.verizon.net> has joined #yocto | 16:26 | |
| wmills | Anyone around that understands the testresults git repo structure and procedures? | 16:29 |
| RP | wmills: I'm tempted to hide ;-) | 16:30 |
| wmills | I am trying to understand why some builds have just one result set ( /0 ) but most of 2 to 3 and finally a few per year have 10 result sets ( /0 to /9 ) | 16:31 |
| khem | RP: Seeing your glibc version bump patch the memalign patches look interestign | 16:31 |
| wmills | I do realize it is Friday night | 16:31 |
| RP | wmills: it depends how many times the autobuilder runs against that revision | 16:31 |
| RP | wmills: if there are no pushes over a weekend you may see 2 to 3 | 16:32 |
| wmills | It is not different people running different tests? | 16:32 |
| RP | khem: that was my thought | 16:32 |
| RP | wmills: in theory it could be, in practise I think it is when we don't push and the nightly autobuilder jobs rerun | 16:33 |
| wmills | OK that helps. For build master/70850-gd221e59a5067266c3f620259a1e56a56823df1fb I see 10 result sets. Most have 222 testresults.json files but /1 and /8 have 61 more testresults.json files. Any idea what is going on there? | 16:35 |
| RP | wmills: a-full vs a-quick builds? | 16:35 |
| wmills | That makes sense. (222 does not seem quick). The extra tests are 2 more images in poky-altcfg for qemumips qemuppc and 26 new ptests for qemux86-64 and qemuarm64. Additional ptests include openssh parted etc | 16:39 |
| RP | wmills: that sounds very like the differences between a-full and a-quick | 16:40 |
| *** leon-anavi <leon-anavi!~Leon@46.55.231.62> has quit IRC (Read error: Connection reset by peer) | 16:41 | |
| *** leon-anavi <leon-anavi!~Leon@46.55.231.62> has joined #yocto | 16:41 | |
| RP | wmills: https://git.yoctoproject.org/yocto-autobuilder2/tree/config.py#n92 | 16:42 |
| wmills | OK I'll look at autobuild config next. | 16:42 |
| wmills | Great! | 16:42 |
| RP | wmills: see trigger_builders_wait_full vs trigger_builders_wait_full | 16:42 |
| RP | er, wait_full vs wait_quick | 16:42 |
| wmills | So I am trying to figure out how Linaro can record its test's results from genericarm64. First I wanted to understand the scope of what was tested first. But I was looking for examples of HW tests being checked in independently | 16:45 |
| *** ptsneves <ptsneves!~Thunderbi@031011128011.dynamic-3-poz-k-0-2-0.vectranet.pl> has quit IRC (Quit: ptsneves) | 16:45 | |
| *** ptsneves1 is now known as ptsneves | 16:45 | |
| wmills | I think I saw examples in the stable branches | 16:45 |
| *** ptsneves1 <ptsneves1!~Thunderbi@031011128011.dynamic-3-poz-k-0-2-0.vectranet.pl> has joined #yocto | 16:45 | |
| RP | wmills: each release should have manual entries from QA's runs | 16:45 |
| RP | wmills: taking http://downloads.yoctoproject.org/releases/yocto/yocto-4.2/ you'll see testresults and testresults-intel, the latter are the manual QA additions from intel+wr | 16:47 |
| wmills | each release but not each master build, correct? I think I should switch back to looking at the stable branches as the release builds will be easier to find | 16:47 |
| RP | the top level report is re-generated to include them all | 16:47 |
| RP | wmills: correct | 16:47 |
| Saur | RP: Sorry for the wall of text to the openembedded-core list. | 16:48 |
| wmills | How do the intel & wr test results get checking in to the git repo? Do they are push rights? A maintainer does it? or a server process? | 16:50 |
| RP | wmills: Intel does the release engineering, they collect up the results and push them in. They have access as release engineering | 16:50 |
| *** amitk_ <amitk_!~amit@58.84.61.208> has joined #yocto | 16:50 | |
| RP | Saur: what happens before the SRCPV changes if you try and build one of those recipes with invalid srcrevs? | 16:52 |
| wmills | RP: OK let me keep looking at this. Thanks. Have a good weekend | 16:52 |
| RP | wmills: From memory I think there is a collaboration staging git repo and Intel collects the results from there | 16:53 |
| Saur | RP: In Mickledore I get no errors during parsing, and the same errors that I now get with my suggested change applied to Nanbield. I.e., with my suggested change applied the behavior in Mickledore and Nanbield is identical. | 16:54 |
| RP | Saur: your change feels like we're just papering over problems :( | 16:56 |
| *** florian_kc <florian_kc!~florian@dynamic-093-133-189-142.93.133.pool.telefonica.de> has joined #yocto | 16:58 | |
| Saur | RP: Well, this maintains status quo when tags are used in SRCREV (for good or bad). | 16:59 |
| RP | Saur: so to be clear, you don't get a parsing error when you try and execute the recipe, it fails at runtime in do_fetch | 16:59 |
| Saur | RP: Yes, exactly as it used to be. | 17:00 |
| RP | whilst it may have done that, I think it is bad | 17:00 |
| RP | Saur: what happens if you make the fetcher raise SkipRecipe() ? | 17:01 |
| Saur | You mean as I did in my original patch? | 17:01 |
| *** leon-anavi <leon-anavi!~Leon@46.55.231.62> has quit IRC (Quit: Leaving) | 17:03 | |
| Saur | Then the error message changes for the case where you set SRCREV to a tag to the one I included in the commit message. | 17:03 |
| RP | Saur: I guess I'm thinking of the fetcher function itself doing it but it would be equivalence | 17:04 |
| RP | I guess I still think that these recipes should be fixed to raise SkipRecipe themselves if they set broken configurations | 17:04 |
| Saur | The problem (for me) is that the brokenness depends on external factors, i.e., whether the user building happens to have access to a specific Git repository or not. A repository for a recipe he probably isn't interested in anyway (since he does not have access to it). | 17:07 |
| RP | Saur: there is another side to this - a user does generally prefer to know about breakage earlier than later. This is just going to hide breakage from a user until part way through a build | 17:08 |
| Saur | True, but at the same time, errors during parsing are horrible as they, e.g., prevent `bitbake -e` from being used. | 17:10 |
| Saur | And the fetch tasks are typically run early in the build process anyway. | 17:10 |
| RP | Saur: I'll think about it. I'm more of the view that in general people do want to know about broken configuration sooner than later though | 17:11 |
| Saur | RP: My problem with that is that the current early error is just a side effect of using tags in SRCREV. E.g., if you set an incorrect SHA-1 in the SRCREV you will not get the error until the fetch fails, i.e., the same behavior that I have for tags in SRCREV with my patch applied. | 17:15 |
| RP | Saur: we have to resolve tags and we can detect that early. It is assumed that revisions are correct but we would detect e.g. typos in the revision that made then invalid | 17:17 |
| Saur | RP: Well, true. But as I see it, having a reference in the SRCREV that all may not be able to access, is no different from having a PACKAGECONFIG that adds a dependency on a recipe that you do not have. It only becomes an error if you actually try to enable that PACKAGECONFIG, much like the SRCREV only becomes an error if you try to build the recipe without the proper access rights. | 17:22 |
| RP | Saur: I disagree and I you're rapidly pushing me to the view this really should be an error | 17:24 |
| RP | I appreciate it is tricky for your situation | 17:24 |
| Saur | RP: Well, (I think) I can handle the situation for us, by using an anonymous Python function in each recipe that is affected and letting it raise SkipRecipe. But I would of course very much prefer a generic solutions that maintains the behavior from previous releases. | 17:31 |
| Saur | RP: Related to this: while we currently rely on being able to set SRCREV to a tag, have you considered removing this support and only allow SHA-1s in SRCREV? | 17:31 |
| * RP thinks the previous behaviour is broken | 17:32 | |
| RP | Saur: I wondered about it but I suspect people would be out with pitchforks if I did that :/ | 17:32 |
| *** goliath <goliath!~goliath@user/goliath> has joined #yocto | 17:34 | |
| Saur | RP: Well, you don't know until you try. I know it would definitely make us reprioritise some of our development work. ;) | 17:36 |
| *** slimak <slimak!~slimak@eu242.internetdsl.tpnet.pl> has quit IRC (Ping timeout: 246 seconds) | 17:38 | |
| *** gsalazar <gsalazar!~gsalazar@107.105.60.94.rev.vodafone.pt> has quit IRC (Ping timeout: 260 seconds) | 17:54 | |
| *** florian_kc <florian_kc!~florian@dynamic-093-133-189-142.93.133.pool.telefonica.de> has quit IRC (Ping timeout: 255 seconds) | 18:16 | |
| *** flom84 <flom84!~flom84@user/flom84> has joined #yocto | 18:21 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #yocto | 18:31 | |
| *** flom84 <flom84!~flom84@user/flom84> has quit IRC (Ping timeout: 246 seconds) | 18:55 | |
| *** flom84 <flom84!~flom84@user/flom84> has joined #yocto | 18:56 | |
| *** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Ping timeout: 248 seconds) | 18:57 | |
| *** flom84 <flom84!~flom84@user/flom84> has quit IRC (Remote host closed the connection) | 18:58 | |
| *** Vonter <Vonter!~Vonter@user/vonter> has joined #yocto | 18:59 | |
| *** olani <olani!~olani@31-208-215-228.cust.bredband2.com> has quit IRC (Ping timeout: 246 seconds) | 19:00 | |
| *** olani <olani!~olani@66.159.215.7> has joined #yocto | 19:00 | |
| *** olani_ <olani_!~olani@31-208-215-228.cust.bredband2.com> has quit IRC (Ping timeout: 246 seconds) | 19:00 | |
| *** olani_ <olani_!~olani@66.159.215.7> has joined #yocto | 19:01 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed) | 19:02 | |
| *** florian_kc <florian_kc!~florian@dynamic-093-133-189-142.93.133.pool.telefonica.de> has joined #yocto | 19:09 | |
| *** l3s8g <l3s8g!~l3s8g@p200300de1735060000000000000005e9.dip0.t-ipconnect.de> has joined #yocto | 19:11 | |
| *** dvergatal <dvergatal!~dvergatal@185.53.145.32> has joined #yocto | 19:13 | |
| *** amitk_ <amitk_!~amit@58.84.61.208> has quit IRC (Ping timeout: 260 seconds) | 19:16 | |
| *** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV) | 19:19 | |
| khem | RP: did the new glibc update help ? | 19:29 |
| *** Kubu_work <Kubu_work!~kubu@2a01cb05945b7e009bdc688723a24f31.ipv6.abo.wanadoo.fr> has quit IRC (Quit: Leaving.) | 19:35 | |
| *** Wouter0100670440 <Wouter0100670440!~Wouter010@entry.nbg.netvos.nl> has quit IRC (Quit: The Lounge - https://thelounge.chat) | 19:36 | |
| *** Wouter0100670440 <Wouter0100670440!~Wouter010@entry.nbg.netvos.nl> has joined #yocto | 19:37 | |
| *** reatmon <reatmon!sid538117@id-538117.helmsley.irccloud.com> has quit IRC (Server closed connection) | 19:42 | |
| *** reatmon <reatmon!sid538117@id-538117.helmsley.irccloud.com> has joined #yocto | 19:42 | |
| *** amitk <amitk!~amit@58.84.61.208> has quit IRC (Ping timeout: 255 seconds) | 19:46 | |
| RP | khem: I think so. We'll need more testing to know for sure | 19:56 |
| *** mvlad <mvlad!~mvlad@2a02:2f08:4c00:5d00:7656:3cff:fe3f:7ce9> has quit IRC (Remote host closed the connection) | 20:09 | |
| *** mdp <mdp!sid49840@id-49840.ilkley.irccloud.com> has quit IRC (Server closed connection) | 20:13 | |
| *** mdp <mdp!sid49840@id-49840.ilkley.irccloud.com> has joined #yocto | 20:13 | |
| *** goliath <goliath!~goliath@user/goliath> has joined #yocto | 20:16 | |
| *** ptsneves1 <ptsneves1!~Thunderbi@031011128011.dynamic-3-poz-k-0-2-0.vectranet.pl> has quit IRC (Ping timeout: 248 seconds) | 20:17 | |
| *** NishanthMenon <NishanthMenon!sid138049@id-138049.uxbridge.irccloud.com> has quit IRC (Server closed connection) | 20:23 | |
| *** NishanthMenon <NishanthMenon!sid138049@id-138049.uxbridge.irccloud.com> has joined #yocto | 20:23 | |
| adrianf | Saur,RP: just a third opinion. If we think about OSS repositories only, a parsing error is fine. However, for example we have a GitLab infrastructure with 10 thousands of users. Only users who really need access to a git repo get access to it. If parsing a layer requires access to all the repos referred by a recipe in the layer, tags are no longer | 20:25 |
| adrianf | usable. I changed all our recipes from tags to hashes after updating to Kirkstone. If I remember correctly, Kirkstone started throwing warnings. I hope this comment makes sense, but I'm not sure that I got the begin of the discussion. | 20:25 |
| adrianf | It's maybe also important to know that GitLab runs bitbake with the previledges of the user who pushed the build pipeline. In such an environment a fetch error is much better than a parse error. | 20:29 |
| *** pabigot <pabigot!~pab@250.sub-75-236-9.myvzw.com> has quit IRC (Ping timeout: 255 seconds) | 20:32 | |
| *** xmn <xmn!~xmn@2600:4040:9390:8c00:95aa:e2e5:6d90:9e68> has quit IRC (Ping timeout: 246 seconds) | 20:37 | |
| RP | adrianf: the point is that recipes should either parse and work or they should be skipped and effectively not be present. The state of parsing then failing part way through a build is not a good user experience | 20:39 |
| *** xmn <xmn!~xmn@2600:4040:9390:8c00:95aa:e2e5:6d90:9e68> has joined #yocto | 20:41 | |
| adrianf | For us tags are useless now. It's not a big issue. We can go with recipes with hashes only. But it means manually maintaining the hash and the pv=tag per recipe. Users are asking why this is required. | 20:46 |
| *** l3s8g <l3s8g!~l3s8g@p200300de1735060000000000000005e9.dip0.t-ipconnect.de> has quit IRC (Ping timeout: 246 seconds) | 20:46 | |
| *** pabigot <pabigot!~pab@250.sub-75-236-9.myvzw.com> has joined #yocto | 20:48 | |
| *** rsalveti <rsalveti!uid117878@id-117878.uxbridge.irccloud.com> has quit IRC (Quit: Connection closed for inactivity) | 20:48 | |
| adrianf | Resolving at parse time also makes parsing slower. This makes sense for e.g. bitbake world. But it is a disadvantage if rebuilding one recipe with the esdk is the use case. Especially if you are offline. | 20:51 |
| JaMa | adrianf: bitbake was always resolving tags into shas while parsing, that's why we switched from tags to hashes about 10 years ago, because it was hammering our gerrit servers too much while parsing the recipes | 20:51 |
| JaMa | adrianf: we have a bbclass which checks that has matches with a tag name and PV, so it doesn't have to be done manually | 20:52 |
| Saur | JaMa: Do you have a URL for that class? | 20:52 |
| adrianf | Yes, the DoS attacks are also why we changed all recipes. | 20:53 |
| JaMa | adrianf: Saur: https://github.com/openwebos/meta-webos/commit/5796817464f3a692af91526bdf1b33955da123b0 | 20:53 |
| JaMa | currently used version is now in meta-webosose: https://github.com/webosose/meta-webosose/blob/master/meta-webos/classes/webos_enhanced_submissions.bbclass | 20:54 |
| JaMa | but there weren't so many changes since introduction | 20:54 |
| adrianf | But my understanding of the question was: If resolving at parse time is better than resolving at fetch time. I just wanted to say: It really depends. | 20:55 |
| JaMa | but you also said it changed in kirkstone which I don't think is true, it was always like that | 20:56 |
| *** l3s8g <l3s8g!~l3s8g@p200300de1735060000000000000005e9.dip0.t-ipconnect.de> has joined #yocto | 20:56 | |
| JaMa | or maybe you just meant that kirkstone started throwing warnings | 20:57 |
| Saur | JaMa: I think the change adrianf is thinking of is the requirement to use ${SRCPV} when using anything but SHA-1 or you get an error. | 20:57 |
| JaMa | IC | 20:57 |
| Saur | I guess that requirement has solved itself now though since ${SRCPV} is no more... | 20:59 |
| RP | aaround kirkstone time there was a realisation that there were big problems if you didn't use SRCPV when bitbake was expecting it. That was why the warnings were added, I spent days working out why some odd behaviour happened :/ | 21:01 |
| RP | now, we get to try and clean things up a bit and if we can, simplify... | 21:01 |
| RP | adrianf: tags had to be resolved to hashes for a while after it was found people do move tags :( | 21:02 |
| *** brrm <brrm!~brrm@ip-078-043-203-234.um18.pools.vodafone-ip.de> has quit IRC (Ping timeout: 245 seconds) | 21:09 | |
| *** brrm <brrm!~brrm@ip-078-043-203-234.um18.pools.vodafone-ip.de> has joined #yocto | 21:10 | |
| JaMa | for that we enforce using annotated tags as well with their hash ending in SRCREV, so if someone recreates tag with the same name it's detected as well | 21:21 |
| adrianf | RP, Saur,JaMa: With Kirkstone my conclusion was that tags have several negative side effects and I finally removed them. This discussion pointed out some more disadvantages. I agree, that resolving while fetching would lead to even worse corner cases than failing fast at parse time. But from a user's perspective it's not too obvious why tags should | 21:24 |
| adrianf | not be used. | 21:24 |
| RP | adrianf: we probably should at least document this somewhere... | 21:24 |
| *** pabigot <pabigot!~pab@250.sub-75-236-9.myvzw.com> has quit IRC (Ping timeout: 248 seconds) | 21:25 | |
| *** warthog9 <warthog9!warthog9@proxy.monkeyblade.net> has quit IRC (Ping timeout: 246 seconds) | 21:25 | |
| JaMa | RP: I don't want to jinx it, but the ping timeout fix from you seems to work on my 90K task jobs, only timeouts I got today were from j | 21:28 |
| JaMa | java.io.EOFException | 21:28 |
| adrianf | RP: I would probably search for that in the bitbake manual git fetcher section. | 21:32 |
| *** pabigot <pabigot!~pab@250.sub-75-236-9.myvzw.com> has joined #yocto | 21:41 | |
| *** warthog9 <warthog9!warthog9@proxy.monkeyblade.net> has joined #yocto | 21:50 | |
| *** ptsneves <ptsneves!~Thunderbi@031011128011.dynamic-3-poz-k-0-2-0.vectranet.pl> has quit IRC (Quit: ptsneves) | 22:03 | |
| *** l3s8g <l3s8g!~l3s8g@p200300de1735060000000000000005e9.dip0.t-ipconnect.de> has quit IRC (Ping timeout: 246 seconds) | 22:23 | |
| *** florian_kc <florian_kc!~florian@dynamic-093-133-189-142.93.133.pool.telefonica.de> has quit IRC (Ping timeout: 250 seconds) | 22:46 | |
| *** Marian66 <Marian66!~Marian@c-73-219-138-101.hsd1.nh.comcast.net> has joined #yocto | 22:55 | |
| Marian66 | Hi, | 22:57 |
| Marian66 | I have a recipe that on do_compile is creating build/x86_64/ and build/arm64. | 22:57 |
| Marian66 | On do_install I'm trying ot install them based on the TARGET_ARCH: | 22:57 |
| Marian66 | if ["${TARGET_ARCH}" == "aarch64"]; then | 22:57 |
| Marian66 | target="arm64" | 22:57 |
| Marian66 | elif ["${TARGET_ARCH}" == "x86_64"]; then | 22:57 |
| Marian66 | target="amd64" | 22:57 |
| Marian66 | fi | 22:57 |
| Marian66 | When I compile I get the following: | 22:57 |
| Marian66 | 177: [x86_64: not found | 22:57 |
| Marian66 | 179: [x86_64: not found | 22:57 |
| Marian66 | Can you please help? | 22:57 |
| *** ldts <ldts!sid269548@2a03:5180:f:4::4:1cec> has quit IRC (Server closed connection) | 22:58 | |
| *** ldts <ldts!sid269548@id-269548.hampstead.irccloud.com> has joined #yocto | 22:58 | |
| *** florian_kc <florian_kc!~florian@dynamic-093-133-189-142.93.133.pool.telefonica.de> has joined #yocto | 23:07 | |
| Saur | Marian66: You are lacking spaces after [ and before ] | 23:13 |
| Saur | Marian66: You should also use = instead of == as the latter is a bashism. | 23:14 |
| *** florian_kc <florian_kc!~florian@dynamic-093-133-189-142.93.133.pool.telefonica.de> has quit IRC (Ping timeout: 250 seconds) | 23:18 | |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!