Re: [Crowbar] how to debug Travis failures

2013-03-13 Thread James Tan
On 03/12/2013 11:16 PM, andi_a...@dell.com wrote: -Original Message- From: crowbar-bounces On Behalf Of Adam Spiers Sent: Monday, March 11, 2013 7:28 PM To: crowbar Subject: Re: [Crowbar] how to debug Travis failures Adam Spiers (aspi...@suse.com) wrote: I'm really keen that

Re: [Crowbar] how to debug Travis failures

2013-03-12 Thread Andi_Abes
> -Original Message- > From: crowbar-bounces On Behalf Of Adam Spiers > Sent: Monday, March 11, 2013 7:28 PM > To: crowbar > Subject: Re: [Crowbar] how to debug Travis failures > > Adam Spiers (aspi...@suse.com) wrote: > > I'm really keen that I (or Jam

Re: [Crowbar] how to debug Travis failures

2013-03-11 Thread Adam Spiers
Adam Spiers (aspi...@suse.com) wrote: > I'm really keen that I (or James, or anyone else) don't become the > bottleneck on Travis builds. I really think it needs to be a > team-wide responsibility, e.g. if anyone sees test failures and thinks > they may have caused them, that they take the lead in

[Crowbar] how to debug Travis failures

2013-03-11 Thread Adam Spiers
christopher_dearb...@dell.com (christopher_dearb...@dell.com) wrote: > I submitted a pull request that should resolve most of these issues > (https://github.com/crowbar/barclamp-network/pull/158). That pull was merged > on Friday, but does not appear to be in this build. > > Could whoever is ma