All right, now I've got it. The "%*" on the command line is a mistake. When there are no command line parameters, then unittest tries to find tests in the directory tree. So just plain
python3 -m unittest On Wednesday, February 16, 2022 at 4:56:24 PM UTC-5 [email protected] wrote: > Sorry, sent too soon by mistake. > > Leo 6.6b2-devel, devel branch, build 513f9493ec > 2022-02-16 14:35:19 -0600 > Python 3.9.9, PyQt version 6.2.3 > Windows 10 AMD64 (build 10.0.19043) > home: C:\Users\tom > leo-editor: C:\Tom\git\leo-editor > > On Wednesday, February 16, 2022 at 4:54:13 PM UTC-5 [email protected] > wrote: > >> c:\Tom\git\leo-editor>py -m unittest %* >> E >> ====================================================================== >> ERROR: %* (unittest.loader._FailedTest) >> ---------------------------------------------------------------------- >> ImportError: Failed to import test module: %* >> Traceback (most recent call last): >> File "C:\Program Files\Python39\lib\unittest\loader.py", line 154, in >> loadTestsFromName >> module = __import__(module_name) >> ModuleNotFoundError: No module named '%*' >> >> >> ---------------------------------------------------------------------- >> Ran 1 test in 0.000s >> >> FAILED (errors=1) >> >> On Wednesday, February 16, 2022 at 3:05:13 PM UTC-5 Edward K. Ream wrote: >> >>> On Wednesday, February 16, 2022 at 11:34:47 AM UTC-6 Edward K. Ream >>> wrote: >>> >>> I have already revoked the permissions for TravisCI. The next steps: >>>> >>>> - Remove the TravisCI files from both master and devel (using PR's), >>>> thereby disabling unit tests on all commits. >>>> - Disable (convert @clean to @@clean) the corresponding nodes in >>>> leoDist.leo. >>>> >>> >>> Done directly in master at rev 58f2dd9 >>> <https://github.com/leo-editor/leo-editor/commit/58f2dd96766185470917b00153bd16ad2c6856aa>. >>> >>> Done in devel via PR #2429 >>> <https://github.com/leo-editor/leo-editor/pull/2429>. leoDist.leo >>> contains @@@clean nodes for the deleted files, so it should be >>> straightforward to restore the status quo ante should that seem desirable. >>> >>> So now Thomas and I are responsible for running tests manually. To run >>> pylint on all files, execute the following: >>> >>> cd C:\leo.repo\leo-editor >>> python -m pylint-leo %* >>> >>> To run Leo's test-all command, execute the following in the leo-editor >>> directory: >>> >>> cd C:\leo.repo\leo-editor >>> python -m unittest %* >>> >>> That's easy enough! The scripts shown above are for Windows .cmd files. >>> Linux scripts would be similar. >>> >>> Edward >>> >> -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/0f5b3f0c-5c70-42b2-ac4e-c431af4de36cn%40googlegroups.com.
