packaging
/
ostree
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

tests: Unset SOURCE_DATE_EPOCH 

Some distributions set this during build in order to have reproducible
builds from the same source code: for example, Debian uses the date
from debian/changelog.

However, some of our tests assume that `ostree commit` will result in
a commit with the current date/time, and SOURCE_DATE_EPOCH breaks that
assumption. Unset it for our build-time tests.

Resolves: https://github.com/ostreedev/ostree/issues/2405
Signed-off-by: Simon McVittie <smcv@collabora.com>
This commit is contained in:
Simon McVittie 2021-07-26 11:48:45 +01:00
parent 420952595b
commit 2c5fa2cdb6
2 changed files with 9 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
ci/gh-build.sh
View File

@ -44,6 +44,11 @@ ${make}
# Run the tests both using check and distcheck. # Run the tests both using check and distcheck.
${make} check ${make} check
# Some tests historically failed when package builds set this.
# By setting it for distcheck but not check, we exercise both ways.
export SOURCE_DATE_EPOCH=$(date '+%s')
${make} distcheck DISTCHECK_CONFIGURE_FLAGS="$*" ${make} distcheck DISTCHECK_CONFIGURE_FLAGS="$*"
# Show the installed files # Show the installed files

4
tests/libtest.sh
View File

@ -69,6 +69,10 @@ if ! test -f .testtmp; then
touch .testtmp touch .testtmp
fi fi
# Some distribution builds set this, but some of our build-time tests
# assume this won't be used when committing
unset SOURCE_DATE_EPOCH
# Also, unbreak `tar` inside `make check`...Automake will inject # Also, unbreak `tar` inside `make check`...Automake will inject
# TAR_OPTIONS: --owner=0 --group=0 --numeric-owner presumably so that # TAR_OPTIONS: --owner=0 --group=0 --numeric-owner presumably so that
# tarballs are predictable, except we don't want this in our tests. # tarballs are predictable, except we don't want this in our tests.