Source: python-pynvim Version: 0.4.1-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201119 ftbfs-bullseye
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > collecting ... collected 68 items > > test/test_buffer.py::test_repr PASSED [ > 1%] > test/test_buffer.py::test_get_length PASSED [ > 2%] > test/test_buffer.py::test_get_set_del_line PASSED [ > 4%] > test/test_buffer.py::test_get_set_del_slice PASSED [ > 5%] > test/test_buffer.py::test_vars PASSED [ > 7%] > test/test_buffer.py::test_api PASSED [ > 8%] > test/test_buffer.py::test_options PASSED [ > 10%] > test/test_buffer.py::test_number PASSED [ > 11%] > test/test_buffer.py::test_name PASSED [ > 13%] > test/test_buffer.py::test_valid PASSED [ > 14%] > test/test_buffer.py::test_append PASSED [ > 16%] > test/test_buffer.py::test_mark PASSED [ > 17%] > test/test_buffer.py::test_invalid_utf8 > E: Build killed with signal TERM after 150 minutes of inactivity The full build log is available from: http://qa-logs.debian.net/2020/11/19/python-pynvim_0.4.1-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures.
