I just discussed this briefly with pitti. Since:
* breaks-testbed tests are currently not supported in our infrastructure, and we think that using one will cause the testing infrastructure to treat it as a failure. * Server tests are generally breaks-testbed. but: The infrastructure will happen to work fine with one test that is breaks-testbed but isn't declared as such, and: I want to write more than one test, since test cases are still handy to run locally and store somewhere, even if we can't use them in automation, I'm going to: Write and upload additional tests anyway, but leave them commented out in debian/tests/control for now, except for the first one where I will not declare breaks-testbed even though it is. This way, we can still get more usefulness out of the first test, and subsequent tests will be there, can be used manually, and eventually be supported when the infrastructure can support breaks-testbed correctly. -- Ubuntu-quality mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
