Open Stack

>
> So... test jobs should be extremely explicit about what they setup and
> what they expect.


+2

Best regards,
Boris Pavlovic

On Thu, May 7, 2015 at 9:44 PM, Sean Dague <sean at dague.net> wrote:

> On 05/07/2015 02:29 PM, Joshua Harlow wrote:
> > Boris Pavlovic wrote:
> >> Sean,
> >>
> >> Nobody is able to track and know *everything*.
> >>
> >> Friendly reminder that Heat is going to be removed and not installed by
> >> default would help to avoid such situations.
> >
> > Doesn't keystone have a service listing? Use that in rally (and
> > elsewhere?), if keystone had a service and each service had a API
> > discovery ability, there u go, profit! ;)
>
> Service listing for test jobs is actually quite dangerous, because then
> something can change something about which services are registered, and
> you automatically start skipping 30% of your tests because you react
> correctly to this change. However, that means the job stopped doing what
> you think it should do.
>
> *This has happened multiple times in the past*. And typically days,
> weeks, or months go by before someone notices in investigating an
> unrelated failure. And then it's days, weeks, or months to dig out of
> the regressions introduced.
>
> So... test jobs should be extremely explicit about what they setup and
> what they expect.
>
>         -Sean
>
> --
> Sean Dague
> http://dague.net
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150507/ffcab2ea/attachment.html>