search

cbitstech / Purple-Robot

Sensing and automation platform for Android.
Other
38 stars 19 forks source link

Prior trigger execution timing when fire_on_boot = false? #229

Closed estory1 closed 10 years ago

estory1 commented 10 years ago

Not sure what the timing for running or not running prior triggers looks like…

Three tests have produced the following results (the first two tests’ times are approximate, based on memory). (For future readers unfamiliar with the terminology here: [1])

Note that a passing (desired) result in each case is: • MP-5min did not fire. • MP+0min did not fire.

Tests:

  1. MP-5min = 14:15, MP+0min = 14:20; powered-off phone @ 14:12; powered-on phone @ 14:21: a. Actual result (fail):
    1. MP-5min fired.
    2. MP+0min did not fire.
  2. MP-5min = 14:25, MP+0min = 14:30; powered-off phone @ 14:23; powered-on phone @ 14:31: a. Actual result (fail):
    1. MP-5min fired.
    2. MP+0min did not fire.
  3. MP-5min = 15:42, MP+0min = 15:47; powered-off phone @ 15:40; powered-on phone @ 15:55: a. Actual result (pass!):
    1. MP-5min did not fire.
    2. MP+0min did not fire.

Test config file you can use: http://app2.cbits.northwestern.edu/output_files/MA/T.CK.prCfg.json.txt

[1] MP = Medprompt -- a trigger to be fired at some scheduled time. The +/-Xmin nomenclature is a name that redundantly contains the time distance from the Medprompt.

estory1 commented 10 years ago

Neither @audaciouscode nor I could reproduce this in multiple subsequent tests. Will reopen if observed again.