For new elecraft driver… I can read and display radio memories. Can’t set ‘em yet. BUT:
I’ve started tox running successfully, and it starts up workers and generating an html report. It describes >1000 warnings, and then gives an exit 5. The html contains preface but no results.
I’ve NO idea what is causing it to die. Is there a timeout (it takes 10s of seconds to read the memories)?
Error is ... 8 workers [0 items] scheduling tests via LoadScheduling
--- Generated html report: file:///Users/declan/darchirp/driver_report.html ---- =========================== 1139 warnings in 16.93s ============================ driver: exit 5 (17.43 seconds) /Users/declan/darchirp> pytest --disable-warnings --html=driver_report.html -v tests/test_drivers.py -n auto -k Yaesu_Elecraft_KX3 pid=77757 .pkg: _exit> python /usr/local/lib/python3.11/site-packages/pyproject_api/_backend.py True setuptools.build_meta __legacy__ driver: FAIL code 5 (28.39=setup[10.96]+cmd[17.43] seconds) evaluation failed :( (28.55 seconds)
pytest exit code 5 is "No tests were collected".
https://docs.pytest.org/en/7.1.x/reference/exit-codes.html
Did you add a test file? If so, are the tests in a form that pytest will discover them?
Martin. KD6YAM
On Wed, Nov 13, 2024 at 11:17 AM Declan Rieb via Developers < developers@lists.chirpmyradio.com> wrote:
For new elecraft driver… I can read and display radio memories. Can’t set ‘em yet. BUT:
I’ve started tox running successfully, and it starts up workers and generating an html report. It describes >1000 warnings, and then gives an exit 5. The html contains preface but no results.
I’ve NO idea what is causing it to die. Is there a timeout (it takes 10s of seconds to read the memories)?
Error is ... 8 workers [0 items] scheduling tests via LoadScheduling
--- Generated html report: file:///Users/declan/darchirp/driver_report.html ---- =========================== 1139 warnings in 16.93s ============================ driver: exit 5 (17.43 seconds) /Users/declan/darchirp> pytest --disable-warnings --html=driver_report.html -v tests/test_drivers.py -n auto -k Yaesu_Elecraft_KX3 pid=77757 .pkg: _exit> python /usr/local/lib/python3.11/site-packages/pyproject_api/_backend.py True setuptools.build_meta __legacy__ driver: FAIL code 5 (28.39=setup[10.96]+cmd[17.43] seconds) evaluation failed :( (28.55 seconds)
Developers mailing list -- developers@lists.chirpmyradio.com To unsubscribe send an email to developers-leave@lists.chirpmyradio.com
pytest exit code 5 is "No tests were collected".
Yep.
Did you add a test file? If so, are the tests in a form that pytest will discover them?
The invocation by tox will select the files. The problem is this:
driver: exit 5 (17.43 seconds) /Users/declan/darchirp> pytest --disable-warnings --html=driver_report.html -v tests/test_drivers.py -n auto -k Yaesu_Elecraft_KX3
He asked to only test the "Yaesu_Elecraft_KX3" which of course makes no sense (i.e. doesn't match the keyword on any test).
FYI, you can use the "fast-driver" tox target, which will attempt to only run tests on drivers changed since origin/master, but if you have anything outside of drivers/ changed it will revert back to "everything".
--Dan
Thanks for the quick reply. And for knowing what the exit code means. I didn’t even know that purest is what was used (tox is just a tool one is required to use for me.)
No, I’ve not added a test file. It makes sense that one needs to be written for a completely new driver but I’ve only modified old ones before.
On Nov 13, 2024, at 12:50, Martin Cooper via Developers developers@lists.chirpmyradio.com wrote:
pytest exit code 5 is "No tests were collected".
https://docs.pytest.org/en/7.1.x/reference/exit-codes.html https://docs.pytest.org/en/7.1.x/reference/exit-codes.html
Did you add a test file? If so, are the tests in a form that pytest will discover them?
Martin. KD6YAM
participants (3)
-
Dan Smith -
Declan Rieb -
Martin Cooper