Bug#971214: elpy: FTBFS: tests failed

[Salman Mohammadi]

Hi,

What I can see is that

(error "Elpy error: black not installed")

Is *black* already installed?


Cheers,

Salman

Source: elpy
Version: 1.34.0-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200926 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.

make[1]: Entering directory '/<<PKGBUILDDIR>>'
dh_auto_build
I: pybuild base:217: /usr/bin/python3 setup.py build
running build
running build_py
creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_elpy/build/elpy
copying elpy/jedibackend.py ->

/<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_elpy/build/elpy

copying elpy/refactor.py ->

/<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_elpy/build/elpy

copying elpy/__init__.py ->

/<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_elpy/build/elpy

copying elpy/__main__.py ->

/<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_elpy/build/elpy

copying elpy/pydocutils.py ->

/<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_elpy/build/elpy

copying elpy/blackutil.py ->

/<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_elpy/build/elpy

copying elpy/yapfutil.py ->

/<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_elpy/build/elpy

copying elpy/compat.py ->

/<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_elpy/build/elpy

copying elpy/auto_pep8.py ->

/<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_elpy/build/elpy

copying elpy/rpc.py ->

/<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_elpy/build/elpy

copying elpy/server.py ->

/<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_elpy/build/elpy

creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_elpy/build/elpy/tests
copying elpy/tests/test_server.py ->

/<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_elpy/build/elpy/tests

copying elpy/tests/test_rpc.py ->

/<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_elpy/build/elpy/tests

copying elpy/tests/support.py ->

/<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_elpy/build/elpy/tests

copying elpy/tests/test_yapf.py ->

/<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_elpy/build/elpy/tests

copying elpy/tests/__init__.py ->

/<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_elpy/build/elpy/tests

copying elpy/tests/test_pydocutils.py ->

/<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_elpy/build/elpy/tests

copying elpy/tests/test_auto_pep8.py ->

/<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_elpy/build/elpy/tests

copying elpy/tests/test_refactor.py ->

/<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_elpy/build/elpy/tests

copying elpy/tests/test_jedibackend.py ->

/<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_elpy/build/elpy/tests

copying elpy/tests/compat.py ->

/<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_elpy/build/elpy/tests

copying elpy/tests/test_black.py ->

/<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_elpy/build/elpy/tests

copying elpy/tests/test_support.py ->

/<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_elpy/build/elpy/tests

running egg_info
creating elpy.egg-info
writing elpy.egg-info/PKG-INFO
writing dependency_links to elpy.egg-info/dependency_links.txt
writing requirements to elpy.egg-info/requires.txt
writing top-level names to elpy.egg-info/top_level.txt
writing manifest file 'elpy.egg-info/SOURCES.txt'
reading manifest file 'elpy.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
writing manifest file 'elpy.egg-info/SOURCES.txt'
PYTHONPATH=. python3 -m sphinx -N -bman docs/ build/man
Running Sphinx v3.2.1
making output directory... done
building [mo]: targets for 0 po files that are out of date
building [man]: all manpages
updating environment: [new config] 9 added, 0 changed, 0 removed
reading sources... [ 11%] FAQ

[Debian Bug Tracking System]

tag -1 unreproducible

Bug #971214 [src:elpy] elpy: FTBFS: tests failed
Added tag(s) unreproducible.

[Debian Bug Tracking System]

Your message dated Fri, 23 Oct 2020 14:48:27 -0400
with message-id <***@DigitalMercury.dynalias.net>
and subject line Re: Bug#971214: elpy: FTBFS: tests failed
has caused the Debian Bug report #971214,
regarding elpy: FTBFS: tests failed
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ***@bugs.debian.org
immediately.)