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!
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!
FS#76582 - [python-unrardll] No tests were really run
Attached to Project:
Community Packages
Opened by Felix Yan (felixonmars) - Tuesday, 15 November 2022, 14:39 GMT
Opened by Felix Yan (felixonmars) - Tuesday, 15 November 2022, 14:39 GMT
|
DetailsDescription:
After the "setup.py test" removal, the tests were not really run at all: ==> Starting check()... ---------------------------------------------------------------------- Ran 0 tests in 0.000s OK In comparison, before the change: ==> Starting check()... running test running build_py running build_ext test_comment (test.basic.BasicTests) ... ok test_extract (test.basic.BasicTests) ... ok test_extract_member (test.basic.BasicTests) ... ok test_invalid_callback (test.basic.BasicTests) ... ok test_memory_leaks (test.basic.BasicTests) ... skipped 'psutil is not available' test_multipart (test.basic.BasicTests) ... ok test_names (test.basic.BasicTests) ... ok test_open_failure (test.basic.BasicTests) ... ok test_password (test.basic.BasicTests) ... ok test_share_open (test.basic.BasicTests) ... ok ---------------------------------------------------------------------- Ran 10 tests in 0.207s OK (skipped=1) |
This task depends upon