This script is in the tests folder. The tests folder is not controlled in the way the Dialin files are controlled so I might go back and forth in between different tests. This is not affecting any of the Dialin features.
This script is in the tests folder. The tests folder is not controlled in the way the Dialin files are controlled so I might go back and forth in between different tests. This is not affecting any of the Dialin features.
I think better to use self test status enum (mentioned in .h comment). This enum will have pass/fail/in progress. I think if we're still in INIT, zero, or self-test state, in-progress is appropriate return value. I think you should have a BOOL variable defined to remember whether self-test passed or failed (instead of inferring from current state). Then if in normal state, return pass if self-test passed, failed if not.
This script is in the tests folder. The tests folder is not controlled in the way the Dialin files are controlled so I might go back and forth in between different tests. This is not affecting any of the Dialin features. Last time it was used to program the HD RTC clock.
For files in the peter folder I understand. However, with the repo scripts in this folder are typically shared with cross-functional teams and are "forward facing."
If alarm is recoverable, we should go to paused state. If not, we should not delete this line of code so we can exit fill mode. Otherwise, we get stuck here forever.
