Nondeterministic CI failures due to Makefile recompliation checking in heapster-tests
#1801
Labels
tooling: CI
Issues involving CI/CD scripts or processes
The CI is nondeterministically failing on the
heapster-tests
job, as seen in this example:At first glance, this seems off, since we have already checked in a
rust_data.bc
file that is known to work withllvm-pretty-bc-parser
. But the output above is only half of the story. Earlier in the CI log, we see this:This is rebuilding the
rust_data.bc
file, but with a more recent version ofrustc
than what was used to originally compile it! This is terrible, because (1) this produces different bitcode than what we want to test, and (2) the bitcode that newerrustc
s emit will not supportllvm-pretty-bc-parser
(at least, not in its current state).@kquick notes that
make
will rebuild a.bc
file if its creation timestamp is different than its modified timestamp. Normally, these timestamps are set to the same time due to the waygit clone
works, but there can occasionally be ever-so-slight delays during the checkout process that cause the modified time to be later than the created time. That is most likely whyrust_data.bc
(and onlyrust_data.bc
) is being rebuilt in the CI log above, as it was the one.bc
file in the Heapster examples directory that happened to suffer from an ever-so-slight delay during the checkout process.We should figure out a way to avoid this. One possible solution is to run
touch *.bc
before runningmake
to ensure that the created and modified timestamps are the same.The text was updated successfully, but these errors were encountered: