On 06/28/2012 08:53 AM, Matt Wagner wrote:
On Wed, Jun 27, 2012 at 06:12:14PM -0700, Richard Su wrote:
> You may have already noticed from our first build status email from
> Travis CI.
Might we be able to turn off notifications until tests are expected to
pass? My fear is that if we don't, people will get used to tuning out
the notifications as "noise," versus being alarmed that the build just
broke.
Yes, notifications can be turned off. I can go either way, it is a bit
noisy until the tests are expected to pass, but having them around does
keep the need to fix them visible. What do other people think?
> For upstream, tests are kicked off when a change is committed to
> aeolusproject/github. The tests consists of running cucumber and
> rspec in a Bundler environment and reporting their results. No rpms
> are installed and aeolus-configure is not executed.
This is awesome! Thanks for seeing this through.
> Many tests are broken, around 18 for cucumber and around 228 for
> rspec. These are known issues because some of our tests are dependent
> on having services like deltacloud-core up. I believe Jay is already
> helping to fix some of these. The plan is to get more people on board
> to fix the others in future sprints.
Sign me up to help as needed with tackling failures!
-- Matt