[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

reprotest fails in dh_auto_test. What to do?



Dear Mentors,

my package parlatype is failing reprotest in dh_auto_test. In detail a
test in appstream-util is failing: it checks the release date in shipped
appstream data and if the time is varied, that release date is in the
future, resulting in a failed test, failed build and failed reprotest.
Log output is:

--- command ---
/usr/bin/appstream-util validate-relax --nonet
com.github.gkarsay.parlatype.appdata.xml
--- stdout ---
com.github.gkarsay.parlatype.appdata.xml: FAILED:
• attribute-invalid     : <release> timestamp is in the future
--- stderr ---
Validation of files failed
-------

This is not uploaded yet, only in Debian Salsa:
https://salsa.debian.org/gabork-guest/parlatype

What would be the best solution to this problem::

1) Disabling appstream-util test entirely.

2) Running reprotest with DEB_BUILD_OPTIONS=nocheck
There is a commit for Salsa CI pipeline removing this option because it
might hide reproducibility problems:
https://salsa.debian.org/salsa-ci-team/pipeline/commit/4942def0eac1808aeead80cd87e8d4c6560a96f1

There is a similar discussion in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786644 "reproducible
builds should vary whether nocheck is added to DEB_BUILD_OPTIONS"

This package doesn't change the binary during the test. The first build
could be run with the test, the second build could be run without and
there should be no difference in the binary.

I understand I could change this in Salsa CI, but not for the tests run
on the archive. I failed to find out which options are used for the
repro tests run on the archive and I guess they can't be changed on a
per-package basis?

3) Is there a possibility to continue reprotest even if dh_auto_test
failed, making it non-fatal?

Those are the solutions I could think of, what would you advise?

Regards,
Gabor


Reply to: