qa-devel November 2013

qa-devel@lists.fedoraproject.org

8 participants
47 discussions

[Fedora QA] #416: irc list sort order doesn't match html buglist
by fedora-badges 09 Dec '13

09 Dec '13

#416: irc list sort order doesn't match html buglist --------------------------------------+------------------------ Reporter: tflink | Owner: tflink Type: defect | Status: new Priority: major | Milestone: Fedora 20 Component: Blocker bug tracker page | Version: Keywords: | Blocked By: Blocking: | --------------------------------------+------------------------ = bug description = The sort order of the bugs displayed on the html buglist (milestone/XX/YY/buglist) doesn't match the sort order used when generating the irc list for meetbot. This causes some confusion and annoyance when the order of bugs discussed in the meeting is not what appears in the list that participants are looking at = fix recommendation = Make the sort order consistent as component,bzid for both lists -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/416> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 6

[AutoQA] #445: upgradepath is failing rawhide builds due to no rawhide-pending
by fedora-badges 09 Dec '13

09 Dec '13

#445: upgradepath is failing rawhide builds due to no rawhide-pending ---------------------+------------------------ Reporter: tflink | Owner: Type: defect | Status: new Priority: major | Milestone: Hot issues Component: tests | Keywords: Blocked By: | Blocking: ---------------------+------------------------ == Description == There are several examples where upgradepath is failing builds if rawhide isn't a newer version (not including release) compared to branched or the active releases. This is leaving failure messages in bodhi and is leaving false negatives in bodhi and needs to be fixed. == Examples of Failure == * http://autoqa.fedoraproject.org/results/681687-autotest/virt04.qa/upgradepa… /resource-agents-3.9..html#2 * http://autoqa.fedoraproject.org/results/681759-autotest/virt10.qa/upgradepa… -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/445> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 9

[Fedora QA] #431: Enable HTTPS for beaker.fp.o
by fedora-badges 03 Dec '13

03 Dec '13

#431: Enable HTTPS for beaker.fp.o --------------------------------------+--------------------- Reporter: atodorov | Owner: tflink Type: defect | Status: new Priority: major | Milestone: Component: Blocker bug tracker page | Version: Keywords: | Blocked By: Blocking: | --------------------------------------+--------------------- Please enable HTTPS for beaker.fp.o. Can be self-signed or a wildcard *.fp.o certificate if there is one. -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/431> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 2

[Fedora QA] #387: Updates pending stable show as stable
by fedora-badges 02 Dec '13

02 Dec '13

#387: Updates pending stable show as stable --------------------------------------+--------------------- Reporter: kparal | Owner: tflink Type: defect | Status: new Priority: minor | Milestone: Component: Blocker bug tracker page | Version: Keywords: | Blocked By: Blocking: | --------------------------------------+--------------------- A package that is in updates-testing and is pending stable is shown as [stable] in the app. That can cause some confusion (i.e. one of us can close a related bug by assuming the package is already stable, and the package push can be cancelled afterwards). I think the app should display the repository the package is currently in, not the repository the package in pending to. What do you think? -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/387> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 4

Locking Down Access to Beaker
by Tim Flink 01 Dec '13

01 Dec '13

After a conversation with infra, we decided to lock down access to beaker.fedoraproject.org by IP address until we have a more secure solution for logins [1]. I've changed the server configuration so that access to beaker is only allowed from certain IPs. I think that most current users should be included in this list but if you're seeing 403s and think you should have access to beaker.fedoraproject.org, please let me know. Sorry for the inconvenience, we hope to have an alternate access method soon. Tim [1]https://lists.fedorahosted.org/pipermail/beaker-devel/2013-November/00088…

2 1

[Fedora QA] #439: IRC bug order does not match web bug order
by fedora-badges 27 Nov '13

27 Nov '13

#439: IRC bug order does not match web bug order --------------------------------------+--------------------- Reporter: kparal | Owner: tflink Type: defect | Status: new Priority: minor | Milestone: Component: Blocker bug tracker page | Version: Keywords: | Blocked By: Blocking: | --------------------------------------+--------------------- Look at those two screenshots. Captured at the same time, yet the third and the fourth bug position is swapped between web ui and IRC script. Ideally the ordering should be the same. Thanks. -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/439> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 1

[Maniphest] [Changed CC] T12: Create comprehensive functional tests for package level checks
by tflink (Tim Flink) 27 Nov '13

27 Nov '13

jdulaney added a subscriber: jdulaney. TASK DETAIL https://phab.qadevel.cloud.fedoraproject.org/T12 To: jdulaney Cc: qa-devel, tflink, jdulaney

1 0

[Maniphest] [Created] T23: login with flask_fas_openid fails with "Strange state: failure"
by tflink (Tim Flink) 26 Nov '13

26 Nov '13

tflink created this task. tflink claimed this task. tflink added a subscriber: tflink. tflink added a project: blockerbugs TASK DESCRIPTION When logging in, some users are redirected to FAS-OpenID, complete the auth process only to be met with fails with "Strange state: failure" TASK DETAIL https://phab.qadevel.cloud.fedoraproject.org/T23 To: tflink Cc: qa-devel, tflink

1 1

Seeking a candidate for the Server Working Group
by Stephen Gallagher 26 Nov '13

26 Nov '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Server Working Group is a team focused on the development of a server-OS built from the Fedora Project. Recently, the chair held by Jóhann B. Guðmundsson was vacated. At today's Working Group meeting[1], we agreed that we would like to approach Fedora QA first for someone to fill this chair. If you feel that you are able and willing to represent the interests of Fedora QA in the Server Working Group, please respond and we will consider you. Thank you very much in advance. [1] http://meetbot.fedoraproject.org/fedora-meeting-1/2013-11-26/fedora-meeting… -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.15 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlKU5CUACgkQeiVVYja6o6OYsQCfbevd04RHvco2HBbY4ZsX81d0 zE8AnjAnAF4QjhkqyucHt7gFZ2Iq3wGZ =LKJv -----END PGP SIGNATURE-----

2 1

Re: [Fedora QA] #359: Create Ansible Playbooks for Deployment and Updating
by fedora-badges 26 Nov '13

26 Nov '13

#359: Create Ansible Playbooks for Deployment and Updating ---------------------------------------+--------------------------------- Reporter: tflink | Owner: tflink Type: enhancement | Status: closed Priority: major | Milestone: Undetermined Future Component: Blocker bug tracker page | Version: Resolution: fixed | Keywords: Blocked By: | Blocking: ---------------------------------------+--------------------------------- Changes (by mkrizek): * status: new => closed * resolution: => fixed Comment: tflink has done this. Closing. -- Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/359#comment:2> Fedora QA <http://fedorahosted.org/fedora-qa> Fedora Quality Assurance

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

qa-devel November 2013