Use time tolerance in run_code_generation check.

The mtime values I was seeing on my file system were sometimes floating point numbers that were very very close but not exactly the same. This might be due to numerical errors. Increasing the tolerance to something still very small, precision is less than a second. It will lead to fewer rebuilds of non-dirty files. Bug: angleproject:2455 Change-Id: I95dc3214ee91af7a70a20cc625405e0e2bc18698 Reviewed-on: https://chromium-review.googlesource.com/1032855Reviewed-by: Luc Ferron <lucferron@chromium.org> Commit-Queue: Jamie Madill <jmadill@chromium.org>

Use time tolerance in run_code_generation check.
0ade8e88 · Jamie Madill · Commit Bot · b90779eb · 0ade8e88
Commit 0ade8e88 authored Apr 27, 2018 by Jamie Madill Committed by Commit Bot Apr 30, 2018
Hide whitespace changes
Inline Side-by-side

Showing with 2 additions and 1 deletion

run_code_generation.py scripts/run_code_generation.py +2 -1

No files found.
--- a/scripts/run_code_generation.py
+++ b/scripts/run_code_generation.py
@@ -204,7 +204,8 @@ for name, info in sorted(generators.iteritems()):
                dirty = True
            else:
                output_mtime = os.path.getmtime(foutput)
-                if input_mtime > output_mtime:
+                # Use a fuzzy comparison to avoid tiny time delta errors.
+                if input_mtime - output_mtime > 0.1:
                    dirty = True
    if dirty: