Bugzilla

(In reply to Timothy Nikkel (:tnikkel) from comment #4)
> There's only about a dozen bugs depending on this, pretty easy to skim through them to see.

Suhaib does not regularly triage platform bugs, so more specific feedback from somebody like you who does would probably be more actionable. I don't think there's been any feedback from anybody who does a lot of graphics triage, so I'm sure that would be a welcome perspective.

I looked over all of the bugs reported so far, and it does look like the reporting threshold for bugs without anything to make them particularly actionable seems rather low. Specifically, there are a bunch of crashes in graphics drivers (bug 1862276, bug 1862279, bug 1862280, bug 1862283) that have only happened a couple of times in the last week on Nightly, so I don't think they should be filed. A few of them only happened once. Bug 1862347 is another crash in graphics drivers, though that one is a bit odd because it is a null pointer crash, but it is still happening in graphics code with very low volume, so the odds of us being able to take a action to fix it are very low.

Bug 1862348 has only happened twice in the last week on Nightly, and is not a null crash or an assert so it also seems like it would have been better to not file it.

Bug 1862284 and bug 1862349 also have only happened a few times each, but they are release asserts in our code, so there might be something actionable thing, so it looks reasonable to me (as a non-graphics person) that bugs were filed for them.

(In reply to Timothy Nikkel (:tnikkel) from comment #4)
> There's only about a dozen bugs depending on this, pretty easy to skim through them to see.

Suhaib does not regularly triage platform bugs, so more specific feedback from somebody like you who does would probably be more actionable. I don't think there's been any feedback from anybody who does a lot of graphics triage, so I'm sure that would be a welcome perspective.

I looked over all of the bugs reported so far, and it does look like the reporting threshold for bugs without anything to make them particularly actionable seems rather low. Specifically, there are a bunch of crashes in graphics drivers (bug 1862276, bug 1862279, bug 1862280, bug 1862283) that have only happened a couple of times in the last week on Nightly, so I don't think they should be filed. A few of them only happened once. Bug 1862347 is another crash in graphics drivers, though that one is a bit odd because it is a null pointer crash, but it is still happening in graphics code with very low volume, so the odds of us being able to take a action to fix it are very low.

Bug 1862348 has only happened twice in the last week on Nightly, and is not a null crash or an assert so it also seems like it would have been better to not file it.

Bug 1862284 and bug 1862349 also have only happened a few times each, but they are release asserts in our code, so there might be something actionable, so it looks reasonable to me (as a non-graphics person) that bugs were filed for them.