Processing control commands:
> severity -1 serious
Bug #976952 [src:lmfit-py] 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
Severity set to 'serious' from 'normal'
--
976952:
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,
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.
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.
> 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
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
> 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
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)'
>
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
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
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
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
12 matches
Mail list logo
