Check that all Outputs are newer than Inputs after targets run #3817
Labels
Area: Debuggability
Issues impacting the diagnosability of builds, including logging and clearer error messages.
Feature Request
Feature: Warning Waves
Warnings to enable in opt-in waves. Formerly "strict mode".
triaged
See KirillOsenkov/MSBuildStructuredLog#204 proposed by @garuma.
There are cases where a target runs because some of its inputs are more recent than its outputs but by the end of the target the inputs are still more recent than the outputs (which should not be the case).
This is a widespread problem because a lot of targets authors use some variant of a CopyIfChanged mechanism that break this invariant.
I imagine this check should be off by default, but easy to turn on (either via an environment variable, or setting a property?). There maybe should be a way to turn this check on per target.
The text was updated successfully, but these errors were encountered: