Thanks - applied.
On Thu, Feb 9, 2017 at 8:20 PM, Atira Odhner wrote:
> It looks like there was some test setup logic that happened in test_utils.py
> that was node-name specific. We've removed that logic and re-enabled
> cleaning up the test databases.
>
> Tira & George
>
> On Thu, Feb 9, 2017 a
It looks like there was some test setup logic that happened in
test_utils.py that was node-name specific. We've removed that logic and
re-enabled cleaning up the test databases.
Tira & George
On Thu, Feb 9, 2017 at 7:16 AM, Dave Page wrote:
> Hi
>
> On Wed, Feb 8, 2017 at 9:37 PM, Atira Odhner
Hi
On Wed, Feb 8, 2017 at 9:37 PM, Atira Odhner wrote:
> Here is the additional patch to exclude one or more packages.
>
> On Tue, Feb 7, 2017 at 6:02 PM, George Gelashvili
> wrote:
>>
>> Hello Hackers,
>>
>> To chase down a set of tests that were failing together, we wanted to run
>> deeper tre
Here is the additional patch to exclude one or more packages.
On Tue, Feb 7, 2017 at 6:02 PM, George Gelashvili
wrote:
> Hello Hackers,
>
> To chase down a set of tests that were failing together, we wanted to run
> deeper trees of tests. We changed the behavior of the --pkg argument to
> runtes
Hello Hackers,
To chase down a set of tests that were failing together, we wanted to run
deeper trees of tests. We changed the behavior of the --pkg argument to
runtests.py so it runs tests under a package and its subpackages, instead
of for a single node.
It gave us more flexibility in what test
