Avoiding writing ninjalog.cfg unnecessarily
Writing to ninjalog.cfg comes with the risk of failure (Ctrl+C at the wrong time) which can lead to an empty or corrupted file. This will cause errors on subsequent builds when loading the config file, and will lose the users opt-in/out settings. This change ensures that the config file is only written when something has changed, thus essentially avoiding the risk. Bug: 941810 Change-Id: If266f07536569c9ac91ee37c28797c8b2ccc6fdc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/tools/depot_tools/+/1522291 Reviewed-by: Takuto Ikuta <tikuta@chromium.org> Reviewed-by: Fumitoshi Ukai <ukai@chromium.org> Commit-Queue: Bruce Dawson <brucedawson@chromium.org>changes/91/1522291/2
							parent
							
								
									8e85c22df6
								
							
						
					
					
						commit
						cf9613f166
					
				
					Loading…
					
					
				
		Reference in New Issue