#141 1885154 retrace jobs seem to always fail
Closed 8 months ago by blockerbot. Opened a year ago by blockerbot.

Bug details: https://bugzilla.redhat.com/show_bug.cgi?id=1885154

Current vote summary

  • Rejected FinalBlocker (+1, 0, -0)
  • Accepted FinalFE (+0, 0, -0)

Commented but haven't voted yet: kparal, coremodule

The votes have been last counted at 2020-10-05 19:50 UTC and the last processed comment was #comment-693603

To learn how to vote, see:
https://pagure.io/fedora-qa/blocker-review


I'm not completely sold on the blocker status here. You can still process the coredump locally. The retrace server sometimes doesn't work anyway (e.g. if you have an older package than available in stable updates, I believe). It's bad that it fails every time (it seems), but I'm on the fence here.

AGREED AcceptedFinalFE RejectedFinalBlocker

Discussed during the 2020-10-05 blocker review meeting: [0]

The decision to classify this bug as a "RejectedBlocker" and an "AcceptedFreezeException" was made as the app is likely working (the bug is likely in the retrace server itself), and local traceback generation does work so we aren't stuck without being able to report crashes. Accepted as a freeze exception issue just in case a fix is needed to the package, obviously we would want that in for release.

[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2020-10-05/f33-blocker-review.2020-10-05-16.00.txt

The following votes have been closed:

  • Rejected FinalBlocker (+1, 0, -0)
  • Accepted FinalFE (+0, 0, -0)

Metadata Update from @blockerbot:
- Issue status updated to: Closed (was: Open)

8 months ago

Release F33 is no longer tracked by BlockerBugs, closing this ticket.

Login to comment on this ticket.

Metadata