I'll go one step further. If I wanted to ENSURE that as many machines "glitched" as possible, I WOULD roll out an update day of. Most county boards of elections will not accept a change to a machine after certification. Because of this, all I would need to do is make sure the LAST software had a threshold of say 1000 Republican ballots before implementing "glitches", since the tests themselves are needed to be performed rapidly to get all the machines validated and "freeze" them for the election. Test ballots are likely a few hundred for each candidate, and then verified by known numbers coming back from the tests. This also explains the SHIVA Analysis results, since as more people vote straight republican the more the votes skew Biden. If you set a threshold to then go through your OWN acknowledged test functions to swap ballots, then after the election when the machines are "unfrozen" your new patch gets applied to wipe away your evidence, and if it DOESN'T get wiped you have the excuse "but we already issued the patch and alerted them, this is on THEM not us!".
I'll go one step further. If I wanted to ENSURE that as many machines "glitched" as possible, I WOULD roll out an update day of. Most county boards of elections will not accept a change to a machine after certification. Because of this, all I would need to do is make sure the LAST software had a threshold of say 1000 Republican ballots before implementing "glitches", since the tests themselves are needed to be performed rapidly to get all the machines validated and "freeze" them for the election. Test ballots are likely a few hundred for each candidate, and then verified by known numbers coming back from the tests. This also explains the SHIVA Analysis results, since as more people vote straight republican the more the votes skew Biden. If you set a threshold to then go through your OWN acknowledged test functions to swap ballots, then after the election when the machines are "unfrozen" your new patch gets applied to wipe away your evidence, and if it DOESN'T get wiped you have the excuse "but we already issued the patch and alerted them, this is on THEM not us!".