On Tue, Oct 07, 2014 at 04:28:23PM +0100, Chris Dent wrote:
> On Mon, 25 Aug 2014, Joe Gordon wrote:
> >On Mon, Aug 4, 2014 at 3:29 AM, Chris Dent wrote:
> >>For constraints: Will tempest be available as a stable library? Is using
> >>tempest (or other same library across all projects) a good or b
On Mon, 25 Aug 2014, Joe Gordon wrote:
On Mon, Aug 4, 2014 at 3:29 AM, Chris Dent wrote:
For constraints: Will tempest be available as a stable library? Is using
tempest (or other same library across all projects) a good or bad thing?
Seems there's some disagreement on both of these.
Yes, the
On Mon, Aug 25, 2014 at 2:50 PM, Chris Dent wrote:
> On Mon, 25 Aug 2014, Joe Gordon wrote:
>
> [Other stuff snipped, thanks for that, good to have some pointers.]
>
>
> Why can't you run devstack locally? Maybe there are some changes we can
>> make so its easier to run devstack locally first.
>
On Mon, 25 Aug 2014, Joe Gordon wrote:
[Other stuff snipped, thanks for that, good to have some pointers.]
Why can't you run devstack locally? Maybe there are some changes we can
make so its easier to run devstack locally first.
I do run a local devstack, and throw in some tempest and grenade
On Mon, Aug 4, 2014 at 3:29 AM, Chris Dent wrote:
>
> In the "Thoughts on the patch test failure rate and moving forward"
> thread[1] there's discussion of moving some of the burden for
> functional testing to the individual projects. This seems like a good
> idea to me, but also seems like it co
In the "Thoughts on the patch test failure rate and moving forward"
thread[1] there's discussion of moving some of the burden for
functional testing to the individual projects. This seems like a good
idea to me, but also seems like it could be a source of confusion so I
thought I'd start another
