[Fedora QA] #381: Bug and Update syncs shouldn't be halted by an isolated problem with one update or bug
by fedora-badges
#381: Bug and Update syncs shouldn't be halted by an isolated problem with one
update or bug
--------------------------------------+----------------------------------
Reporter: tflink | Owner: tflink
Type: enhancement | Status: new
Priority: major | Milestone: Undetermined Future
Component: Blocker bug tracker page | Version:
Keywords: | Blocked By:
Blocking: |
--------------------------------------+----------------------------------
= problem =
The current bug and update sync algorithms are very fragile in that one
error will stop the entire sync algorithm, leaving stuff out of sync with
bodhi or bugzilla. This has caused problems in the past
= analysis =
This could be solved by better error handling in the sync process such
that an error is logged but doesn't bubble up to the main sync code and
halt the entire process.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/381>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
10 years, 2 months
[Fedora QA] #384: Improve documentation
by fedora-badges
#384: Improve documentation
--------------------------------------+------------------------
Reporter: tflink | Owner: tflink
Type: enhancement | Status: new
Priority: major | Milestone: Fedora 20
Component: Blocker bug tracker page | Version:
Keywords: | Blocked By:
Blocking: |
--------------------------------------+------------------------
= problem =
At the moment, our documentation is out of date and somewhat incomplete.
= analysis =
Update the docs and find an appropriate place for them to live.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/384>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
10 years, 2 months
[Fedora QA] #440: show also closed bugs
by fedora-badges
#440: show also closed bugs
--------------------------------------+---------------------
Reporter: sharkcz | Owner: tflink
Type: enhancement | Status: new
Priority: major | Milestone:
Component: Blocker bug tracker page | Version:
Keywords: | Blocked By:
Blocking: |
--------------------------------------+---------------------
I would like to be able to see also closed blocker bugs, not only the
pending ones. The current setup can be the default and have a check box
for showing the closed ones.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/440>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
10 years, 2 months
AutoQA 0.8.5 Released
by Tim Flink
The AutoQA developers are proud to announce the release of AutoQA 0.8.5
today. This is a maintenance release with the following changes:
- Improved clarity in upgradepath output (#445)
- Updated repository configuration for F20 release
The new version has been deployed to our staging environment and will
be moved to production later this week if no issues manifest.
Thanks,
Tim
10 years, 3 months
Review Request 59: Show number of blockers/FEs in titles in the blocker list
by Martin Krizek
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
http://reviewboard-tflink.rhcloud.com/r/59/
-----------------------------------------------------------
Review request for blockerbugs.
Repository: blockerbugs
Description
-------
kparal had an idea of displaying number of blockers/FEs in titles in the blocker list, this is what I came up with.
commit d96ed8d6b5c196f9750cf5e062a6fc958e35821c
Author: Martin Krizek <mkrizek(a)redhat.com>
Date: Mon Dec 16 14:31:22 2013 +0100
Show number of blockers/FEs in titles in the blocker list.
With this patch, titles now look like e.g. these:
1 Proposed Blocker
No Accepted Blockers
2 Accepted Freeze Exceptions
Diffs
-----
blockerbugs/templates/blocker_list.html ea79d9ba852a5147a362cd904f853c77bd03c54a
Diff: http://reviewboard-tflink.rhcloud.com/r/59/diff/
Testing
-------
Testing done on my dev machine.
Thanks,
Martin Krizek
10 years, 3 months
Review Request 57: Multiple builds fixing a bug show confusing status label
by Martin Krizek
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
http://reviewboard-tflink.rhcloud.com/r/57/
-----------------------------------------------------------
Review request for blockerbugs.
Bugs: 438
https://fedorahosted.org/fedora-qa/ticket/438
Repository: blockerbugs
Description
-------
commit 911781af9cc06e27c0a8580f07f7673c90e7329d
Author: Martin Krizek <mkrizek(a)redhat.com>
Date: Tue Dec 10 16:28:52 2013 +0100
Sort updates by (status.desc(), pending.desc())
This way an update label is correctly set when multiple updates fix a
bug. The label is chosen by the following order (the lowest one):
pending testing < testing < pending stable < stable
Fixes: #438
Note: the rest of the issues with displaying label is handled outside this ticket in https://phab.qadevel.cloud.fedoraproject.org/T26
Diffs
-----
blockerbugs/models/update.py 89c083da5c91558d4dead118c67e4a1138b8cae1
blockerbugs/controllers/main.py 1795ed1d717bb85e0f3d9e7e7008d68c2aae36d8
blockerbugs/__init__.py dcf6c5aadb24e6d86e95d5bb3d608b81721de47f
Diff: http://reviewboard-tflink.rhcloud.com/r/57/diff/
Testing
-------
Sorting seems to be working as expected.
Thanks,
Martin Krizek
10 years, 3 months
[Fedora QA] #438: Multiple builds fixing a bug show confusing status label
by fedora-badges
#438: Multiple builds fixing a bug show confusing status label
--------------------------------------+---------------------
Reporter: kparal | Owner: tflink
Type: defect | Status: new
Priority: minor | Milestone:
Component: Blocker bug tracker page | Version:
Keywords: | Blocked By:
Blocking: |
--------------------------------------+---------------------
See the screenshot. There are two updates that claim to fix a single bug
(that is correct, both of them are needed). One is stable, one is in
testing. The BBA shows [stable] label. That is confusing, that seems to
indicate that everything needed is in stable. (One might happen to visit
that bug and close it, without inspecting it closer).
I think a better choice here is to show the "worst" status in the label.
Therefore:
{{{
update X: stable
update Y: testing
-> label: [testing]
update X: stable
update Y: stable
-> label: [stable]
update X: pending testing
update Y: testing
-> label: [pending testing]
update X: pending stable
update Y: testing
-> label: [testing]
update X: stable
update Y: pending stable
-> label: [pending stable]
}}}
So, if you have an ordered array ['pending testing', 'testing', 'pending
stable', 'stable'], you pick the lowest index available in update XYZ
statuses and show that as the label.
What do you think?
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/438>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
10 years, 3 months
[Maniphest] [Created] T27: Irrelevant "phantom" updates are not purged from active update list
by tflink (Tim Flink)
tflink created this task.
tflink added a subscriber: tflink.
tflink added a project: blockerbugs
TASK DESCRIPTION
Currently, there are two anaconda updates displayed in the blocker tracking app. One is current, one is a phantom update that no longer exists in bodhi.
The phantom update appears to have come from the fact that updates don't get UIDs before being pushed to updates-testing. This particular update was modified after the blocker tracking app picked it up but before the update was pushed to updates-testing. This means that the title changed before we could get the UID and we detected two different updates - one valid and one invalid.
Regardless of the method by which the "phantom" updates are showing up, the update sync algorithm should be removing any phantom or invalid updates from the list.
TASK DETAIL
https://phab.qadevel.cloud.fedoraproject.org/T27
To: tflink
Cc: qa-devel, tflink
10 years, 3 months