You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The TestGoroutineMonitorStops test in pkg/pillar/cmd/watcher/watcher_test.go sometimes fails with the error:
=== FAIL: cmd/watcher TestGoroutineMonitorStops (3.03s)
Failed to write to log, write |1: file already closed
watcher_test.go:518: Expected log output to contain 'Stopping goroutines monitor'
This failure is likely due to the log output pipe being closed before the goroutines monitor has fully stopped and logged the "Stopping goroutines monitor" message. To make the stop check more reliable, we should either increase the wait time to ensure the goroutine monitor has entirely stopped before closing the log output pipe or introduce a reliable way to check that the goroutine is stopped.
The text was updated successfully, but these errors were encountered:
The TestGoroutineMonitorStops test in pkg/pillar/cmd/watcher/watcher_test.go sometimes fails with the error:
This failure is likely due to the log output pipe being closed before the goroutines monitor has fully stopped and logged the "Stopping goroutines monitor" message. To make the stop check more reliable, we should either increase the wait time to ensure the goroutine monitor has entirely stopped before closing the log output pipe or introduce a reliable way to check that the goroutine is stopped.
The text was updated successfully, but these errors were encountered: