Bug#1050432: rpy2: FTBFS on mips64el
On 27 August 2023 at 18:44, YunQiang Su wrote: | Maybe there is something wrong with ffi. (In fact the complex support of mips | was added by me. ;) Hah. | I am looking for a way to use debug to debug the extensions. | If you have any documents, can you point it to me. I can help you with R, I think here the issue is more on the Python side. But to the best of my knowledge, the applications languages generally just call into the C library 'and assume things work'. But maybe here we need another compile-time / link-time option to turn ffi on? Dirk -- dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
Bug#1050432: rpy2: FTBFS on mips64el
Dirk Eddelbuettel 于2023年8月27日周日 16:52写道： > > > On 27 August 2023 at 14:09, YunQiang Su wrote: > | Dirk Eddelbuettel 于2023年8月27日周日 00:15写道： > | > > | > > | > Hi all, > | > > | > As the test failures for complex valued variables appeared to be systemic > on > | > the 'mips64el' platform, I buckled down, taught myself some Python ==:-) > and > | > conditioned the number of failing tests away via > | > > | > @pytest.mark.skipif(platform.machine() == 'mips64' and sys.byteorder == > 'little', > | > reason="Complex tests fails for 'mips64el'.") > | > > | > Maybe the porters team can shed some light on why we needed it, and if > this > | > worked (the autobuilders will tell us soon enough) I can pass the patch > on to > | > Laurent for a possible inclusion upstream. > | > > | > | Sorry for the late reply. I can work on it. > > Appreciate that! > > (While my fix corrected the build, it is a stop-gap as it avoids the issue. A > real fix would be good.) > > | Do you knwo any way to run a single testcase? > > Can you start from the unit tests I conditioned out? Each of those has > simple expression with a complex in it. Those should be executable directly > in the Python interpreter. You probably need all the build-deps (python, R, > rpy2, numpy, ...) installed. > Maybe there is something wrong with ffi. (In fact the complex support of mips was added by me. ;) I am looking for a way to use debug to debug the extensions. If you have any documents, can you point it to me. > Dirk > > -- > dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org -- YunQiang Su
Bug#1050432: rpy2: FTBFS on mips64el
On 27 August 2023 at 14:09, YunQiang Su wrote: | Dirk Eddelbuettel 于2023年8月27日周日 00:15写道： | > | > | > Hi all, | > | > As the test failures for complex valued variables appeared to be systemic on | > the 'mips64el' platform, I buckled down, taught myself some Python ==:-) and | > conditioned the number of failing tests away via | > | > @pytest.mark.skipif(platform.machine() == 'mips64' and sys.byteorder == 'little', | > reason="Complex tests fails for 'mips64el'.") | > | > Maybe the porters team can shed some light on why we needed it, and if this | > worked (the autobuilders will tell us soon enough) I can pass the patch on to | > Laurent for a possible inclusion upstream. | > | | Sorry for the late reply. I can work on it. Appreciate that! (While my fix corrected the build, it is a stop-gap as it avoids the issue. A real fix would be good.) | Do you knwo any way to run a single testcase? Can you start from the unit tests I conditioned out? Each of those has simple expression with a complex in it. Those should be executable directly in the Python interpreter. You probably need all the build-deps (python, R, rpy2, numpy, ...) installed. Dirk -- dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
Bug#1050432: rpy2: FTBFS on mips64el
Dirk Eddelbuettel 于2023年8月27日周日 00:15写道： > > > Hi all, > > As the test failures for complex valued variables appeared to be systemic on > the 'mips64el' platform, I buckled down, taught myself some Python ==:-) and > conditioned the number of failing tests away via > > @pytest.mark.skipif(platform.machine() == 'mips64' and sys.byteorder == > 'little', > reason="Complex tests fails for 'mips64el'.") > > Maybe the porters team can shed some light on why we needed it, and if this > worked (the autobuilders will tell us soon enough) I can pass the patch on to > Laurent for a possible inclusion upstream. > Sorry for the late reply. I can work on it. Do you knwo any way to run a single testcase? > Cheers, Dirk > > -- > dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org > -- YunQiang Su
Bug#1050432: rpy2: FTBFS on mips64el
Hi all, As the test failures for complex valued variables appeared to be systemic on the 'mips64el' platform, I buckled down, taught myself some Python ==:-) and conditioned the number of failing tests away via @pytest.mark.skipif(platform.machine() == 'mips64' and sys.byteorder == 'little', reason="Complex tests fails for 'mips64el'.") Maybe the porters team can shed some light on why we needed it, and if this worked (the autobuilders will tell us soon enough) I can pass the patch on to Laurent for a possible inclusion upstream. Cheers, Dirk -- dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
Bug#1050432: rpy2: FTBFS on mips64el
Hi Dirk, mips-porters, On 24-08-2023 17:25, Dirk Eddelbuettel wrote: Paul: While I have you here, and as all those failures are on _complex_, is there a known issue with mips64el or a specific compiler switch that may be needed? rpy2 is fairly widely used but also 'glue' around other Python libraries, are any others affected? I don't know. I guess we should ask the mips* porters (done so by putting them in TO). Paul OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1050432: rpy2: FTBFS on mips64el
Paul, Thanks for the hint. I was aware and had been meaning to bring this up with Laurent (upstream, now CCed). Laurent: I should have access to a 'porterbox' running mips64el if you have an idea about what may be going on here / have a branch to test. Paul: While I have you here, and as all those failures are on _complex_, is there a known issue with mips64el or a specific compiler switch that may be needed? rpy2 is fairly widely used but also 'glue' around other Python libraries, are any others affected? Dirk On 24 August 2023 at 16:59, Paul Gevers wrote: | Source: rpy2 | Version: 3.5.13-1 | Severity: serious | Tags: ftbfs | Justification: FTBFS | | Dear maintainer, | | Since the upload version 3.5.13-1, rpy2 has been failing to build on | mips64el, which is blocking migration to testing. | | https://buildd.debian.org/status/logs.php?pkg=rpy2=mips64el | | === short test summary info | FAILED rpy2/tests/rinterface/test_na.py::test_R_to_NAComplex - assert False | FAILED rpy2/tests/rinterface/test_vector_complex.py::test_init_from_seqr - as... | FAILED rpy2/tests/rinterface/test_vector_complex.py::test_getitem - assert (-... | FAILED rpy2/tests/rinterface/test_vector_complex.py::test_setitem - assert (-... | FAILED rpy2/tests/rinterface/test_vector_complex.py::test_getslice - assert (... | FAILED rpy2/tests/rinterface/test_vector_complex.py::test_getslice_negative | FAILED rpy2/tests/rinterface/test_vector_complex.py::test_setslice - assert (... | FAILED rpy2/tests/rinterface/test_vector_complex.py::test_setslice_negative | FAILED rpy2/tests/rinterface/test_vector_complex.py::test_index - ValueError:... | FAILED rpy2/tests/robjects/test_conversion_numpy.py::TestNumpyConversions::test_vector_complex | | Paul | | -- System Information: Debian Release: trixie/sid APT prefers testing | APT policy: (990, 'testing') Architecture: amd64 (x86_64) | | Kernel: Linux 6.4.0-2-amd64 (SMP w/8 CPU threads; PREEMPT) | Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en | Shell: /bin/sh linked to /usr/bin/dash | Init: systemd (via /run/systemd/system) | LSM: AppArmor: enabled -- dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
Bug#1050432: rpy2: FTBFS on mips64el
Source: rpy2 Version: 3.5.13-1 Severity: serious Tags: ftbfs Justification: FTBFS Dear maintainer, Since the upload version 3.5.13-1, rpy2 has been failing to build on mips64el, which is blocking migration to testing. https://buildd.debian.org/status/logs.php?pkg=rpy2=mips64el === short test summary info FAILED rpy2/tests/rinterface/test_na.py::test_R_to_NAComplex - assert False FAILED rpy2/tests/rinterface/test_vector_complex.py::test_init_from_seqr - as... FAILED rpy2/tests/rinterface/test_vector_complex.py::test_getitem - assert (-... FAILED rpy2/tests/rinterface/test_vector_complex.py::test_setitem - assert (-... FAILED rpy2/tests/rinterface/test_vector_complex.py::test_getslice - assert (... FAILED rpy2/tests/rinterface/test_vector_complex.py::test_getslice_negative FAILED rpy2/tests/rinterface/test_vector_complex.py::test_setslice - assert (... FAILED rpy2/tests/rinterface/test_vector_complex.py::test_setslice_negative FAILED rpy2/tests/rinterface/test_vector_complex.py::test_index - ValueError:... FAILED rpy2/tests/robjects/test_conversion_numpy.py::TestNumpyConversions::test_vector_complex Paul -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.4.0-2-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
