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 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 resolving them.
Yup.. as you might notice from the latest set of activity, there's been a
concerted effort to fix the test failures.
Yes we noticed that, awesome!
One thing that caused some confusion is the distinction between:
a) the machinery that runs the tests - i.e travis itself,
b) the update-git cron job, and its activities
c) the actual test failures.
AFAIK:
we're not going to mess with travis proper :), so that takes care of a).
update-git ( b) above. If I understand correctly, you have it covered - in some
remote corner of your lab there's a server that dutifully runs this on a 5
minute interval? At this point, we're not running a similar process, making
your server the only trigger for updating the travis repo. (so if it was
running on your laptop and you went home for the weekend, no tests will be
triggered till you were back ;).
Should we setup a mirror of this process, to avoid a SPOF? It appears
relatively safe to run multiple copies - or do you suspect that Bad Things will
happen (e.g. the 2 instances resulting in some sort badness ?). It appears that
the script does a 'git push -f' so merge conflicts are not likely.
The update-git cron job was running in a VM on my workstation (as a
stop-gap measure). However it stopped working properly a couple of weeks
back while I was away, and so Adam has moved it to
http://ci.opensuse.org/job/crowbar-travis_ci-trackupstream/. We'll be
updating the documentation in github.com soon to reflect this.
As for c)... yes. Definitely. I think we've been doing that.
+1000
Cheers,
James T.
_______________________________________________
Crowbar mailing list
Crowbar@dell.com
https://lists.us.dell.com/mailman/listinfo/crowbar
For more information: http://crowbar.github.com/
