All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2015-03-18
Date: Thu, 19 Mar 2015 12:51:26 +0100	[thread overview]
Message-ID: <550AB83E.5050400@imgtec.com> (raw)
In-Reply-To: <20150319103012.GC2415@tarshish>

Hi Baruch,

On 19/03/15 11:30, Baruch Siach wrote:
> Hi Vicente,
> 
> On Thu, Mar 19, 2015 at 11:17:57AM +0100, Vicente Olivert Riera wrote:
>> On 19/03/15 08:30, Thomas Petazzoni wrote:
>>> Build statistics for 2015-03-18
>>> ===============================
>>>       mipsel |          lua-periphery-1.0.4-1 | NOK | http://autobuild.buildroot.net/results/901c2d922ea4d126bf6cb1f4e36324601e3a4664/
>>>     mips64el |          lua-periphery-1.0.4-1 | NOK | http://autobuild.buildroot.net/results/4d795b723facfde23792e5e2a0c170902d89c621/
>>>     mips64el |          lua-periphery-1.0.4-1 | NOK | http://autobuild.buildroot.net/results/a97d1bda93b5fa9ce975145b82a752c957c24cab/
>>>       mipsel |          lua-periphery-1.0.4-1 | NOK | http://autobuild.buildroot.net/results/f01e4aa07856db6b7bb63ca07eac1ed0987f3e7f/
>>
>> The failure is actually in c-periphery. I have fixed it upstream...
>>
>> https://github.com/vsergeev/c-periphery/commit/0fdfac3264f1dce32991f4ec30d084e34b35181d
>>
>> ...and since c-periphery is "git-cloned" into lua-periphery...
>>
>> $ grep clone output/build/lua-periphery-1.0.4-1/lua-periphery/Makefile
>> 	git clone git://github.com/vsergeev/c-periphery --depth 1 --branch v1.0.1
>>
>> ...then this problem is automatically fixed in Buildroot! :-)
> 
> That is nice for this bug fix, but IMO it is bad for reproducibility. That is, 
> lua-periphery build different source code every time this external repo 
> updates.

Yes, I agree with that. Perhaps you could ask lua-periphery upstream and
tell them to not do that :P

Regards,
--
Vincent

> baruch
> 

  reply	other threads:[~2015-03-19 11:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-19  7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2015-03-18 Thomas Petazzoni
2015-03-19 10:17 ` Vicente Olivert Riera
2015-03-19 10:30   ` Baruch Siach
2015-03-19 11:51     ` Vicente Olivert Riera [this message]
2015-03-19 12:23       ` Thomas Petazzoni
2015-03-19 20:30         ` François Perrad

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=550AB83E.5050400@imgtec.com \
    --to=vincent.riera@imgtec.com \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.