We don't want klog to print to anything other than GinkgoWriter, but it still used os.Stderr in addition to GinkgoWriter when printing log entries with severity >= error. Changing "stderrthreshold" fixes that. The unit test for framework output handling didn't test klog behavior. Now it does: - os.Stderr is redirected, should be empty - a new test invokes klog
5.7 KiB
5.7 KiB