Closed dubee closed 6 years ago
@jberstler, any thoughts on this?
Ah, I see. We are spamming the backend Whisk server with activation list
requests with pollFor
when we can just do a timeout based from 60 * maxRetries
then do one activation list
.
Tests poll for 100 activations matching
triggerName
formaxRetries
. Doing this means we have to worry about the clock for the backend being in sync with the machine the health test runs on. Instead we can just get the lastx
related activations in one request and repeat the testmaxRetries
until we get the activation ID we are looking for.Also we may have more than one matching activation due to the retry loop.