#22919 would help with unit tests. TLS enabled etcd for registry unit test packages is pretty slow

Timed out again
https://pantheon.corp.google.com/storage/browser/kubernetes-jenkins/logs/kubernetes-test-go/9953/

And again
https://pantheon.corp.google.com/storage/browser/kubernetes-jenkins/logs/kubernetes-test-go/9986/
This makes it twice in two days. Maybe we need to bump the priority.

@spxtr to delegate

The suite used to take about 35 minutes, then for a few days it started taking 42 minutes, and now it's back to 35 minutes. Rather than bump up the timeout, we need to figure out which test has slowed down and why.

If it's something expected or out of our control then increasing the timeout is fine.

did the slowdowns coincide with #21535 merging? we saw that make all the registry package unit tests take 3x as long, and some hit the 1 minute package timeout

The original slowdown was caused by #21535, but it has improved somewhat since.

I made a quick plot of kubernetes-test-go test times for the last thousand or so. The huge spike was #21535, and we recovered most of the way but not all the way. Sometime yesterday we improved again.

Any interest in #22919, which runs the individual registry package units with non-tls etcd?

That looks like it might improve this significantly :)

Anyway, we're back down to ~35 minutes. Closing this issue.