fixes flaky test

[squeedee]

• just extends the timeout, hopefully that is enough.
• ultimately, story to use informers will make this test redundant
  [Running an Informer on a Simple Change #23]

Co-authored-by: Emily Johnson emjohnson@vmware.com

[netlify]

✔️ Deploy Preview for elated-stonebraker-105904 canceled.

🔨 Explore the source changes: fee48dc

🔍 Inspect the deploy log: https://app.netlify.com/sites/elated-stonebraker-105904/deploys/615b4b22b30d9600070d63d2

[cirocosta]

> ultimately, story to use informers will make this test redundant

aah maybe I'm misunderstanding the test, but I thought that polling interval wasn't relevant because of how what we're testing here is all about shorticuiting the interval in the first place 🤔 isn't that the case?

[cirocosta]

lgtm

[squeedee]

> ultimately, story to use informers will make this test redundant

aah maybe I'm misunderstanding the test, but I thought that polling interval wasn't relevant because of how what we're testing here is all about shorticuiting the interval in the first place 🤔 isn't that the case?

The way I read it is, this test ensures that backoff is shortcut by observing a supply chain change. It's really simple to prove that it's applied but not that the component chain's speed is reset to "fast"

If the speed isn't reset, then any component affected by the supply chain change will immediately restamp. but we might still wait hours to copy results down the chain. Happy to be corrected.

So assuming I'm right about the above, then there's no concerns about backoff when we use informers instead, because updates to the stamped resource trigger a reconcile