[chirp_devel] Fixing bugs for a (live) radio I don't have
While looking into adding support for a new (to Chirp) Icom live radio, I've come across a bug (#5023) for a different Icom live radio. The fix for that bug will also be needed for the radio I'm looking to add. (The Icom live radios share the bulk of their code in a single driver file.)
It would be great to have one or two of the people who have chimed in on #5023 test the (small) change to make sure it will work for both radios. Since this is a live radio situation, there are no images for me to run tests against.
Is there a commonly used scenario for addressing this? I'm not in a position to build for multiple platforms to give people something to test, and I couldn't find anything in the developer docs (all of which I've read) that talks about this.
Your guidance would be appreciated.
Martin. KD6YAM
Hi Martin,
While looking into adding support for a new (to Chirp) Icom live radio, I've come across a bug (#5023) for a different Icom live radio. The fix for that bug will also be needed for the radio I'm looking to add. (The Icom live radios share the bulk of their code in a single driver file.)
It would be great to have one or two of the people who have chimed in on #5023 test the (small) change to make sure it will work for both radios. Since this is a live radio situation, there are no images for me to run tests against.
Is there a commonly used scenario for addressing this? I'm not in a position to build for multiple platforms to give people something to test, and I couldn't find anything in the developer docs (all of which I've read) that talks about this.
Such is life for this project where we can't all have all the radios locally to test. You can comment in your bug, or ask people from another bug to check out yours. Also, ask for volunteers on the chirp_users list which have the necessary radios, etc.
Note that with developer tools turned on, you can have people load changed .py files to test something without generating a new build. It's a big hammer and should be used sparingly by people willing to test potentially destructive things, but it's a good way to get people on a bug to help you test something. With those tools enabled File->Load Module. Just send them the file (or files) necessary for testing and have them load them before they test.
--Dan
Thanks. I hadn't noticed Load Module before, so that's good to know about. As you say, a big hammer, but may come in handy.
As it turns out, I am just about ready to submit a patch to add support for a new radio. (Patchbomb is new to me.) As part of that, I have to fix the other bug, or it will break the other radio for sure. I will indeed note that bug and fix in the commit message.
(Detail: A field definition was incorrectly typed in the other radio, but the field was never referenced - which is why users couldn't change it. The same field is present in the new radio, so my patch to add the new radio will allow users to change the field for both radios.)
Martin. KD6YAM
On Sun, Jun 21, 2020 at 11:23 AM Dan Smith via chirp_devel < chirp_devel@intrepid.danplanet.com> wrote:
Hi Martin,
While looking into adding support for a new (to Chirp) Icom live radio,
I've come across a bug (#5023) for a different Icom live radio. The fix for that bug will also be needed for the radio I'm looking to add. (The Icom live radios share the bulk of their code in a single driver file.)
It would be great to have one or two of the people who have chimed in on
#5023 test the (small) change to make sure it will work for both radios. Since this is a live radio situation, there are no images for me to run tests against.
Is there a commonly used scenario for addressing this? I'm not in a
position to build for multiple platforms to give people something to test, and I couldn't find anything in the developer docs (all of which I've read) that talks about this.
Such is life for this project where we can't all have all the radios locally to test. You can comment in your bug, or ask people from another bug to check out yours. Also, ask for volunteers on the chirp_users list which have the necessary radios, etc.
Note that with developer tools turned on, you can have people load changed .py files to test something without generating a new build. It's a big hammer and should be used sparingly by people willing to test potentially destructive things, but it's a good way to get people on a bug to help you test something. With those tools enabled File->Load Module. Just send them the file (or files) necessary for testing and have them load them before they test.
--Dan _______________________________________________ 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
participants (2)
-
Dan Smith -
Martin Cooper