Hi Graham,

Thanks for making me aware ... this is probably related to this PR which was 
just accepted upstream:
https://github.com/silx-kit/pyFAI/pull/1729
Apparently, Michael Hudson-Doyle is from Ubuntu and the bugs addressed are 
exactly those...

Unfortunately, there is no release planed in the foreseeable future ... 
Cheers,

Jerome (upstream author of pyFAI)

On Wed, 31 Aug 2022 08:35:02 +0200
Graham Inggs <gin...@debian.org> wrote:

> Source: pyfai
> Version: 0.21.3+dfsg1-1
> Severity: important
> User: debian...@lists.debian.org
> Usertags: regression
> 
> Hi Maintainer
> 
> The autopkgtests of pyfai have regressed on armel and i386 [1][2],
> where they passed previously (see results of e.g. 0.20.0+dfsg1-3).  I
> have copied what I hope is the relevant part of the log below.
> 
> These test failures are known upstream, as can be seen in the
> following code snippets.
> 
> pyFAI/test/test_histogram.py:
> @unittest.skipIf(UtilsTest.low_mem, "test unreliable on 32bits processor")
> def test_count_csr(self):
> 
> pyFAI/test/test_histogram.py:
> @unittest.skipIf(UtilsTest.low_mem, "test unreliable on 32bits processor")
> def test_numpy_vs_cython_vs_csr_2d(self):
> 
> pyFAI/test/test_csr.py:
> @unittest.skipIf(UtilsTest.low_mem, "test unreliable on 32bits processor")
> def test_2d_nosplit(self):
> 
> This was noticed in Ubuntu, when the upload of glibc 2.36 caused the
> same tests to start failing on armhf.
> 
> Regards
> Graham
> 
> 
> [1] https://ci.debian.net/packages/p/pyfai/unstable/armel/
> [2] https://ci.debian.net/packages/p/pyfai/unstable/i386/
> 
> 
> ======================================================================
> FAIL: test_count_csr (pyFAI.test.test_histogram.TestHistogram2d)
> Test that the pixel count and the total intensity is conserved
> ----------------------------------------------------------------------
> Traceback (most recent call last):
>   File "/usr/lib/python3/dist-packages/pyFAI/test/test_histogram.py",
> line 339, in test_count_csr
>     self.assertTrue(delta == 0, msg="check all pixels were counted")
> AssertionError: False is not true : check all pixels were counted
> 
> ======================================================================
> FAIL: test_numpy_vs_cython_vs_csr_2d 
> (pyFAI.test.test_histogram.TestHistogram2d)
> Compare numpy histogram with cython simple implementation
> ----------------------------------------------------------------------
> Traceback (most recent call last):
>   File "/usr/lib/python3/dist-packages/pyFAI/test/test_histogram.py",
> line 373, in test_numpy_vs_cython_vs_csr_2d
>     self.assertTrue(delta_max <= self.err_max_cnt, "pixel count
> difference numpy/csr : max delta=%s" % delta_max)
> AssertionError: False is not true : pixel count difference numpy/csr :
> max delta=8.0
> 
> ======================================================================
> FAIL: test_2d_nosplit (pyFAI.test.test_csr.TestCSR)
> ----------------------------------------------------------------------
> Traceback (most recent call last):
>   File "/usr/lib/python3/dist-packages/pyFAI/test/test_csr.py", line
> 195, in test_2d_nosplit
>     self.assertLess(error.mean(), 1e-3, "img are almost the same")
> AssertionError: 244.15215998872887 not less than 0.001 : img are almost the 
> same
> 
> ----------------------------------------------------------------------
> Ran 376 tests in 285.382s
> 
> FAILED (failures=3, skipped=10)
> 
> -- 
> Debian-pan-maintainers mailing list
> debian-pan-maintain...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-pan-maintainers


-- 
Jérôme Kieffer
tel +33 476 882 445

Reply via email to