| author | |
| committer | |
| log | 198f35c98c8a8216a120f146605bb729e7b8dd66 |
| tree | 9e52a7c65295f1c150a36c2514e2cc753a6be19d |
| parent | 19c63406d4acded72966a66ac369ccceb69173a2 |
I'm a bit confused because my understanding is that each step is
supposed to make its own decision about whether to clear its watch
inputs and start over, or retain them from the previous update. However,
without this fix in place, the problem from #35224 manifests itself
again.
Since this fix is in place in master branch, I'll leave it for now and
audit the file watching logic later.1 files changed, 1 insertions(+), 2 deletions(-)
lib/compiler/Maker/Step.zig+1-2| ... | ... | @@ -312,8 +312,7 @@ pub fn reset(step: *Step, maker: *Maker) void { |
| 312 | 312 | step.result_duration_ns = null; |
| 313 | 313 | step.result_peak_rss = 0; |
| 314 | 314 | step.test_results = .{}; |
| 315 | // We do not clearWatchInputs here because each step manages that choice | |
| 316 | // independently. | |
| 315 | clearWatchInputs(step, maker); | |
| 317 | 316 | |
| 318 | 317 | step.result_error_bundle.deinit(gpa); |
| 319 | 318 | step.result_error_bundle = std.zig.ErrorBundle.empty; |