May 2011 - autoqa-devel - Fedora Mailing-Lists

Decreasing Bodhi Comment Emails From AutoQA

by Tim Flink

Since this has almost nothing to do with the log output of depcheck upgradepath, I'm splitting this conversation off into another thread. As Kamil pointed out, my initial proposal was naive and needs more thought before implementing anything. We will soon have the ability to disable emails for comments in Bodhi and we need to figure out how to best make use of that ability. Lots of questions here, I'll save my thoughts for replying to myself. Tim How would we deal with tests that change state between PASS and FAIL? - Either 'PASS -> FAIL' or 'FAIL -> PASS' What emails do we want to get rid of? - Just certain 'PASS' messages? - All results messages? How do we expect maintainers to learn of AutoQA results if we turn off email notifications? Can we do this in a way such that it is configurable by maintainer? - If so, should we attempt this? - What is the benefit? How big is it? Can we just send a single email after all tests have passed? - Again, if so, should we? Is there another approach that would be better?

12 years, 11 months

3
10
0 / 0

Fwd: rawhide report: 20110511 changes

by Kamil Paral

> ----- Forwarded Message ----- > From: "Rawhide Report" <rawhide(a)fedoraproject.org> > To: devel(a)lists.fedoraproject.org, test(a)lists.fedoraproject.org > Sent: Wednesday, May 11, 2011 11:26:07 AM > Subject: rawhide report: 20110511 changes > > > sdcv-0.4.2-6.fc16 > ----------------- > * Wed May 11 2011 Pavel Zhukov <landgraf(a)fedoraproject.org> - 0.4.2-6 > - Increment release number to become AutoQA happy Just spotted this one ↑. In the end, AutoQA really serves sometimes to its purpose. I'm happy :-) https://admin.fedoraproject.org/updates/sdcv-0.4.2-6.fc15

12 years, 11 months

2
1
0 / 0

[AutoQA] #324: depcheck: subpackage conflicts are not handled properly

by fedora-badges

#324: depcheck: subpackage conflicts are not handled properly --------------------+------------------------------------------------------- Reporter: kparal | Owner: Type: defect | Status: new Priority: major | Milestone: Hot issues Component: tests | Keywords: --------------------+------------------------------------------------------- sharkcz contacted me about his zabbix update: https://admin.fedoraproject.org/updates/zabbix-1.8.5-1.fc14 It has failed depcheck because (AFAIU) depcheck tries to install all subpackages of zabbix. But zabbix-server-mysql, zabbix-server-pgsql and zabbix-server-sqlite3 conflicts with each other. That makes depcheck reject the whole update. Log attached. We need to modify depcheck for these use cases. Interesting is that the same update passed for F15: https://admin.fedoraproject.org/updates/zabbix-1.8.5-1.fc15 But the logs are no longer available. Where's the difference? sharkcz is CCed, he may provide additional information if required. -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/324> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

12 years, 11 months

1
1
0 / 0

Re: [AutoQA] #317: Create user-facing documentation for upgradepath

by fedora-badges

#317: Create user-facing documentation for upgradepath ---------------------------+------------------------------------------------ Reporter: kparal | Owner: kparal Type: task | Status: closed Priority: major | Milestone: 0.5.0 Component: documentation | Resolution: fixed Keywords: | ---------------------------+------------------------------------------------ Changes (by kparal): * status: new => closed * resolution: => fixed Comment: I think upgradepath documentation is done. Of course if we come upon some further problems, we will amend the wiki page. Similarly when test output changes. -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/317#comment:4> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

12 years, 11 months

1
0
0 / 0

[PATCH] koji_utils: allow package download caching

by Kamil Paral

Please review: https://fedorahosted.org/reviewboard/r/143/

12 years, 11 months

2
3
0 / 0

Re: [AutoQA] #316: depcheck: extract possible cause of failure

by fedora-badges

#316: depcheck: extract possible cause of failure -------------------------+-------------------------------------------------- Reporter: kparal | Owner: jskladan Type: enhancement | Status: assigned Priority: major | Milestone: 0.5.0 Component: tests | Resolution: Keywords: | -------------------------+-------------------------------------------------- Changes (by jskladan): * status: new => assigned -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/316#comment:2> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

12 years, 11 months

1
0
0 / 0

Re: [AutoQA] #316: depcheck: extract possible cause of failure

by fedora-badges

#316: depcheck: extract possible cause of failure -------------------------+-------------------------------------------------- Reporter: kparal | Owner: jskladan Type: enhancement | Status: new Priority: major | Milestone: 0.5.0 Component: tests | Resolution: Keywords: | -------------------------+-------------------------------------------------- Changes (by kparal): * owner: => jskladan -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/316#comment:1> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

12 years, 11 months

1
0
0 / 0

Re: [AutoQA] #318: Provide access to test documentation

by fedora-badges

#318: Provide access to test documentation -------------------------+-------------------------------------------------- Reporter: kparal | Owner: kparal Type: enhancement | Status: assigned Priority: major | Milestone: 0.5.0 Component: core | Resolution: Keywords: | -------------------------+-------------------------------------------------- Comment (by kparal): This is the Luke's response: {{{ Right now bodhi does not allow arbitrary HTML in comments. There is some hardcoded logic in our Comment model that automatically links up http addresses, along with bug numbers. https://fedorahosted.org/bodhi/browser/bodhi/model.py#L1196 This could probably be extended to link up AutoQA results. If you want to see this happen, please file a ticket with some details. }}} I think we will probably just provide documentation link inside the pretty log for now. -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/318#comment:2> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

12 years, 11 months

1
0
0 / 0

Re: [AutoQA] #317: Create user-facing documentation for upgradepath

by fedora-badges

#317: Create user-facing documentation for upgradepath ---------------------------+------------------------------------------------ Reporter: kparal | Owner: kparal Type: task | Status: new Priority: major | Milestone: 0.5.0 Component: documentation | Resolution: Keywords: | ---------------------------+------------------------------------------------ Old description: > Create a wiki page upgradepath that contains the following: > * Thorough description of the test > * How to read and interpret the results > * How to interpret the log output and use it to find failures > * Description of common failures > * Links to useful resources > * correct procedure descriptions (e.g. packaging guidelines, etc). > * Other relevant information > > {{{ > #!comment > For some reason, I can't get a ticket query with single result to render, > changed to static > }}} > > Related to #326 - Create user-facing documentation for depcheck New description: Create a wiki page for upgradepath that contains the following: * Thorough description of the test * How to read and interpret the results * How to interpret the log output and use it to find failures * Description of common failures * Links to useful resources * correct procedure descriptions (e.g. packaging guidelines, etc). * Other relevant information {{{ #!comment For some reason, I can't get a ticket query with single result to render, changed to static }}} Related to #326 - Create user-facing documentation for depcheck Comment (by tflink): prepositions are so overrated ... -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/317#comment:3> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

12 years, 11 months

1
0
0 / 0

Re: [AutoQA] #317: Create user-facing documentation for upgradepath

by fedora-badges

#317: Create user-facing documentation for upgradepath ---------------------------+------------------------------------------------ Reporter: kparal | Owner: kparal Type: task | Status: new Priority: major | Milestone: 0.5.0 Component: documentation | Resolution: Keywords: | ---------------------------+------------------------------------------------ Changes (by tflink): * owner: => kparal * summary: Document depcheck and upgradepath => Create user-facing documentation for upgradepath Old description: > Create a wiki page for depcheck and upgradepath with thorough description > of the test, how to interpret the results, how to find the cause of the > failure in the log, the explanation for most common failures, links to > resources with correct procedure descriptions (e.g. packaging guidelines, > etc). New description: Create a wiki page upgradepath that contains the following: * Thorough description of the test * How to read and interpret the results * How to interpret the log output and use it to find failures * Description of common failures * Links to useful resources * correct procedure descriptions (e.g. packaging guidelines, etc). * Other relevant information {{{ #!comment For some reason, I can't get a ticket query with single result to render, changed to static }}} Related to #326 - Create user-facing documentation for depcheck Comment: Split ticket up into 2: one for depcheck, one for upgradepath. -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/317#comment:2> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

12 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

autoqa-devel May 2011