[chirp_devel] TOX tests on Mac.
ImportError: cannot import name Serial
What part of the setup have I missed?
You're missing python-serial. Can you add deps=serial to the [testenv:driver] section in tox.ini and see if that works?
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
----------------------------------------
Command "python setup.py egg_info" failed with error code 1 in /private/var/folders/yf/rh0gfjk57pzfvdls7z6nwnmr0000gn/T/pip-kuILg4-build/
*driver installed: future==0.16.0,iso8601==0.1.12,libxml2-python==2.9.7,lxml==4.1.1,mercurial==4.5,pluggy==0.6.0,py==1.5.2,pycairo==1.15.3,PyYAML==3.12,serial==0.0.38,six==1.11.0,tox==2.9.1,virtualenv==15.1.0*
_______________________________________________________________________________ summary _______________________________________________________________________________
ERROR: driver: InvocationError: /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 (see /Users/nicolas/Documents/FT70CHIRP/chirp.hg/.tox/driver/log/driver-4.log)
nicolass-Mac-mini:chirp.hg nicolas$
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
On Tue, Feb 20, 2018 at 9:27 PM Dan Smith via chirp_devel chirp_devel@intrepid.danplanet.com wrote:
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
This is the same error that is experienced in a DevelopersWin32Environment. What the file should look like is "chirp-0.3.0dev.zip". Not knowing much about it, it seem the CHIRP_VERSION can't be imported because the "module named chirp" is missing or otherwise can't be accessed. Whatever the issue is, it is common to Windows and macOS. I have finally figured out all the steps needed to setup a DevelopersLinuxEnvironment and submitted my first patch using it. I would much rather do it on my Win32 system, though.
Jim
I don't know whether it is related, but I had the same issue under Win10. I moved my stuff to Linux, where at first it didn't work either - it took me a few days until I discovered that for permissions reasons, one cannot have the code on a drive with a VFAT file system (I have all my data on a portable memory stick which is easy to carry around and to back up).
Once moved to a EXT4 file system, tox worked great. I didn't try back on Windows, whether that would fix the problem as well.
73 Bernhard
On 12/30/19 5:06 PM, Jim Unroe via chirp_devel wrote:
On Tue, Feb 20, 2018 at 9:27 PM Dan Smith via chirp_devel chirp_devel@intrepid.danplanet.com wrote:
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
This is the same error that is experienced in a DevelopersWin32Environment. What the file should look like is "chirp-0.3.0dev.zip". Not knowing much about it, it seem the CHIRP_VERSION can't be imported because the "module named chirp" is missing or otherwise can't be accessed. Whatever the issue is, it is common to Windows and macOS. I have finally figured out all the steps needed to setup a DevelopersLinuxEnvironment and submitted my first patch using it. I would much rather do it on my Win32 system, though.
Jim _______________________________________________ chirp_devel mailing list chirp_devel@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_devel Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers
On Mon, Dec 30, 2019 at 8:16 PM Bernhard Hailer via chirp_devel chirp_devel@intrepid.danplanet.com wrote:
I don't know whether it is related, but I had the same issue under Win10. I moved my stuff to Linux, where at first it didn't work either - it took me a few days until I discovered that for permissions reasons, one cannot have the code on a drive with a VFAT file system (I have all my data on a portable memory stick which is easy to carry around and to back up).
Once moved to a EXT4 file system, tox worked great. I didn't try back on Windows, whether that would fix the problem as well.
73 Bernhard
That's good to know. I was thinking about moving my chirp.hg folder over to an NVME drive that is formatted FAT32. I can see where they may be an issue. I'm still going to try it, though.
Jim KC9HI
Jim
During my research, I read that NTFS would work (it's actually POSIX compliant), but it does take some doing. That's still running under Linux.
I'd also be interested to get it running under Windows, although I'm doing ok now with Linux.
73 Bernhard AE6YN
On 12/30/19 5:24 PM, Jim Unroe wrote:
On Mon, Dec 30, 2019 at 8:16 PM Bernhard Hailer via chirp_devel chirp_devel@intrepid.danplanet.com wrote:
I don't know whether it is related, but I had the same issue under Win10. I moved my stuff to Linux, where at first it didn't work either - it took me a few days until I discovered that for permissions reasons, one cannot have the code on a drive with a VFAT file system (I have all my data on a portable memory stick which is easy to carry around and to back up).
Once moved to a EXT4 file system, tox worked great. I didn't try back on Windows, whether that would fix the problem as well.
73 Bernhard
That's good to know. I was thinking about moving my chirp.hg folder over to an NVME drive that is formatted FAT32. I can see where they may be an issue. I'm still going to try it, though.
Jim KC9HI
Jim
participants (4)
-
Bernhard Hailer -
Dan Smith -
Jim Unroe -
Nicolas Pike