qa-devel March 2013

qa-devel@lists.fedoraproject.org

5 participants
42 discussions

[Fedora QA] #367: Display flash messages in appropriate place
by fedora-badges 03 Jul '13

03 Jul '13

#367: Display flash messages in appropriate place --------------------------------------+---------------------------------- Reporter: mkrizek | Owner: tflink Type: enhancement | Status: new Priority: minor | Milestone: Undetermined Future Component: Blocker bug tracker page | Version: Keywords: | Blocked By: Blocking: | --------------------------------------+---------------------------------- = problem = Currently flash messages containing information for user are not displayed. = analysis = There should probably be a box right under the header on all pages that would display flash messages. = enhancement recommendation = -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/367> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 2

[Fedora QA] #372: Bugzilla Faults During Proposal are not logged, lead to http 500 errors
by fedora-badges 25 Jun '13

25 Jun '13

#372: Bugzilla Faults During Proposal are not logged, lead to http 500 errors --------------------------------------+------------------------ Reporter: tflink | Owner: tflink Type: defect | Status: new Priority: critical | Milestone: Fedora 19 Component: Blocker bug tracker page | Version: Keywords: | Blocked By: Blocking: | --------------------------------------+------------------------ = bug description = When bugzilla faults during proposal don't have fault code 51, the internal !BugzillaError class isn't used and the fault is lost when attempting to extract information from it {{{ [Wed Mar 27 13:26:38 2013] [error] [20130327-13:26PM] [blockerbugs] [ERROR] Exception on /propose_bug [POST] [Wed Mar 27 13:26:38 2013] [error] Traceback (most recent call last): [Wed Mar 27 13:26:38 2013] [error] File "/usr/lib/python2.6/site- packages/flask/app.py", line 1687, in wsgi_app [Wed Mar 27 13:26:38 2013] [error] response = self.full_dispatch_request() [Wed Mar 27 13:26:38 2013] [error] File "/usr/lib/python2.6/site- packages/flask/app.py", line 1360, in full_dispatch_request [Wed Mar 27 13:26:38 2013] [error] rv = self.handle_user_exception(e) [Wed Mar 27 13:26:38 2013] [error] File "/usr/lib/python2.6/site- packages/flask/app.py", line 1358, in full_dispatch_request [Wed Mar 27 13:26:38 2013] [error] rv = self.dispatch_request() [Wed Mar 27 13:26:38 2013] [error] File "/usr/lib/python2.6/site- packages/flask/app.py", line 1344, in dispatch_request [Wed Mar 27 13:26:38 2013] [error] return self.view_functions[rule.endpoint](**req.view_args) [Wed Mar 27 13:26:38 2013] [error] File "/usr/lib/python2.6/site- packages/blockerbugs/controllers/users.py", line 84, in decorated_function [Wed Mar 27 13:26:38 2013] [error] return f(*args, **kwargs) [Wed Mar 27 13:26:38 2013] [error] File "/usr/lib/python2.6/site- packages/blockerbugs/controllers/main.py", line 375, in propose_bug [Wed Mar 27 13:26:38 2013] [error] bugform.bugid.errors = [e.msg] [Wed Mar 27 13:26:38 2013] [error] AttributeError: 'Fault' object has no attribute 'msg' }}} = fix recommendation = Either all of the bugzilla faults need to be wrapped in a !BugzillaError or the error handling needs to be capable of handling multiple error types. -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/372> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 1

[Fedora QA] #370: Change active milestone list on index to clickable links
by fedora-badges 01 May '13

01 May '13

#370: Change active milestone list on index to clickable links --------------------------------------+---------------------------------- Reporter: tflink | Owner: tflink Type: enhancement | Status: new Priority: minor | Milestone: Undetermined Future Component: Blocker bug tracker page | Version: Keywords: easyfix | Blocked By: Blocking: | --------------------------------------+---------------------------------- = problem = Currently, the milestones listed as current on the index are not links. It would be nice if they linked to the milestone's buglist = enhancement recommendation = Change the index template such that the list of currently active milestones also links to the named milestone's buglist -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/370> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 1

[Fedora QA] #369: Logo in Upper Left Corner Should be a Link to Main Index
by fedora-badges 30 Apr '13

30 Apr '13

#369: Logo in Upper Left Corner Should be a Link to Main Index --------------------------------------+---------------------------------- Reporter: tflink | Owner: tflink Type: enhancement | Status: new Priority: minor | Milestone: Undetermined Future Component: Blocker bug tracker page | Version: Keywords: easyfix | Blocked By: Blocking: | --------------------------------------+---------------------------------- = problem = Many websites have the logo in the upper left hand corner as a link to the index. The blocker tracking app does not. = enhancement recommendation = Modify the base template such that the logo is a clickable link going to the main index -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/369> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 1

Review Request 18: Add cgit link to Main Page
by Martin Krizek 23 Apr '13

23 Apr '13

----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: http://reviewboard-tflink.rhcloud.com/r/18/ ----------------------------------------------------------- Review request for blockerbugs. Bugs: 343 https://fedorahosted.org/fedora-qa/ticket/343 Repository: blockerbugs Description ------- This is maybe trivial to have a review for but two things might be discussed: 1. do we want to show the link just on index or on all pages? 2. is the wording of the link ok? Diffs ----- sass/app.scss 1a4369d0911b77fc411089de0b05c8d5c80e304f blockerbugs/templates/index.html 088962bfcb16c3f0d163366f2235fc557e0d45dc Diff: http://reviewboard-tflink.rhcloud.com/r/18/diff/ Testing ------- Thanks, Martin Krizek

1 5

[Fedora QA] #373: Remove Mockup Warning from proposal thank you page
by fedora-badges 22 Apr '13

22 Apr '13

#373: Remove Mockup Warning from proposal thank you page --------------------------------------+------------------------ Reporter: tflink | Owner: tflink Type: defect | Status: new Priority: major | Milestone: Fedora 19 Component: Blocker bug tracker page | Version: Keywords: | Blocked By: Blocking: | --------------------------------------+------------------------ = bug description = The 'thank you' page after blocker proposal still contains a warning about being a mockup. = fix recommendation = Remove the warning from that template page; it shouldn't be there any more. -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/373> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 1

[Fedora QA] #374: Rework Logging Mechanisms
by fedora-badges 19 Apr '13

19 Apr '13

#374: Rework Logging Mechanisms --------------------------------------+------------------------ Reporter: tflink | Owner: tflink Type: enhancement | Status: new Priority: major | Milestone: Fedora 19 Component: Blocker bug tracker page | Version: Keywords: | Blocked By: Blocking: | --------------------------------------+------------------------ = problem = The logs for both the blocker tracking app and the sync operation are limited to stdout only instead of being separated out into a file. = analysis = The biggest problem here is recording what happens with sync - we used to deal with it by piping the output into a file but with the shift to RPM packaging and hosting in fedora infra, this is no longer an option. The log messages during normal app use go to httpd's error_log but that isn't as big of a problem. This bug will serve as a tracker bug for all the functionality which needs to be done in order to properly log output from sync and the blocker tracking app. -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/374> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 3

[Fedora QA] #377: Add log location to spec
by fedora-badges 19 Apr '13

19 Apr '13

#377: Add log location to spec --------------------------------------+------------------------ Reporter: tflink | Owner: tflink Type: enhancement | Status: new Priority: major | Milestone: Fedora 19 Component: Blocker bug tracker page | Version: Keywords: | Blocked By: Blocking: 374 | --------------------------------------+------------------------ = problem = Once logging has been implemented for sync and the blocker tracking application, that location will need to be created at install time for production systems. = enhancement recommendation = The spec file currently has no concept of the logging location - once the production location has been determined, create that dir in the spec and claim ownership of it. -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/377> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 2

[Fedora QA] #376: Change logging config for app
by fedora-badges 19 Apr '13

19 Apr '13

#376: Change logging config for app --------------------------------------+--------------------- Reporter: tflink | Owner: tflink Type: enhancement | Status: new Priority: minor | Milestone: Component: Blocker bug tracker page | Version: Keywords: | Blocked By: Blocking: 374 | --------------------------------------+--------------------- = problem = The error messages from the app are only sent to stdout instead of being directed to a log file. While this isn't a huge problem (everything will be caught by httpd's error_log), it is not the best solution. = enhancement recommendation = change the logging setup so that the location is configurable (stdout, file) and that both file and stdout could be used at the same time. -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/376> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 3

[Fedora QA] #375: Change logging config for sync
by fedora-badges 19 Apr '13

19 Apr '13

#375: Change logging config for sync --------------------------------------+------------------------ Reporter: tflink | Owner: tflink Type: enhancement | Status: new Priority: major | Milestone: Fedora 19 Component: Blocker bug tracker page | Version: Keywords: | Blocked By: Blocking: 374 | --------------------------------------+------------------------ = problem = The sync process uses a different logging instance than the blocker tracking app and is currently configured to just output to stdout instead of logging to a file. = enhancement recommendation = The sync should log to a file while in production but shouldn't force logging to a static location. The log location should be configurable (stdout, specific file) and it should be separable from app logging. -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/375> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

qa-devel March 2013