[AutoQA] #149: rpmlint: Provide whitelisting of messages
by fedora-badges
#149: rpmlint: Provide whitelisting of messages
--------------------+-------------------------------------------------------
Reporter: kparal | Owner:
Type: task | Status: new
Priority: major | Milestone: Package update tests
Component: tests | Version: 1.0
Keywords: |
--------------------+-------------------------------------------------------
We need to provide some whitelisting capability of rpmlint packages, so
the package maintainers can mark some messages as invalid. We will also
probably want to mark some messages as invalid by default for the whole
Fedora project.
As an interesting inspiration, look at lintian project (validation of deb
packages). It provides some "overrides" on a package basis, you just
create a definition file in /etc/lintian/package_name or kind of. I have
the feeling that rpmlint provides something similar, but we need to
discover it more properly.
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/149>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
12 years, 9 months
[AutoQA] #104: virtguest.py: accept iso image(s) as install location
by fedora-badges
#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
12 years, 9 months
[AutoQA] #183: Write a script and a daemon to send signals between virt machine and host
by fedora-badges
#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
12 years, 9 months
[AutoQA] #208: update minimon to transport logs between guest and host via virtio
by fedora-badges
#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
12 years, 11 months
[AutoQA] #238: Move ResultsDB to Turbogears2 application
by fedora-badges
#238: Move ResultsDB to Turbogears2 application
----------------------------+-----------------------------------------------
Reporter: jskladan | Owner: jskladan
Type: task | Status: new
Priority: major | Milestone: Resultdb
Component: infrastructure | Keywords:
----------------------------+-----------------------------------------------
Because the current implementation has noticeable disadvantages (speed,
database management, ...), I'd like to rewrite the resultsdb backend using
TG2.
This will also provide a json-rpc, added to the xml-rpc interface.
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/238>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
13 years
[AutoQA] #230: upgradepath: current implementation is broken when pushing older packages
by fedora-badges
#230: upgradepath: current implementation is broken when pushing older packages
--------------------+-------------------------------------------------------
Reporter: kparal | Owner:
Type: defect | Status: new
Priority: major | Milestone: Package Update Acceptance Test Plan
Component: tests | Version: 1.0
Keywords: |
--------------------+-------------------------------------------------------
Currently upgradepath takes into account only the given NVR and compares
it with other repositories. This approach works, except for one use case -
when you want to push an older package version into the repository.
Technically you can have multiple package versions in a single repository.
Yum prefers the most recent one, but you can have more of them there. It's
hard to imagine a use case where you want to push an older version, but
let's say for example an older kernel that is needed for hardware
compatibility reasons. In this case, our current upgradepath fails - it
supposes the given NVR is always the latest.
We need to modify upgradepath in such a way, that is supposes that given
NVR has been pushed into the repository and then traverses all
repositories from bottom up and checks for upgradepath constraint
everywhere - including the repo you pushed into, including all package
versions which might be there.
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/230>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
13 years
[AutoQA] #214: conflicts: fails with parent repositories
by fedora-badges
#214: conflicts: fails with parent repositories
--------------------+-------------------------------------------------------
Reporter: kparal | Owner:
Type: defect | Status: new
Priority: major | Milestone: Hot issues
Component: tests | Version: 1.0
Keywords: |
--------------------+-------------------------------------------------------
These two commands work (although the package counts are somewhat weirdly
same):
{{{
# repoclosure --tempcache --newest
--repofrompath=target,http://download.fedoraproject.org/pub/fedora/linux/releases/13/Everything/x86_64/os
--repoid=target
Added target repo from
/root/http:/download.fedoraproject.org/pub/fedora/linux/releases/13/Everything/x86_64/os
Reading in repository metadata - please wait....
Checking Dependencies
/usr/lib/python2.6/site-packages/yum/packages.py:401: UnicodeWarning:
Unicode equal comparison failed to convert both arguments to Unicode -
interpreting them as being unequal
if prcotuple in self.prco[prcotype]:
Repos looked at: 1
target
Num Packages in Repos: 20806
}}}
{{{
# repoclosure --tempcache --newest
--repofrompath=target,http://download.fedoraproject.org/pub/fedora/linux/updates/13/x86_64
--repoid=target
Added target repo from
/root/http:/download.fedoraproject.org/pub/fedora/linux/updates/13/x86_64
Reading in repository metadata - please wait....
Checking Dependencies
/usr/lib/python2.6/site-packages/yum/packages.py:401: UnicodeWarning:
Unicode equal comparison failed to convert both arguments to Unicode -
interpreting them as being unequal
if prcotuple in self.prco[prcotype]:
Repos looked at: 1
target
Num Packages in Repos: 20806
}}}
But if you combine it:
{{{
# repoclosure --tempcache --newest
--repofrompath=target,http://download.fedoraproject.org/pub/fedora/linux/updates/13/x86_64
--repoid=target
--repofrompath=parent1,http://download.fedoraproject.org/pub/fedora/linux/releases/13/Everything/x86_64/os
--repoid=parent1
Added target repo from
/root/http:/download.fedoraproject.org/pub/fedora/linux/updates/13/x86_64
Added parent1 repo from
/root/http:/download.fedoraproject.org/pub/fedora/linux/releases/13/Everything/x86_64/os
Reading in repository metadata - please wait....
Cannot retrieve repository metadata (repomd.xml) for repository: parent1.
Please verify its path and try again
Some dependencies may not be complete for this repository
Run as root to get all dependencies or use -t to enable a user temp cache
Checking Dependencies
Cannot retrieve repository metadata (repomd.xml) for repository: parent1.
Please verify its path and try again
}}}
Something is broken here.
{{{
yum-utils-1.1.28-1.fc13.noarch
yum-metadata-parser-1.1.4-1.fc13.x86_64
yum-3.2.27-4.fc13.noarch
}}}
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/214>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
13 years
[AutoQA] #212: fix check_opt_in to not use collection_name
by fedora-badges
#212: fix check_opt_in to not use collection_name
-----------------------+----------------------------------------------------
Reporter: wwoods | Owner:
Type: task | Status: new
Priority: minor | Milestone:
Component: docs/wiki | Version: 1.0
Keywords: |
-----------------------+----------------------------------------------------
collection_name was used to line up with the dist-cvs branch layout; now
that we have switched to dist-git/fedpkg the branch names match the repo
names used in repoinfo, so we have no need for collection_name.
This will require modifying the existing autoqa-optin file structure to
match the git layout. We can leave symlinks for the old ('F-14') distro
names but use the new ones ('f14') as the canonical ones.
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/212>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
13 years, 1 month