Impact label assignment

[Dor1s]

1. https://bugs.chromium.org/p/chromium/issues/detail?id=1139963#c9 the Security_Impact-Stable label was manually assigned.
2. https://bugs.chromium.org/p/chromium/issues/detail?id=1139963#c40 ClusterFuzz assigned Security_Impact-Beta and removed Security_Impact-Stable, although the regression range was pointing far into the past
3. https://bugs.chromium.org/p/chromium/issues/detail?id=1139963#c45 the Security_Impact-Beta label was manually replaces with Security_Impact-Stable again

Now ClusterFuzz shows that the crash impacts Stable too. Did ClusterFuzz learn it from the bug tracker, or did it succeed reproducing the issue on stable?

If the latter, why did ClusterFuzz put the Beta label in the first place?

[Dor1s]

c#47 hints that the initial reproducer might've been unreliable / failing to reproduce on Stable.

I'll check the logs.

[Dor1s]

I've uploaded another testcase from that bug. It has been processed correctly: https://clusterfuzz.com/testcase-detail/5742515649314816

Also nothing suspicious in the logs for the original testcase (https://clusterfuzz.com/testcase-detail/5740292802412544).

I've exported all the logs into JSON, can share the file.

My last guess would be that CF detected Beta impact first and went head to set that label (plus to remove the Stable one). Later on, CF detected Stable impact too, but it the bug was already updated manually. If that's true, then the question is whether thisis WAI or we shouldn't remove manually assigned impact labels?

@mbarbella-chromium offered to help with this. Thanks a lot Marty!