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

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

Bug#959631: hy: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 returned exit code 13

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#959631: hy: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 returned exit code 13 Tianon Gravi <tianon@debian.org> - 2020-05-05 20:30 +0200
    Bug#959631: hy: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 returned exit code 13 Tianon Gravi <tianon@debian.org> - 2020-05-15 20:30 +0200
      Bug#959631: hy: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 returned exit code 13 Lucas Nussbaum <lucas@debian.org> - 2020-06-21 22:10 +0200

#12557 — Bug#959631: hy: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 returned exit code 13

On Sun, 3 May 2020 at 06:12, Lucas Nussbaum <lucas@debian.org> wrote:
> > ...
> > =============================== warnings summary ===============================
> > .pybuild/cpython3_3.8_hy/build/tests/native_tests/comprehensions.hy::test_fors[sfor]
> >   /<<PKGBUILDDIR>>/hy/models.py:133: RuntimeWarning: coroutine '<module>' was never awaited
> >     return super(HySymbol, cls).__new__(cls, s)
> >
> > .pybuild/cpython3_3.8_hy/build/tests/native_tests/comprehensions.hy::test_fors[gfor]
> >   /usr/lib/python3/dist-packages/funcparserlib/parser.py:232: RuntimeWarning: coroutine '<module>' was never awaited
> >     self.pos = pos
> >
> > .pybuild/cpython3_3.8_hy/build/tests/native_tests/comprehensions.hy::test_empty_for
> >   /usr/lib/python3/dist-packages/_pytest/nodes.py:192: RuntimeWarning: coroutine '<module>' was never awaited
> >     return (x[1] for x in self.iter_markers_with_node(name=name))
> >
> > .pybuild/cpython3_3.8_hy/build/tests/native_tests/core.hy::test_parse_args
> >   /usr/lib/python3/dist-packages/funcparserlib/parser.py:322: RuntimeWarning: coroutine '<module>' was never awaited
> >     raise NoParseError('got unexpected token', s)
> >
> > -- Docs: https://docs.pytest.org/en/latest/warnings.html
> > ======= 5 failed, 547 passed, 54 deselected, 4 warnings in 8.47 seconds ========
> > E: pybuild pybuild:352: test: plugin distutils failed with: exit code=1: cd /<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_hy/build; python3.8 -m pytest -k '-test_bin -test_hy2py'
> > dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 returned exit code 13
>
> ...

Oh, fun times.

I was definitely over my head with this one, so I reached out to the
Hy community and was pointed to https://bugs.python.org/issue39562,
which does seem quite related from my own limited understanding, so
this might technically be a bug in the Python package?

I'm including the Debian Python list on CC to hopefully see if someone
there can provide some assistance figuring out what's necessary here.
O:)

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4

[toc] | [next] | [standalone]

#12588

On Tue, 5 May 2020 at 10:55, Tianon Gravi <tianon@debian.org> wrote:
> I was definitely over my head with this one, so I reached out to the
> Hy community and was pointed to https://bugs.python.org/issue39562,
> which does seem quite related from my own limited understanding, so
> this might technically be a bug in the Python package?
>
> I'm including the Debian Python list on CC to hopefully see if someone
> there can provide some assistance figuring out what's necessary here.
> O:)

Looking at results from ci.debian.net[1], our autopkgtests failed on
2020-05-07 and passed today (2020-05-15).  Comparing the logs, it
appears the difference is that the last failing build was against
python3.8 version 3.8.3~rc1-1, and the successful build from today was
against python3.8 version 3.8.3-1 (lending credence to the thought it
was probably a Python bug, and that it's now fixed).

[1]: https://ci.debian.net/packages/h/hy/

Can you re-test and verify that we no longer FTBFS in your testing? O:)

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4

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

#12668

On 15/05/20 at 11:18 -0700, Tianon Gravi wrote:
> On Tue, 5 May 2020 at 10:55, Tianon Gravi <tianon@debian.org> wrote:
> > I was definitely over my head with this one, so I reached out to the
> > Hy community and was pointed to https://bugs.python.org/issue39562,
> > which does seem quite related from my own limited understanding, so
> > this might technically be a bug in the Python package?
> >
> > I'm including the Debian Python list on CC to hopefully see if someone
> > there can provide some assistance figuring out what's necessary here.
> > O:)
> 
> Looking at results from ci.debian.net[1], our autopkgtests failed on
> 2020-05-07 and passed today (2020-05-15).  Comparing the logs, it
> appears the difference is that the last failing build was against
> python3.8 version 3.8.3~rc1-1, and the successful build from today was
> against python3.8 version 3.8.3-1 (lending credence to the thought it
> was probably a Python bug, and that it's now fixed).
> 
> [1]: https://ci.debian.net/packages/h/hy/
> 
> Can you re-test and verify that we no longer FTBFS in your testing? O:)

Hi,

Sorry for the delay. I confirm it builds fine now.

Lucas

[toc] | [prev] | [standalone]

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

csiph-web