yellow team mailing list archive

[Gary Poster <gary.poster@xxxxxxxxxxxxx>]

On 04/02/12 13:40, Gary Poster wrote:

> I've had some very weird test runs, as I mentioned on IRC.

The problem is that zope.testing's behavior for --subunit --list broke 
in our p5 release.  Could it be because that behavior had no tests? :-)

When you run bin/test --subunit --list you should get a list of tests 
like this:

lp.codehosting.codeimport.tests.test_dispatcher.TestCodeImportDispatcherUnit.test_dispatchJob
lp.codehosting.codeimport.tests.test_dispatcher.TestCodeImportDispatcherUnit.test_findAndDispatchJob_calls_getJobForMachine_with_limit
lp.codehosting.codeimport.tests.test_dispatcher.TestCodeImportDispatcherUnit.test_findAndDispatchJob_jobWaiting
lp.codehosting.codeimport.tests.test_dispatcher.TestCodeImportDispatcherUnit.test_findAndDispatchJob_noJobWaiting
lp.codehosting.codeimport.tests.test_dispatcher.TestCodeImportDispatcherUnit.test_findAndDispatchJobs
lp.codehosting.codeimport.tests.test_dispatcher.TestCodeImportDispatcherUnit.test_findAndDispatchJobs_sleeps
lp.codehosting.codeimport.tests.test_dispatcher.TestCodeImportDispatcherUnit.test_getHostname
lp.codehosting.codeimport.tests.test_dispatcher.TestCodeImportDispatcherUnit.test_getHostnameOverride
lp.codehosting.codeimport.tests.test_foreigntree.TestCVSWorkingTree.test_checkout
lp.codehosting.codeimport.tests.test_foreigntree.TestCVSWorkingTree.test_commit
lp.codehosting.codeimport.tests.test_foreigntree.TestCVSWorkingTree.test_module
lp.codehosting.codeimport.tests.test_foreigntree.TestCVSWorkingTree.test_path

...and so on.

That's what you see in p4.  In p5, the list looks like this:

tags: zope:layer:lp.testing.layers.BaseLayer
test: 
lp.codehosting.codeimport.tests.test_dispatcher.TestCodeImportDispatcherUnit.test_dispatchJob
successful: 
lp.codehosting.codeimport.tests.test_dispatcher.TestCodeImportDispatcherUnit.test_dispatchJob
test: 
lp.codehosting.codeimport.tests.test_dispatcher.TestCodeImportDispatcherUnit.test_findAndDispatchJob_calls_getJobForMachine_with_limit
successful: 
lp.codehosting.codeimport.tests.test_dispatcher.TestCodeImportDispatcherUnit.test_findAndDispatchJob_calls_getJobForMachine_with_limit
test: 
lp.codehosting.codeimport.tests.test_dispatcher.TestCodeImportDispatcherUnit.test_findAndDispatchJob_jobWaiting
successful: 
lp.codehosting.codeimport.tests.test_dispatcher.TestCodeImportDispatcherUnit.test_findAndDispatchJob_jobWaiting
test: 
lp.codehosting.codeimport.tests.test_dispatcher.TestCodeImportDispatcherUnit.test_findAndDispatchJob_noJobWaiting
successful: 
lp.codehosting.codeimport.tests.test_dispatcher.TestCodeImportDispatcherUnit.test_findAndDispatchJob_noJobWaiting
test: 
lp.codehosting.codeimport.tests.test_dispatcher.TestCodeImportDispatcherUnit.test_findAndDispatchJobs
successful: 
lp.codehosting.codeimport.tests.test_dispatcher.TestCodeImportDispatcherUnit.test_findAndDispatchJobs
test: 
lp.codehosting.codeimport.tests.test_dispatcher.TestCodeImportDispatcherUnit.test_findAndDispatchJobs_sleeps
successful: 
lp.codehosting.codeimport.tests.test_dispatcher.TestCodeImportDispatcherUnit.test_findAndDispatchJobs_sleeps
test: 
lp.codehosting.codeimport.tests.test_dispatcher.TestCodeImportDispatcherUnit.test_getHostname
successful: 
lp.codehosting.codeimport.tests.test_dispatcher.TestCodeImportDispatcherUnit.test_getHostname
test: 
lp.codehosting.codeimport.tests.test_dispatcher.TestCodeImportDispatcherUnit.test_getHostnameOverride
successful: 
lp.codehosting.codeimport.tests.test_dispatcher.TestCodeImportDispatcherUnit.test_getHostnameOverride

...and so on.  If we fix this, tests run.

And we get new failures quickly, presumably thanks in part to --shuffle. 
:-)  But I'll send that under separate cover.

Gary