Colin Cross b0b369c4fa Stop NinjaReader from sending new status messages after Close ... If NinjsReader keeps sending tool status messages after Close has been called it can cause a concurrent map access when CriticalPath.WriteToMetrics is called concurrently with CriticalPath.FinishAction. Try harder to stop the NinjaReader goroutine when NinjaReader.Close is called, even if the external ninja process has not closed its FIFO or NinjaReader has not finished processing all the messages after 5 seconds. Bug: 286382228 Test: m nothing Change-Id: I3e3dce601510e2dfb5ed82ca55bd11723fac7e70		2023-09-05 11:11:29 -07:00
..
build_error_proto
build_progress_proto
ninja_frontend	Include tags in trace data.	2023-06-21 20:17:57 +00:00
Android.bp	Add critical path infomation into metrics	2023-03-14 17:59:22 +09:00
critical_path.go	Add time unit for CriticalPathInfo's fields' name	2023-03-16 18:29:55 +09:00
critical_path_logger.go	Add critical path infomation into metrics	2023-03-14 17:59:22 +09:00
critical_path_test.go	Add critical path infomation into metrics	2023-03-14 17:59:22 +09:00
kati.go	Update tests for a changed status message.	2023-06-26 07:05:07 +00:00
kati_test.go	Update tests for a changed status message.	2023-06-26 07:05:07 +00:00
log.go
ninja.go	Stop NinjaReader from sending new status messages after Close	2023-09-05 11:11:29 -07:00
ninja_test.go
status.go	Include tags in trace data.	2023-06-21 20:17:57 +00:00
status_test.go