On 2/5/16 10:33 AM, Ian Campbell wrote:
> On Fri, 2016-02-05 at 08:48 -0600, Doug Goldstein wrote:
>>
>> The goal here is not to replace osstest by any means but to augment it by
>> providing some easy to do build tests on every revision and reporting back.
>> It
>> should be possible in the futur
On Fri, 2016-02-05 at 08:48 -0600, Doug Goldstein wrote:
>
> The goal here is not to replace osstest by any means but to augment it by
> providing some easy to do build tests on every revision and reporting back. It
> should be possible in the future to potentially tie this into osstest to
> allow
On Fri, Feb 05, 2016 at 09:19:30AM -0600, Doug Goldstein wrote:
> On 2/5/16 9:09 AM, Wei Liu wrote:
> > On Fri, Feb 05, 2016 at 08:48:49AM -0600, Doug Goldstein wrote:
> >> This is just suppose to do a simple compile test on Travis CI. Currently
> >> due to linux86 (bcc/bin86/dev86) not being white
On 2/5/16 9:09 AM, Wei Liu wrote:
> On Fri, Feb 05, 2016 at 08:48:49AM -0600, Doug Goldstein wrote:
>> This is just suppose to do a simple compile test on Travis CI. Currently
>> due to linux86 (bcc/bin86/dev86) not being whitelisted the tools cannot
>> be built.
>>
>> Signed-off-by: Doug Goldstein
On Fri, Feb 05, 2016 at 08:48:49AM -0600, Doug Goldstein wrote:
> This is just suppose to do a simple compile test on Travis CI. Currently
> due to linux86 (bcc/bin86/dev86) not being whitelisted the tools cannot
> be built.
>
> Signed-off-by: Doug Goldstein
> ---
>
> So this will work great if
This is just suppose to do a simple compile test on Travis CI. Currently
due to linux86 (bcc/bin86/dev86) not being whitelisted the tools cannot
be built.
Signed-off-by: Doug Goldstein
---
So this will work great if we get a regular cronjob or a post-receive hook
to push to GitHub (https://githu
