A bit more info for those interested, I ran all the juju tests through
that tool:
go test -p 1 -v -timeout 60m github.com/juju/juju/... -check.vv
2>&1 | timestamp
and this is what it said:
total suites 1219
total test time 49m10.093s
total suite time 1h18m9.061s
total setup test 14m27.71s
total teardown test 1m10.401s
total setup suite 35.9s
total teardown suite 28m41.037s
total fixture overhead 44m55.048s
longest test 5m1.207s ( serverSuite.TestNewServerDoesNotAccessState)
setup 276ms teardown 19ms
overall time 1h18m29.001s
For the record, it produced just under 750000 lines of output (61MB)
The top 10 longest tests are these:
serverSuite.TestNewServerDoesNotAccessState 301.207
StatusHistorySuite.TestPruneStatusHistoryBySize 83.978
UniterSuite.TestActionEvents 41.471
localServerSuite.TestStopInstanceSecurityGroupNotDeleted 29.152
UniterSuite.TestUniterRelations 21.693
ShowOutputSuite.TestRun 18.056
StatusSuite.TestStatusAllFormats 15.697
oplogSuite.TestWithRealOplog 15.503
kvmProvisionerSuite.TestContainerStartedAndStopped 15.465
lxcProvisionerSuite.TestContainerStartedAndStopped 15.366
I suspect there's a bunch of low hanging fruit that can
be picked to speed up the tests.
cheers,
rog.
On 17 May 2016 at 03:52, David Cheney <[email protected]> wrote:
> Testing this package takes 16 minutes on my machine*; it sure didn't
> use to take this long.
>
> What happened ?
>
> * yes, you have to raise the _10 minute_ timeout to make this test 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
