running the test suite in parallel fails

[Robert Collins]

I ran the test suite in parallel (as the 5 minute run time was a bit tedious) and found that the test suite is not concurrency safe.

To reproduce, make a file .testr.conf containing:
======
[DEFAULT]
test_command=./test --reporter=subunit $LISTOPT $IDLIST
test_list_option=-n
======

And run 'testr run --parallel'.

And watch the fireworks.

[Robert Collins (lifeless)]

(note: moving from trial to testtools may help with this as testtools doesn't have a singleton test dir, and that avoids a whole class of concurrency issues with log files etc).

[Kapil Thangavelu (hazmat)]

I'd say Importance -> Low, we're hovering around 2m atm for 2.1k tests, w/
sec 3. that seems fine to me.

On Sat, Sep 29, 2012 at 3:01 AM, Clint Byrum <email address hidden> wrote:

> ** Changed in: juju
> Importance: Undecided => Medium
>
> --
> You received this bug notification because you are subscribed to juju.
> https://bugs.launchpad.net/bugs/1017273
>
> Title:
> running the test suite in parallel fails
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1017273/+subscriptions
>

[Clint Byrum (clint-fewbar)]

I have confirmed this does not work. Leaving it at Medium as improving test runs should mean more efficient development, even if we take it from 2m to 1m.. until it is 30s or less, it will be tedious.

[Kapil Thangavelu (hazmat)]

it should be possible to chroot the various zk clients by pid to allow for parallel testing.