Hi,
On 5/18/21 8:25 PM, Jochen Sprickerhof wrote:
>
> I think there are a number of problems:
> - Tests not being executed due to the open file limit ("Killing test" in
> the log). If you want to use the tests as an indicator if the build works,
> you should make sure the all tests are executed, otherwise 200 tolerated
> failures is arbitrary.
I have been struggling with this for quite a while and I don't know how to fix
it. It comes and goes and does not seem to affect vanilla upstream builds. This
has impacted progress on the package since one cannot properly work on it when
the test suite crashes. I tried asking upstream for help here and provided more
details:
https://groups.google.com/g/sage-packaging/c/1G_3JiIcbvY
> - I found a number of segfaults in the tests, like:
> sage -t --long --random-seed=0 src/sage/interfaces/singular.py # Killed
> due to segmentation fault
> - Looking at the amd64 log of the buildd:
> Error: 202 tests failed, up to 200 failures are tolerated
> Yes: 202 tests failed, up to 400 failures are tolerated for rerun
> Success: 192 tests failed, up to 200 failures are tolerated
> does that mean we ran the test twice and it passed the second time cause
> there where 10 failures less? Can we be sure that this always succeeds? 192
> is really close to 200.
> - I still see cython: not found in the logs, so there are definitely tests
> broken due to that. Maybe it makes sense to define tests which are allowed
> to break and other which should succeed?
I agree, segfaults and the cython issue should be fixed. The number of failed
tests always grows with time when dependencies change and sagemath is not
adapted accordingly.
Best,
Tobias
