Bug#976952: [Help] Re: lmfit-py: FTBFS on ppc64el (arch:all-only src pkg): dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13
Control: severity -1 serious This same issue prevents lmfit-py/1.0.1-5 from migrating to testing. Issues preventing migration: blocked by freeze: autopkgtest not fully successful I'll make a team upload shortly, disabling test_model_nan_policy and test_manypeaks_speed during the build and autopkgtests.
Bug#976952: [Help] Re: lmfit-py: FTBFS on ppc64el (arch:all-only src pkg): dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13
On 12/18/20 4:49 PM, Andreas Tille wrote: >> Well, the test is obviously broken and upstream currently can't be bothered >> to fix >> it on non-x86 targets. He will certainly have to do it at some point given >> that ARM64 >> is replacing more and more x86_64 systems, but I wouldn't bother, personally. > > But its on ppc64el not arm64. This is no argument to ignore the issue, > but the practical relevance of ppc64el is smaller than amd64 and arm64 > theses days if I'm not misleaded. I was referring to the comment in the openSUSE spec file which claims the tests are broken on all non-x86_64 targets. I have not verified whether this is correct, though. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#976952: [Help] Re: lmfit-py: FTBFS on ppc64el (arch:all-only src pkg): dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13
Ok, in that case, I think that a comment in the d/rules files is enough in order to keep in mind that we have this issue with ppc64el.
Bug#976952: [Help] Re: lmfit-py: FTBFS on ppc64el (arch:all-only src pkg): dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13
On Fri, Dec 18, 2020 at 04:44:04PM +0100, John Paul Adrian Glaubitz wrote: > > > > so it does not fit with our policy: do not hide problems ;) Well, we do not need to *hide* the problem. We can exclude the test and *document* the problem - say in a README.Debian on the affected architecture. > > The problem is that I do not have enougt time to investigate... on a porter > > box > > Well, the test is obviously broken and upstream currently can't be bothered > to fix > it on non-x86 targets. He will certainly have to do it at some point given > that ARM64 > is replacing more and more x86_64 systems, but I wouldn't bother, personally. But its on ppc64el not arm64. This is no argument to ignore the issue, but the practical relevance of ppc64el is smaller than amd64 and arm64 theses days if I'm not misleaded. Kind regards Andreas. -- http://fam-tille.de
Bug#976952: [Help] Re: lmfit-py: FTBFS on ppc64el (arch:all-only src pkg): dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13
> Well, the test is obviously broken and upstream currently can't be bothered > to fix > it on non-x86 targets. He will certainly have to do it at some point given > that ARM64 > is replacing more and more x86_64 systems, but I wouldn't bother, personally. so what is the best solution in order to have lmfit-py in bulleyes ?
Bug#976952: [Help] Re: lmfit-py: FTBFS on ppc64el (arch:all-only src pkg): dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13
> Yes, good catch. The spec file for the openSUSE package has this [1]: so it does not fit with our policy: do not hide problems ;) The problem is that I do not have enougt time to investigate... on a porter box
Bug#976952: [Help] Re: lmfit-py: FTBFS on ppc64el (arch:all-only src pkg): dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13
On 12/18/20 4:42 PM, PICCA Frederic-Emmanuel wrote: >> Yes, good catch. The spec file for the openSUSE package has this [1]: > > so it does not fit with our policy: do not hide problems ;) > > The problem is that I do not have enougt time to investigate... on a porter > box Well, the test is obviously broken and upstream currently can't be bothered to fix it on non-x86 targets. He will certainly have to do it at some point given that ARM64 is replacing more and more x86_64 systems, but I wouldn't bother, personally. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#976952: [Help] Re: lmfit-py: FTBFS on ppc64el (arch:all-only src pkg): dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13
Hi Frederic! On 12/18/20 4:00 PM, PICCA Frederic-Emmanuel wrote: > looking at the Opensuze log, I can find this > > [ 93s] + pytest-3.8 --ignore=_build.python2 --ignore=_build.python3 > --ignore=_build.pypy3 -v -k 'not speed and not (test_model_nan_policy or > test_shgo_scipy_vs_lmfit_2)' > [ 97s] = test session starts > == > > does it means that the failling test on Debian is skipped during the build on > OBS ? Yes, good catch. The spec file for the openSUSE package has this [1]: # We don't care about speed, and test_itercb is architecture-specific # test_model_nan_policy - fails on non x86_64 # test_shgo_scipy_vs_lmfit_2 - fails on non x86_64 %pytest -k 'not speed and not (test_model_nan_policy or test_shgo_scipy_vs_lmfit_2)' Adrian > [1] > https://build.opensuse.org/package/view_file/devel:languages:python:numeric/python-lmfit/python-lmfit.spec?expand=1 -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#976952: [Help] Re: lmfit-py: FTBFS on ppc64el (arch:all-only src pkg): dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13
Hello looking at the Opensuze log, I can find this [ 93s] + pytest-3.8 --ignore=_build.python2 --ignore=_build.python3 --ignore=_build.pypy3 -v -k 'not speed and not (test_model_nan_policy or test_shgo_scipy_vs_lmfit_2)' [ 97s] = test session starts == does it means that the failling test on Debian is skipped during the build on OBS ? === FAILURES === _ TestUserDefiniedModel.test_model_nan_policy __ cheers Frederic
Bug#976952: [Help] Re: lmfit-py: FTBFS on ppc64el (arch:all-only src pkg): dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13
On Fri, Dec 18, 2020 at 03:41:58PM +0100, John Paul Adrian Glaubitz wrote: > On 12/18/20 3:19 PM, Andreas Tille wrote: > > I wonder whether we could get some help from PowerPC team to solve this > > issue. If we can not get that test working I see only two options: > > > >1. Skip this specific test > >2. Exclude ppc64el from architecture list > > > > Any help would be really welcome. > > The testsuite passes on ppc64el on openSUSE: > > > https://build.opensuse.org/package/show/devel:languages:python:numeric/python-lmfit > > https://build.opensuse.org/build/devel:languages:python:numeric/openSUSE_Factory_PowerPC/ppc64le/python-lmfit/_log > > So this might be related to the build environment? Thanks a lot for that hint - but I have no idea how to check this. Kind regards Andreas. -- http://fam-tille.de
Bug#976952: [Help] Re: lmfit-py: FTBFS on ppc64el (arch:all-only src pkg): dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13
On 12/18/20 3:19 PM, Andreas Tille wrote: > I wonder whether we could get some help from PowerPC team to solve this > issue. If we can not get that test working I see only two options: > >1. Skip this specific test >2. Exclude ppc64el from architecture list > > Any help would be really welcome. The testsuite passes on ppc64el on openSUSE: > https://build.opensuse.org/package/show/devel:languages:python:numeric/python-lmfit > https://build.opensuse.org/build/devel:languages:python:numeric/openSUSE_Factory_PowerPC/ppc64le/python-lmfit/_log So this might be related to the build environment? Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#976952: [Help] Re: lmfit-py: FTBFS on ppc64el (arch:all-only src pkg): dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13
Control: tags -1 -upstream Control: tags -1 help Hi, I wonder whether we could get some help from PowerPC team to solve this issue. If we can not get that test working I see only two options: 1. Skip this specific test 2. Exclude ppc64el from architecture list Any help would be really welcome. Kind regards Andreas. - Forwarded message from Matt Newville - Date: Fri, 18 Dec 2020 05:35:01 -0800 From: Matt Newville To: lmfit/lmfit-py Cc: Andreas Tille , Author Subject: Re: [lmfit/lmfit-py] Test failure on ppc64el (#692) This is a duplicate of #686. Personally, I could not care less about supporting PPC and have no intention of doing any work toward that. It's okay with me if someone else works on that, and It's okay with me if no one does. I guess I'm willing to leave this open to avoid another duplicate issue. -- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: https://github.com/lmfit/lmfit-py/issues/692#issuecomment-748087195 - End forwarded message - -- http://fam-tille.de
