Skip to content

Commit 5dc16db

Browse files
Hack to ensure core.a looks newer during builds
Commented in the code, but buasically the generation of git version includes on each build causes the cached core.a to be ignored because that header is newer than the file we just wrote (even though on any CI run the GIT version is identical).
1 parent e34acb7 commit 5dc16db

File tree

1 file changed

+8
-0
lines changed

1 file changed

+8
-0
lines changed

tests/common.sh

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -52,6 +52,14 @@ function build_sketches()
5252
if [ $testcnt -ne $build_rem ]; then
5353
continue # Not ours to do
5454
fi
55+
56+
# Uber hack warning - setting the cached core.a file to the future to
57+
# ensure it is accepted as unmodified during build process. Problem is
58+
# the git version header is rewritten after each compile, so the
59+
# builder sees it is new and says "rebuild the whole thing!"
60+
61+
if [ -e $cache_dir/core/*.a ]; then touch -t 203712310000 $cache_dir/core/*.a; fi
62+
5563
rm -rf $build_dir/*
5664
local sketchdir=$(dirname $sketch)
5765
local sketchdirname=$(basename $sketchdir)

0 commit comments

Comments
 (0)