Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.maint.python > #13938 > unrolled thread

Bug#1002325: [Help] Re: python-envisage: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" returned exit code 13

Started byAndreas Tille <andreas@an3as.eu>
First post2022-02-10 09:00 +0100
Last post2022-02-14 15:00 +0100
Articles 3 — 2 participants

Back to article view | Back to linux.debian.maint.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Bug#1002325: [Help] Re: python-envisage: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" returned exit code 13 Andreas Tille <andreas@an3as.eu> - 2022-02-10 09:00 +0100
    Bug#1002325: [Help] Re: python-envisage: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" returned exit code 13 Andreas Tille <andreas@an3as.eu> - 2022-02-14 14:10 +0100
      Bug#1002325: [Help] Re: python-envisage: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" returned exit code 13 Stefano Rivera <stefanor@debian.org> - 2022-02-14 15:00 +0100

#13938 — Bug#1002325: [Help] Re: python-envisage: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" returned exit code 13

FromAndreas Tille <andreas@an3as.eu>
Date2022-02-10 09:00 +0100
SubjectBug#1002325: [Help] Re: python-envisage: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" returned exit code 13
Message-ID<DPcwV-Oos-5@gated-at.bofh.it>
Control: tags -1 help

Hi,

I've updated python-envisage in Salsa[1] to the latest upstream version
and bumped its failing predepends to their according latest upstream and
fixed all bugs in those.  For envisage I'm stumbling upon a Python3.10
related bug I'd like to ask for help:

...
======================================================================
ERROR: test_exclude_multiple (envisage.tests.test_egg_plugin_manager.EggPluginManagerTestCase)
exclude multiple
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/build/python-envisage-6.0.1/.pybuild/cpython3_3.10_envisage/build/envisage/tests/test_egg_plugin_manager.py", line 115, in test_exclude_multiple
    self._add_eggs_on_path([self.egg_dir])
  File "/build/python-envisage-6.0.1/.pybuild/cpython3_3.10_envisage/build/envisage/tests/test_egg_based.py", line 59, in _add_eggs_on_path
    raise SystemError("Cannot find eggs %s" % errors)
SystemError: Cannot find eggs {}

======================================================================
ERROR: test_exclude_specific (envisage.tests.test_egg_plugin_manager.EggPluginManagerTestCase)
exclude specific
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/build/python-envisage-6.0.1/.pybuild/cpython3_3.10_envisage/build/envisage/tests/test_egg_plugin_manager.py", line 91, in test_exclude_specific
    self._add_eggs_on_path([self.egg_dir])
  File "/build/python-envisage-6.0.1/.pybuild/cpython3_3.10_envisage/build/envisage/tests/test_egg_based.py", line 59, in _add_eggs_on_path
    raise SystemError("Cannot find eggs %s" % errors)
SystemError: Cannot find eggs {}


Any idea to deal with this issue in
   envisage/tests/test_egg_based.py", line 59
?

Kind regards

      Andreas.


[1] https://salsa.debian.org/python-team/packages/python-envisage


-- 
http://fam-tille.de

[toc] | [next] | [standalone]


#13948

FromAndreas Tille <andreas@an3as.eu>
Date2022-02-14 14:10 +0100
Message-ID<DQJh7-1L2Q-7@gated-at.bofh.it>
In reply to#13938
Hi Scott,

thanks a lot for your hints.

Am Sun, Feb 13, 2022 at 10:28:15PM -0500 schrieb Scott Talbert:
> I spent some time looking into this.  The problem is that upstream includes
> binary eggs (which are Python version specific) as part of its test suite.
> The problem here is that there are no eggs included for Python 3.10.
> Upstream is aware of this[1] but unfortunately, that patch can't be applied
> because it is a binary patch.  They have also later[2] removed the binary
> eggs completely, but that patch can't be applied either because it involves
> files that are not in the PyPI distribution.  The best solution might be do
> what Fedora did[3], but for that we'd probably have to switch to using a
> GitHub tarball instead of the PyPI tarball because the PyPI tarball is
> missing files.

I switched to Github downloads and followed the Fedora approach.
I'd be happy if you could review my changes[1].

Kind regards

     Andreas.


[1] https://salsa.debian.org/python-team/packages/python-envisage/-/commit/1498f59734676a667d7ba64a2cc622a5c4f07f7b

-- 
http://fam-tille.de

[toc] | [prev] | [next] | [standalone]


#13949

FromStefano Rivera <stefanor@debian.org>
Date2022-02-14 15:00 +0100
Message-ID<DQJTQ-1LfD-3@gated-at.bofh.it>
In reply to#13948
Hi Andreas (2022.02.14_13:00:13_+0000)
> I switched to Github downloads and followed the Fedora approach.
> I'd be happy if you could review my changes[1].

That looks like it's all doing the right thing, I only have minor
nit-picks from review:

I'd suggest starting the multi-line shell thing with a "set -e;" for
sanity.

You could use a subshell in the inner-loop, to avoid having to change
directory back to CURDIR again, but

You could generate all the eggs and then run pybuild --test once,
letting it loop over python versions, itself.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.maint.python


csiph-web