consider removing looping from Test(), thereby removing the need for test_stop.

right now test_stop triggers get passed the dut_id only, but there may be other information in the test_record that the stop trigger may want to use. In my case, I got around this by instantiating a class that provides both an output callback and a test_stop trigger and stashing the test_record when the former is called for accessing in the latter.

i’d like to propose we update the calling convention of test_stop triggers to take the entire test_record (note that because it’s already been output, this is a read-only view of the test_record). Thoughts? Does this break anyone?

[jettisonjoe]

#!/bin/bash

crontab -e

Nailed it.

[fahhem]

The over-engineered, fewer features version of cron. You know, what any self-respecting engineer would do to show impact 😆

while True:
  test.Execute()
  time.sleep(60*minutes)