René Schumacher

Hi @StephenWBertrand, I'm very sorry to see this happening again 😞. Afaik, the issue should have been resolved as it was caused by a misconfigured feature flag in one of...

I have checked your logs and the feature flag looks good even in the failing run. So, the issue might have been caused by a performance degradation in Azure DevOps...

Hi @nickduch, sorry for the delay, I have been on vacation until yesterday. Let me first rephrase what you're trying to achieve to see if I really understood the issue...

Hey, the baseline behavior hasn't changed in version 9.x, so I'm not surprised that you see the same behavior. I just double checked the code and realized that I forgot...

Hi @szabolcsleitner, warning selectors cannot be used to ignore warnings. Instead, you tell BQC to only evaluate warnings matching your selector expressions. So, while it is theoretically possible to create...

Hi again, unfortunately, we haven't implemented any filters for warnings in our task. We have discussed about this years ago and decided against it. We may add them in the...

Hm, got it. Looks like a pretty special case to me. Let's see if I can quickly add warning exclusions to the task.

Hi @szabolcsleitner, we're in the process of releasing an update to BQC, which supports warning exclusions. Should be available in the marketplace within the next couple hours. Hope it meets...

@szabolcsleitner Great, thanks for confirming and thank you for using our task. Please let us know if you need anything else.

Hi @CIPop, currently, the requested behavior is not supported by BQC since we're not parsing/understanding the coverage data directly. BQC merely works based on the coverage summary data provided by...