Closed stevieb9 closed 4 years ago
The good thing here is that there's only a single shared memory segment and semaphgre at all times.
It's looking a whole lot better now. Going to run a dispatch until tomorrow and see the results before closing this.
Although I've added the ability to separate shared mem spaces between prod and test, this is still on the radar.
It appears as though it's related to PWM and multi tests. The tester seems to hang mid-flight.
Overall though, ~70 runs kept things relatively very clean.
This is becoming a bigger problem. t/310-dac.t
fails, we have three pins remaining and can't be used again.
pi@pi-test:~/repos/rpi-wiringpi $ pimeta rpit
$VAR1 = {
'objects' => {
'717545823cf2906f35e7ebd3dfc16ec0' => {
'proc' => 872,
'label' => 't/310-dac.t'
},
'd8250d07b27ee37c8fb97b7bff54c2a7' => {
'label' => 'serial_arduino_display',
'proc' => 374
},
'e369f185a7832fc05bda4ec12eb1c7c3' => {
'proc' => 377,
'label' => 'oled display date/time'
}
},
'pwm' => {},
'pins' => {
'12' => {
'mode' => 0,
'state' => 0,
'comment' => 'MCP4922 DAC CS',
'users' => {
'717545823cf2906f35e7ebd3dfc16ec0' => 1
},
'alt' => 0
},
'26' => {
'alt' => 0,
'users' => {
'717545823cf2906f35e7ebd3dfc16ec0' => 1
},
'comment' => 'MCP3008 ADC CS',
'state' => 0,
'mode' => 0
}
},
'object_count' => 3,
'testing' => {
'test_num' => '310',
'test_name' => 'dac'
}
};
The latter comment refers to #160, but things should still clean up properly if a program or test file crashes
Unit test suite now cleans up properly
We will somehow need a test to ensure that failed tests clean up properly...