After a reboot of the test platform, the I2C test file fails on the first pass.
We could probably just do an initial run without tests, save an env var that the 'pilot' has been run, then subsequent testing could skip that block if said env var is set.
Realistically though, it would be best if we actually found and fixed the underlying problem, as it could be confusing as all hell for end-users.
After a reboot of the test platform, the I2C test file fails on the first pass.
We could probably just do an initial run without tests, save an env var that the 'pilot' has been run, then subsequent testing could skip that block if said env var is set.
Realistically though, it would be best if we actually found and fixed the underlying problem, as it could be confusing as all hell for end-users.