=== RUN TestJoyent ... PASS: config_test.go:1: localServerSuite.TestBootstrap 33.078s PASS: local_test.go:310: localServerSuite.TestBootstrapInstanceUserDataAndState11.614s PASS: local_test.go:401: localServerSuite.TestDeleteMoreThan100 59.346s ... PASS: local_test.go:259: localServerSuite.TestInstanceStatus 9.211s PASS: local_test.go:268: localServerSuite.TestInstancesGathering 16.579s PASS: config_test.go:1: localServerSuite.TestPersistence 6.136s PASS: local_test.go:380: localServerSuite.TestRemoveAll 10.778s PASS: local_test.go:190: localServerSuite.TestStartInstance 16.061s PASS: local_test.go:200: localServerSuite.TestStartInstanceHardwareCharacteristics 14.309s PASS: config_test.go:1: localServerSuite.TestStartStop 14.874s ... PASS: config_test.go:1: localLiveSuite.TestBootstrapMultiple 24.822s ... PASS: config_test.go:1: localLiveSuite.TestFile 8.150s PASS: config_test.go:1: localLiveSuite.TestGlobalPorts 14.838s PASS: config_test.go:1: localLiveSuite.TestPorts 18.891s ... PASS: config_test.go:1: localLiveSuite.TestStartInstanceWithEmptyNonceFails 10.556s PASS: config_test.go:1: localLiveSuite.TestStartStop 10.287s OK: 40 passed, 5 skipped --- PASS: TestJoyent (302.18 seconds) PASS ok launchpad.net/juju-core/provider/joyent 302.280s
So that is around 5 minutes to run the joyent tests, with the slowest ones highlighted. I have a feeling they have some sort of eventual consistency loops that aren't getting overridden inside the test suite. (Compared with openstack: PASS: live_test.go:1: localServerSuite.TestBootstrap 3.597s ) Still, 5min is still well within the 10m boundary, and we could probably ratchet it down a bit. This *is* something that is going to get run everytime we submit a patch, so adding 5m to the test suite is worth spending some time debugging. John =:-> On Wed, Apr 2, 2014 at 1:09 PM, Ian Booth <[email protected]> wrote: > > On 02/04/14 19:00, John Meinel wrote: > > And one more change was to make it: > > go test -test.timeout 10m ./... > > > > I don't really know how tight of a lower bound we could make it (I know > we > > have tests that take at least 2m regularly). But in the end, I don't > really > > care (yet). I want us to get tracebacks when the tests take too long, > which > > is currently at 10m. Eventually I'd like us to ratchet down our test > suite, > > but we can get there later. > > > > The recently added Joyent tests take a long time to run. But I wanted to > get the > code committed so it could be included in 1.18. The tests do need some > love and > attention to figure out why they take so long to run. > > -- > Juju-dev mailing list > [email protected] > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju-dev >
-- Juju-dev mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
