Activity log for bug #107371
| Date | Who | What changed | Old value | New value | Message |
|---|---|---|---|---|---|
| 2007-04-18 01:34:54 | Jonathan Lange | bug | added bug | ||
| 2007-09-26 19:23:17 | Francis J. Lacoste | launchpad: importance | Undecided | Wishlist | |
| 2007-09-26 19:23:17 | Francis J. Lacoste | launchpad: status | New | Confirmed | |
| 2009-08-27 04:48:30 | Jonathan Lange | tags | feature test-system | build-infrastructure feature test-system | |
| 2009-09-09 00:30:35 | Michael Hudson-Doyle | summary | Make the test suite able to be run in parallel | Make the test suite able to be run in parallel on a single machine | |
| 2010-02-22 21:15:07 | Michael Hudson-Doyle | description | At the moment, you can't run the test suite in the background and continue to work on other branches (in particular, running tests in those other branches). The test suite trashes a single, global database listens on hard-coded ports, and writes to files in hardcoded absolute paths. This is a big barrier to running 'make check' on developer workstations. | At the moment, you can't run the test suite in the background and continue to work on other branches (in particular, running tests in those other branches). The test suite trashes a single, global database which listens on hard-coded ports, and writes to files in hard-coded absolute paths. This is a big barrier to running 'make check' on developer workstations. | |
| 2012-02-01 02:25:11 | Robert Collins | tags | build-infrastructure feature lp-foundations test-system | build-infrastructure feature lp-foundations parallelteset test-system | |
| 2012-05-30 21:34:05 | Curtis Hovey | tags | build-infrastructure feature lp-foundations parallelteset test-system | build-infrastructure feature lp-foundations paralleltest test-system |
