I was actually trying to avoid talking about the test itself to keep things shorter ;)
The test is parsing the entire codebase under github.com/juju/juju to look for places where we're creating a new value of crypto/tls.Config instead of using the new helper function that I wrote that creates one with more secure defaults. There's not really any getting around the fact that parsing the whole tree takes a long time. On Wed, Apr 27, 2016 at 1:25 PM Nicholas Skaggs < nicholas.ska...@canonical.com> wrote: > This is a timely discussion Nate. I'll avoid saying too much off the > top, but I do have a question. > > On 04/27/2016 12:24 PM, Nate Finch wrote: > > I just wrote a test that takes ~16.5 seconds on my machine. > Why does the test take so long? Are you intending it to be a short / > small scoped test? > > Nicholas >
-- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
