Re: Bug#1003181: cython: sparc64 is not building cython ("Not For Us")

2022-01-06 Thread Drew Parsons
On 2022-01-06 22:38, John Paul Adrian Glaubitz wrote: Hello! On 1/5/22 18:02, Drew Parsons wrote: cython previously built on sparc64 for bullseye (stable) at version 0.29.21-3 Now (for version 0.29.24-2), cython is marked "Not For Us" on sparc64 and is no longer building. The package is

Re: Bug#1003181: cython: sparc64 is not building cython ("Not For Us")

2022-01-06 Thread John Paul Adrian Glaubitz
Hello! On 1/5/22 18:02, Drew Parsons wrote: > cython previously built on sparc64 for bullseye (stable) at version 0.29.21-3 > > Now (for version 0.29.24-2), cython is marked "Not For Us" on sparc64 > and is no longer building. The package is currently blocked on sparc64 because the testsuite

Re: Bug#1003181: cython: sparc64 is not building cython ("Not For Us")

2022-01-06 Thread John Paul Adrian Glaubitz
On 1/6/22 22:54, Drew Parsons wrote: >> I will build the current version manually for now with the testsuite >> disabled and >> upload the package. > > Thanks Adrian. I guess disabling tests permanently for sparc64 is a > reasonable > (if regrettable) work-around if they continue to cause

Re: Bug#1003181: cython: sparc64 is not building cython ("Not For Us")

2022-01-06 Thread Gregor Riepl
> The package is currently blocked on sparc64 because the testsuite kept > crashing > the host system and no solution was found yet. It seems that the testsuite > will > put a lot of strain on the host system when the machine has many CPU cores > which > is true for most sparc64 systems we use.

Re: Bug#1003181: cython: sparc64 is not building cython ("Not For Us")

2022-01-06 Thread Drew Parsons
On 2022-01-06 23:00, John Paul Adrian Glaubitz wrote: On 1/6/22 22:54, Drew Parsons wrote: I will build the current version manually for now with the testsuite disabled and upload the package. Thanks Adrian. I guess disabling tests permanently for sparc64 is a reasonable (if regrettable)