Closed calebschoepp closed 8 months ago
I tried running the tests a few times to reproduce this issue, but unable to. Is there a specific command that triggers this behavior?
I think this is actually because we use the shared scheme in the testenv client:
https://github.com/spinkube/spin-operator/blob/main/internal/webhook/admission_test.go#L63-L71
(I wasn't super expecting parallel integration tests - we'll need to switch it to making a new scheme, add in default types, and our types)
I tried running the tests a few times to reproduce this issue, but unable to. Is there a specific command that triggers this behavior?
I was getting locally just running make test
. Might be really rare or something that is specific to my machine.
Removing from the initial milestone - looks like something we can fix async. I don't think the bug actually affects anything in prod, but please correct me if I'm wrong on that.
Removing from the initial milestone - looks like something we can fix async. I don't think the bug actually affects anything in prod, but please correct me if I'm wrong on that.
Correct, this has no impact on prod deployments.
@endocrimes does #134 fix this?
Yep
I'm experiencing the integration tests flaking occasionally because of a race condition. I've been unable to diagnose the issue so far but I think it has something to do with this code.