As mentioned when we talked about this on the phone, I don't think this is the best way to approach the problem. Currently, if a test hangs, times out, reboots improperly (and thus times out because it won't get to the expected place), lava will reboot the system back into the test image.  However, at this point, it will mark the previous testsuite it tried to run as a failed run.  Then, if there are other tests queued up to run, it will continue running with the next one - NOT try to re-enter the existing test and continue where it left off.  This is not a capability currently supported in lava-android-test.

The good news is, I think there's a much more straightforward way to do this.
I haven't really seen an example of the kinds of things you want to run, but it seems that it's just a list of several tests, possibly with multiple steps in each test.  And if it reboots, or has a problem, you want it to fail that one and continue to the next.  This is very simple to do, if you simply define each of those tests as lava-android-tests.  Then you can run them all in your test job, and I think it will do exactly what you are looking for here.  Also, they can then be easily reused in other test jobs.

Thanks,
Paul Larson