Closed stevieb9 closed 7 years ago
So, this is caused by brewbuild using the Dispatch module, which if BB_RPI_LCD
set, creates an LCD object immediately which throws off all of the pin status checks.
Need to think about this. Somehow skip/remove the LCD pins from testing/being reset if it's BB running the tests, and BB_RPI_LCD is set?
Perhaps manually registering the LCD pins in Dispatch so that when the tests start, the already-changed pin states will be reflected in test results/reset? Then we'd have to either have a DESTROY to un-register/unset them after a run.
Perhaps:
RPi::WiringPi::Util::cleanup()
?After update to Dispatch, things now work if the env var is set, but we're not using the dispatcher in auto mode. Will have to take corrective action after testing that functionality.
I wonder if it's due to the env var not being available? It's not just brewbuild... bbdispatch too.
Perhaps we need to make the pin registrations disk-based.