Calling klog.FlushAndExit causes the `go test` binary to quit without properly recording which test failed. Both callers of StartScheduler already have a ktesting.TContext, so switching to that is easy and also reduces the number of parameters.