ci:github: retry Test Tetragon on failure

[tixxdz]

closes: #2966

[netlify]

✅ Deploy Preview for tetragon ready!

Name	Link
🔨 Latest commit	a50cd25
🔍 Latest deploy log	https://app.netlify.com/sites/tetragon/deploys/670d91d8169ed800086ae274
😎 Deploy Preview	https://deploy-preview-3001--tetragon.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[mtardy]

sure I imagine we can merge this but it doesn't feel very satisfying as it's not fixing the underlying issue just automating the retries.

Since in this case the commands are simple enough, maybe we should understand which commands returned != 0 and why?

[tixxdz]

sure I imagine we can merge this but it doesn't feel very satisfying as it's not fixing the underlying issue just automating the retries.

Since in this case the commands are simple enough, maybe we should understand which commands returned != 0 and why?

It depends since we parse logs and json events, ion tetragon startup logic, how long it takes..., or when loading policies dynamically how long it takes to add kprobes and have them on the output, so we can try to be smart, but I don't think it really worth it, or it matters since we just retry to see if events showed up or logs were successful or not.