[chirp_devel] TOX testing - potential unexpected condition?

[Dan Smith]

> In my test image, I have a couple of the PMS memories blanked out. In the FT450/D py get memory routines we set mem.empty = true to keep them from displaying on the gui.
> 
> When the test_edges.py  test_get_set_specials routine tries to set the special memories, it does not clear the mem.empty to False after reading what's already there.
> 
> The FT450/D set special memory routines see an incoming request for an "empty" memory, and they make no changes and do not return a memory element. (as expected). The test_get_set_specials routine barfs on this, as the memory element returned is not what they expected. 
> 
> I added the m1.empty = False statement to the routine test_edges.py and the test now passes properly for the cleared memory.

Well, much of chirp expects those specials to not be empty or deletable. However, the new UI technically supports it. I'm guessing maybe some of those fails are because those radios have empty in the immutable set, but I'd have to take a look.

> While I would love for Chirp to accurately reflect what is on the radio, I'm concerned about perturbing the other radio models. (Just the testing obviously)

The easy thing to do for the moment is just make all the specials never empty in your driver, which will make it like basically every other radio. I'll have a look at the failures when we set empty=False in the test.

--Dan