The source project of this merge request has been removed.
Fix a spec to avoid writing to prometheus
What does this MR do?
Fixes an order-dependency in specs by stopping the causative spec from writing to prometheus
Are there points in the code the reviewer needs to double check?
Ideally, we'd flush prometheus state between specs, but I can't find a quick way to do that and this spec doesn't need to write to prom.
Why was this MR needed?
Order-dependent spec failures on master
What are the relevant issue numbers?
Closes #3965 (closed)
/cc @stanhu @bjk-gitlab