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
Last edited by Toolybird (Toolybird) - Sunday, 21 May 2023, 04:17 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Jelle van der Waa (jelly)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
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

Closed by  Toolybird (Toolybird)
Sunday, 21 May 2023, 04:17 GMT
Reason for closing:  Fixed
Additional comments about closing:  python-unrardll 0.1.5-3

Loading...