* [Buildroot] [autobuild.buildroot.net] Your build results for 2019-04-14 [not found] <701271v3F60UVCn.RZmta@smtpin.rzone.de> @ 2019-04-19 17:41 ` André Hentschel 2019-04-21 13:22 ` Thomas Petazzoni 0 siblings, 1 reply; 3+ messages in thread From: André Hentschel @ 2019-04-19 17:41 UTC (permalink / raw) To: buildroot Am 15.04.19 um 08:00 schrieb Thomas Petazzoni: > Hello, > > This is the list of Buildroot build failures that occured on > 2019-04-14, and for which you are a registered architecture developer > or package developer. Please help us improving the quality of > Buildroot by investigating those build failures and sending patches to > fix them. Thanks! > > Results for the 'master' branch > =============================== > > Build failures related to your packages: > > arm | libkrb5-1.16.2 | http://autobuild.buildroot.net/results/41150b7a70ceab08474fa8f1a99486c343f58e21 > arc | libkrb5-1.16.2 | http://autobuild.buildroot.net/results/a12a53b81d5db4d53fb858a2ad2dd79718cf082e > Hi, I can't reproduce those and the others here. Guess they are fixed by cb3a0177ef8ac64699d753b11daa0c37b3cf7b88 ? What a waste of time then... ^ permalink raw reply [flat|nested] 3+ messages in thread
* [Buildroot] [autobuild.buildroot.net] Your build results for 2019-04-14 2019-04-19 17:41 ` [Buildroot] [autobuild.buildroot.net] Your build results for 2019-04-14 André Hentschel @ 2019-04-21 13:22 ` Thomas Petazzoni 2019-04-22 18:29 ` André Hentschel 0 siblings, 1 reply; 3+ messages in thread From: Thomas Petazzoni @ 2019-04-21 13:22 UTC (permalink / raw) To: buildroot Hello, On Fri, 19 Apr 2019 19:41:57 +0200 Andr? Hentschel <nerv@dawncrow.de> wrote: > > Results for the 'master' branch > > =============================== > > > > Build failures related to your packages: > > > > arm | libkrb5-1.16.2 | http://autobuild.buildroot.net/results/41150b7a70ceab08474fa8f1a99486c343f58e21 > > arc | libkrb5-1.16.2 | http://autobuild.buildroot.net/results/a12a53b81d5db4d53fb858a2ad2dd79718cf082e > > > > Hi, > > I can't reproduce those and the others here. Guess they are fixed by cb3a0177ef8ac64699d753b11daa0c37b3cf7b88 ? No, these are fixed by 491b13def5a4dfce21e98becda1f2c6ea99e9fa0, which I applied just a few hours ago. > What a waste of time then... I'm not sure which waste of time you're talking about. All build failures have a "gitid" file that says with which commit the build was done, precisely to be able to check if a fix was already done. The patchwork list of pending patches is also publicly available to check if someone else has already sent a patch for it. I'm not sure how we could do better than this. Best regards, Thomas -- Thomas Petazzoni, CTO, Bootlin Embedded Linux and Kernel engineering https://bootlin.com ^ permalink raw reply [flat|nested] 3+ messages in thread
* [Buildroot] [autobuild.buildroot.net] Your build results for 2019-04-14 2019-04-21 13:22 ` Thomas Petazzoni @ 2019-04-22 18:29 ` André Hentschel 0 siblings, 0 replies; 3+ messages in thread From: André Hentschel @ 2019-04-22 18:29 UTC (permalink / raw) To: buildroot Am 21.04.19 um 15:22 schrieb Thomas Petazzoni: > Hello, > > On Fri, 19 Apr 2019 19:41:57 +0200 > Andr? Hentschel <nerv@dawncrow.de> wrote: > >>> Results for the 'master' branch >>> =============================== >>> >>> Build failures related to your packages: >>> >>> arm | libkrb5-1.16.2 | http://autobuild.buildroot.net/results/41150b7a70ceab08474fa8f1a99486c343f58e21 >>> arc | libkrb5-1.16.2 | http://autobuild.buildroot.net/results/a12a53b81d5db4d53fb858a2ad2dd79718cf082e >>> >> >> Hi, >> >> I can't reproduce those and the others here. Guess they are fixed by cb3a0177ef8ac64699d753b11daa0c37b3cf7b88 ? > > No, these are fixed by 491b13def5a4dfce21e98becda1f2c6ea99e9fa0, which > I applied just a few hours ago. Thank you >> What a waste of time then... > > I'm not sure which waste of time you're talking about. All build > failures have a "gitid" file that says with which commit the build was > done, precisely to be able to check if a fix was already done. The > patchwork list of pending patches is also publicly available to check > if someone else has already sent a patch for it. > > I'm not sure how we could do better than this. Sorry, didn't intend to offend. Should rather have put in more effort. I guess my local host headers were picked up. And I know of gitid, but it didn't helped me with that. ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2019-04-22 18:29 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <701271v3F60UVCn.RZmta@smtpin.rzone.de>
2019-04-19 17:41 ` [Buildroot] [autobuild.buildroot.net] Your build results for 2019-04-14 André Hentschel
2019-04-21 13:22 ` Thomas Petazzoni
2019-04-22 18:29 ` André Hentschel
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox