Don't wait unnecessarily.

tests/stub-generator/testcfg.py

Index: tests/stub-generator/testcfg.py
===================================================================
--- tests/stub-generator/testcfg.py	(revision 999)
+++ tests/stub-generator/testcfg.py	(working copy)
@@ -39,6 +39,9 @@
     (interface, _, implementation) = interface.partition('+')
     return (interface, classes, implementation)
 
+  def IsFailureOutput(self, output):

[floitsch, 2011/11/02 14:34:27]

Are you sure this is necessary?
Do all components now support 'print' in testing mode?

[Ben Laurie (Google), 2011/11/02 14:45:44]

Yes, without it the test can exit early and appear to work even though it does
not.
I don't know, but we need _some_ equivalent mechanism or we cannot, in general,
test asynchronous code.

Being able to set an exit code would be another example of a method that should
work.

[floitsch, 2011/11/02 16:04:17]

The testing-infrastructure should make sure this is not the case. If not, please
give us an example so that we can fix the test-framework. (This is the whole
reason why you have to write expect.succeeded().)

[Ben Laurie (Google), 2011/11/02 21:09:34]

How? AFAICS it does not achieve that: for example, if I return with outstanding
promises, the result is never tested.

+    return output.exit_code != 0 or not '##DONE##' in output.stdout
+
   def BeforeRun(self):
     if not self.context.generate:
       return