Hi Scott, * John Scott <jsc...@posteo.net> [2021-05-03 00:35]:
Has anyone been able to reproduce this? Attempting to build Sage in a fresh unstable environment succeeds for me; perhaps the build failure was spurious.
I triggered reproducible builds yesterday: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/sagemath.html The problem Lucas found is: * Lucas Nussbaum <lu...@debian.org> [2021-04-07 08:51]:
make[4]: Entering directory '/<<PKGBUILDDIR>>' Error: 210 tests failed, up to 200 failures are tolerated make[4]: *** [debian/rules:165: had-few-failures] Error 1
whereas the RB runs above produced: Success: 41 tests failed, up to 200 failures are tolerated Success: 5 tests failed, up to 200 failures are tolerated The 200 is set in debian/rules: https://salsa.debian.org/science-team/sagemath/-/commit/6088e9f2abc7ae99a8d07760ceee6fb6aac7bb54and sounds a little arbitrary. Sadly the state upstream seems not to be much better:
https://github.com/sagemath/sage/tree/9.2 13 failing, 17 cancelled, and 70 successful checks (I did not look into them.)So I think the question is rather if the test suite gives an appropriate view on the quality of the software. If it does, I assume it is not appropriate for a Debian stable release. Contrary if we assume the test suite being broken, we could disable it completely rather then producing random FTBFS.
Cheers Jochen
signature.asc
Description: PGP signature
