[chirp_devel] Build test results: Failure
Mathias Weyland
Tue Mar 13 10:58:45 PDT 2018
On 2018-03-08 15:24, Build System via chirp_devel wrote:
Hello
> Tested changes:
>
> Changes for Build #723
> [Mathias Weyland <lt-betrieb at hb9uf.ch>] [Alinco DJ-G7] Introduce
> empty flag, mode & frequency range checks.
> [...]
> style runtests: commands[0] | python ./tools/cpep8.py
> ./chirp/drivers/alinco.py:752:11: E271 multiple spaces after keyword
> ./chirp/drivers/alinco.py:752:24: E222 multiple spaces after operator
> ./chirp/drivers/alinco.py:752:46: E222 multiple spaces after operator
> ./chirp/drivers/alinco.py:753:24: E222 multiple spaces after operator
> ./chirp/drivers/alinco.py:753:46: E222 multiple spaces after operator
> ./chirp/drivers/alinco.py:764:80: E501 line too long (81 > 79
> characters)
> ./chirp/drivers/alinco.py:766:80: E501 line too long (80 > 79
> characters)
> ./chirp/drivers/alinco.py:769:80: E501 line too long (122 > 79
> characters)
> ./chirp/drivers/alinco.py:771:80: E501 line too long (84 > 79
> characters)
> ./chirp/drivers/alinco.py:772:80: E501 line too long (118 > 79
> characters)
> ./chirp/drivers/alinco.py:777:80: E501 line too long (80 > 79
> characters)
> ERROR: InvocationError:
> '/var/lib/jenkins/jobs/chirp-test/workspace/.tox/style/bin/python
> ./tools/cpep8.py'
OK my apologies for that. I would like to blame it on something but I
guess the best course of action is to seek for the brown paper bag.
Patch attached.
Regards and thank you
Matt
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: chrip_alinco_djg7_linter.patch
Url: http://intrepid.danplanet.com/pipermail/chirp_devel/attachments/20180313/962f6791/attachment-0001.pl
More information about the chirp_devel
mailing list