I think I've figured out the issue; events associated with deployments don't
specify their ordering. New patchset on its way.
Mainn
----- Original Message -----
From: "Jason Guiditta" <jguiditt(a)redhat.com>
To: "Tzu-Mainn Chen" <tzumainn(a)redhat.com>
Cc: aeolus-devel(a)lists.fedorahosted.org
Sent: Tuesday, May 15, 2012 5:33:26 PM
Subject: Re: [PATCH 0/2 conductor] fix a few broken tests
On 15/05/12 13:13 -0400, Tzu-Mainn Chen wrote:
>Fixes a few broken tests exposed as result of soft_delete patchset.
>
>Mainn
>
As discussed in irc, this gets all but one spec passing for me. The
failure is:
Failures:
1) Deployment.uptime_1st_instance with events return nil when
instances are running but event with status code 'first_running'
doesn't exist'
Failure/Error: deployment.uptime_1st_instance.should == nil
expected: nil
got: 10047283.058612 (using ==)
# ./spec/models/deployment_spec.rb:480
Finished in 1004.28 seconds
704 examples, 1 failure