#104: virtguest.py: accept iso image(s) as install location
--------------------+-------------------------------------------------------
Reporter: wwoods | Owner:
Type: task | Status: new
Priority: major | Milestone: Automate installation test plan
Component: tests | Version: 1.0
Keywords: |
--------------------+-------------------------------------------------------
allow {{{VirtGuest.create()}}} to use an iso image (or images) for its
{{{location}}} arg, and automatically choose the appropriate {{{--location
URL}}} or {{{--cdrom IMAGE}}} flag.
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/104>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
#183: Write a script and a daemon to send signals between virt machine and host
----------------------------+-----------------------------------------------
Reporter: kparal | Owner:
Type: task | Status: new
Priority: major | Milestone: Virtualization
Component: infrastructure | Version: 1.0
Keywords: |
----------------------------+-----------------------------------------------
We need to exchange some signals between virt machine and a host. For
example "autotest job finished, need to revert to previous state". We need
to write simple script that will send this signal for virt machine and a
daemon that will receive this signal in the host machine and act
accordingly.
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/183>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
#208: update minimon to transport logs between guest and host via virtio
-------------------+--------------------------------------------------------
Reporter: liam | Owner:
Type: task | Status: new
Priority: major | Milestone: Automate installation test plan
Component: tests | Version: 1.0
Keywords: |
-------------------+--------------------------------------------------------
Since minimon has to use network during test, some test cases will not
activate network during test,in this case, minimon can not transport logs
to host, test also be identified fail even it was successfully run.
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/208>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
#205: make depcheck submit karma/comments to bodhi
--------------------+-------------------------------------------------------
Reporter: wwoods | Owner:
Type: task | Status: new
Priority: major | Milestone: Package Update Acceptance Test Plan - depcheck
Component: tests | Version: 1.0
Keywords: |
--------------------+-------------------------------------------------------
Modify the depcheck test so that it sends status info - karma, comments,
whatever - to bodhi.
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/205>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
#201: Add mash support to depcheck
-----------------------+----------------------------------------------------
Reporter: wwoods | Owner:
Type: task | Status: new
Priority: major | Milestone: Package Update Acceptance Test Plan - depcheck
Component: docs/wiki | Version: 1.0
Keywords: |
-----------------------+----------------------------------------------------
To properly handle possible multilib problems (e.g. the
[https://fedorahosted.org/pipermail/autoqa-devel/2010-June/000703.html
nss-softokn problem] in June and the recent gfortran problem) we need to
run mash on the set of proposed packages, to generate a proper
multilibified repo to test against.
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/201>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
#153: rpmguard: Separate checks into individual python files
-------------------------+--------------------------------------------------
Reporter: kparal | Owner:
Type: enhancement | Status: new
Priority: major | Milestone:
Component: tests | Version: 1.0
Keywords: rpmguard |
-------------------------+--------------------------------------------------
It would be great to have individual checks in rpmguard available as
separate files, very similarly to what rpmlint or yum (-plugins) use. It
would allow easy enabling/disabling of specific check, it would allow easy
contribution of a new check.
More ideas and information here: https://fedorahosted.org/pipermail
/autoqa-devel/2010-May/000496.html
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/153>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
#150: "artificial ignorance": suppress errors and warnings that aren't important
-------------------------+--------------------------------------------------
Reporter: dmalcolm | Owner:
Type: enhancement | Status: new
Priority: major | Milestone: Package Sanity Tests
Component: tests | Version: 1.0
Keywords: |
-------------------------+--------------------------------------------------
There are some interesting ideas in here about suppressing a logfile to
show up the information that's truly important:
http://www.ranum.com/security/computer_security/papers/ai/index.html
I think that the rpmlint test needs to have a set of filters, and should
suppress output matching certain patterns. For example
https://fedorahosted.org/pipermail/autoqa-results/2010-April/013903.html
shows:
{{{
gnome-python2-gnome.i686: W: spelling-error Summary(en_US) libgnome -> lib
gnome, lib-gnome, cognomen
}}}
i.e. it's complaining about a reference to "libgnome" within gnome-
python2-gnome, which is clearly a false-positive.
For this case we might have a python filtering process that says something
like this (caveat: untested):
{{{
patterns = [
": W: spelling-error \S+ libgnome .*",
]
def should_ignore(line):
for pat in patterns
# May want to precompile the patterns:
m = re.match(pat, line)
if m:
return True
# No match:
return False
for line in rpmlint_output
if not should_ignore(line):
print(line)
}}}
and then gradually grow patterns. The idea is to make it nice and
lightweight, and Fedora QA can then easily take ownership of the
suppresssions, without having to get patches into rpmlint.
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/150>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project