[chirp_devel] TOX tests on Mac.
Dan Smith
Tue Feb 20 18:27:24 PST 2018
> Added serial to tox deps and it gets a bit further, any thoughts? as before UNKNOWN-0.0.0.zp can't be write, and now we have no module named chirp. Is there something to be done with the build first? Thanks. Nicolas
>
> nicolass-Mac-mini:chirp.hg nicolas$ tox -e driver -- -d Icom_IC-2820H
> GLOB sdist-make: /Users/nicolas/Documents/FT70CHIRP/chirp.hg/setup.py
> driver inst-nodeps: /Users/nicolas/Documents/FT70CHIRP/chirp.hg/.tox/dist/UNKNOWN-0.0.0.zip
> ERROR: invocation failed (exit code 1), logfile: /Users/nicolas/Documents/FT70CHIRP/chirp.hg/.tox/driver/log/driver-4.log
> ERROR: actionid: driver
> msg: installpkg
> cmdargs: ['/Users/nicolas/Documents/FT70CHIRP/chirp.hg/.tox/driver/bin/pip', 'install', '-U', '--no-deps', '/Users/nicolas/Documents/FT70CHIRP/chirp.hg/.tox/dist/UNKNOWN-0.0.0.zip']
>
> Processing ./.tox/dist/UNKNOWN-0.0.0.zip
> Complete output from command python setup.py egg_info:
> Traceback (most recent call last):
> File "<string>", line 1, in <module>
> File "/private/var/folders/yf/rh0gfjk57pzfvdls7z6nwnmr0000gn/T/pip-kuILg4-build/setup.py", line 5, in <module>
> from chirp import CHIRP_VERSION
> ImportError: No module named chirp
Yeah, I dunno, sorry. I tried on a mac I had access to and I didn't even get this far. I can try to debug it more later, but no obvious ideas. The UNKNOWN-0.0.0 stuff definitely looks funky to me.
You can still run the driver tests manually by running tests/run_tests, which might be easier for you.
--Dan
More information about the chirp_devel
mailing list