tests: Explicitly unset SOURCE_DATE_EPOCH before running fs tests

In some filesystem utils like mksquashfs, they will silently change
behaviour and cause timestamps to unexpectedly change. Build
environments like Debian's set SOURCE_DATE_EPOCH in the environment,
so remove it. Reproducible builds are good and useful for shipped
artifacts, but this causes build-time tests to fail.

Signed-off-by: Steve McIntyre <steve@einval.com>
Reviewed-by: Daniel Kiper <daniel.kiper@oracle.com>

diff --git a/tests/util/grub-fs-tester.in b/tests/util/grub-fs-tester.in
index 43f6175c3b892d7f4506e1a01c1f94177f02a19c..7a48c4399cdb04c2739862bb0ee24edb0c00c8fc 100644 (file)
--- a/tests/util/grub-fs-tester.in
+++ b/tests/util/grub-fs-tester.in
@@ -3,6 +3,9 @@
 set -e
 export BLKID_FILE=/dev/null
 
+# We can't have this set, or filesystem tests will fail.
+unset SOURCE_DATE_EPOCH
+
 fs="$1"
 
 GRUBFSTEST="@builddir@/grub-fstest"