race conditions breaking the build by way of Jasmine/Karma unit tests?

It's a thing. Everything can pass locally and then the Octopus build can break seemingly inexplicably. When this happens there is some asynchronous horror wreaking havoc in a unit test. Beautiful. In my case when I defined a useValue for a mock right there inside of my test all was well, but when I tried to pull in a stub object for an IoC contract in an Angular application the stub could not be found when testing inside ngOnInit against a component, or perhaps it was being found but Jasmine acted like the method I was calling was not a function.