Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#44363 - [python] tests fail during makepkg

Attached to Project: Arch Linux
Opened by Neven Sajko (Neven) - Thursday, 26 March 2015, 23:20 GMT
Last edited by freswa (frederik) - Tuesday, 11 February 2020, 18:53 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Felix Yan (felixonmars)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

The tk and logging tests failed in makepkg's check().
This task depends upon

Closed by  freswa (frederik)
Tuesday, 11 February 2020, 18:53 GMT
Reason for closing:  Upstream
Additional comments about closing:  Seems it has been fixed upstream since 2015
Comment by Felix Yan (felixonmars) - Friday, 27 March 2015, 00:48 GMT
Works for me. Did you test in a clean chroot?
Comment by Neven Sajko (Neven) - Friday, 27 March 2015, 02:12 GMT
The logging test worked afterwards when there wasn't so much stuff up at once, and the tk test is skipped if ran outside an X server - so it builds fine from the console.
It still aborts a few times - I have core dumps.
Comment by Felix Yan (felixonmars) - Friday, 27 March 2015, 02:31 GMT
Yeah I got those coredumps as well, and sometimes the tests stuck, but generally they could pass. Please let me know if any improvements could be applied :)
Comment by Neven Sajko (Neven) - Friday, 27 March 2015, 02:34 GMT
Did you report backtraces of the coredumps? I couldn't register to bugs.python.org.
Comment by Felix Yan (felixonmars) - Friday, 27 March 2015, 02:35 GMT
Not yet as the test passes, which I take as they are meant to segfault.
Comment by Neven Sajko (Neven) - Friday, 27 March 2015, 02:40 GMT
From README:

Testing
-------

To test the interpreter, type "make test" in the top-level directory. The test
set produces some output. You can generally ignore the messages about skipped
tests due to optional features which can't be imported. *If a message is printed
about a failed test or a traceback or core dump is produced, something is wrong.*

The last part seems to indicate the aborts should be reported.
   py-bt-0.txt (0.8 KiB)
   py-bt-3.txt (0.8 KiB)
   py-bt-6.txt (3.2 KiB)
   py-bt-7.txt (446.2 KiB)
   py-bt-8.txt (44.2 KiB)

Loading...