Bug details: https://bugzilla.redhat.com/show_bug.cgi?id=2058920 Information from BlockerBugs App: <img alt="2058920" src="https://qa.fedoraproject.org/blockerbugs/api/v0/bugimg/2058920" />
Commented but haven't voted yet: coremodule
The votes have been last counted at 2022-03-07 22:41 UTC and the last processed comment was #comment-784838
To learn how to vote, see: https://pagure.io/fedora-qa/blocker-review A quick example: BetaBlocker +1 (where the tracker name is one of BetaBlocker/FinalBlocker/BetaFE/FinalFE/0Day/PreviousRelease and the vote is one of +1/0/-1)
BetaBlocker +1
BetaBlocker
FinalBlocker
BetaFE
FinalFE
0Day
PreviousRelease
+1
0
-1
Discussed during the 2022-02-28 blocker review meeting: [0]
The decision to delay the classification of this as a blocker bug was made as we don't have enough info on the causes, consequences or prevalence of this crash to make a decision yet. Chris will report it upstream and see if that gets us anywhere.
[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2022-02-28/f36-blocker-review.2022-02-28-17.00.txt
FinalBlocker -1
Crashes are sad and should be fixed, but I don't think this violates the basic functionality criterion.
Without steps to reproduce showing a common use case, I don't really see this as blocking. Curious to see what's in the locked bug...
AGREED RejectedFinalBlocker
Discussed during the 2022-03-07 blocker review meeting: [0]
The decision to classify this bug as a "RejectedBlocker (Final)" was made as this still doesn't seem clearly reproducible or commonly encountered at present. We will reconsider if clear steps to reproduce are found.
[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2022-03-07/f36-blocker-review.2022-03-07-17.01.txt
The following votes have been closed:
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F36 is no longer tracked by BlockerBugs, closing this ticket.
Log in to comment on this ticket.