Groups
Groups
Sign in
Groups
Groups
Beancount
Conversations
About
Send feedback
Help
Issue #410: Tests fail with Python 3.8 (blais/beancount)
20 views
Skip to first unread message
Dr. Tobias Quathamer
unread,
Nov 20, 2019, 5:36:34 AM
11/20/19
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to bean...@googlegroups.com
New issue 410: Tests fail with Python 3.8
https://bitbucket.org/blais/beancount/issues/410/tests-fail-with-python-38
Dr. Tobias Quathamer:
Hi,
I’m helping to maintain the Debian package of beancount, and the tests have recently begun to fail, after we switched from Python 3.7 to Python 3.8. You can see the full build log here:
[
https://buildd.debian.org/status/fetch.php?pkg=beancount&arch=amd64&ver=2.2.3-1%2Bb1&stamp=1574207855&raw=0](https://buildd.debian.org/status/fetch.php?pkg=beancount&arch=amd64&ver=2.2.3-1%2Bb1&stamp=1574207855&raw=0)
The first failing test is this:
`beancount/ingest/identify_test.py::TestScriptIdentify::test_identify FAILED [ 20%]`
Afterwards, the tests break with a segmentation fault error:
```
beancount/parser/lexer_test.py::TestLexerErrors::test_lexer_invalid_token PASSED [ 55%]
beancount/parser/lexer_test.py::TestLexerUnicode::test_bytes_encoded_latin1 PASSED [ 55%]
beancount/parser/lexer_test.py::TestLexerUnicode::test_bytes_encoded_latin1_invalid PASSED [ 55%]
beancount/parser/lexer_test.py::TestLexerUnicode::test_bytes_encoded_utf16 Segmentation fault
E: pybuild pybuild:341: test: plugin distutils failed with: exit code=139: cd /<<PKGBUILDDIR>>/.pybuild/cpython3_3.8/build; python3.8 -m pytest -v
dh_auto_test: pybuild --test --test-pytest -i python{version} -p "3.8 3.7" returned exit code 13
make: *** [debian/rules:13: binary-arch] Error 255
dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit status 2
```
The corresponding bug in Debian is [
https://bugs.debian.org/943608](https://bugs.debian.org/943608)
, however, there’s not much information in the bug log \(yet\). Could you please take a look at this?
Regards,
Tobias
Reply all
Reply to author
Forward
0 new messages