[AutoQA] #258: implement 'make test'
by fedora-badges
#258: implement 'make test'
-------------------------+--------------------------------------------------
Reporter: kparal | Owner:
Type: enhancement | Status: new
Priority: major | Milestone: 0.5.0
Component: core | Keywords:
-------------------------+--------------------------------------------------
Some of our modules have unit tests. Let's execute them all by "make test"
command and report the result. We can use this functionality to
periodically check whether nothing got broken.
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/258>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
12 years, 10 months
[AutoQA] #271: Create autotestd systemd.service file for F15 (and beyond)
by fedora-badges
#271: Create autotestd systemd.service file for F15 (and beyond)
-----------------------+----------------------------------------------------
Reporter: jlaska | Owner:
Type: task | Status: new
Priority: major | Milestone: Package Update Acceptance Test Plan
Component: packaging | Keywords:
-----------------------+----------------------------------------------------
07:41:40 Viking-Ice: jlaska: nr.1 upstream man pages nr.2 comparing
converting
https://fedoraproject.org/wiki/User:Johannbg/QA/Systemd/compatability (
The Fedora autotest-server package includes a sysVinit script. A
systemd.service file will be needed for f15 and beyond. Guidance from
Viking-Ice included below ...
{{{
07:41:40 Viking-Ice: jlaska: nr.1 upstream man pages nr.2 comparing
converting
https://fedoraproject.org/wiki/User:Johannbg/QA/Systemd/compatability (
you can side by side view them ) nr.3 scim through
Lennart's blog
07:42:36 jlaska: Viking-Ice: perfect, just the bread-crumb trail I
needed. Thank you
07:43:04 * jlaska goes to create a ticket with these instructions (need
to eventually create an autotestd.service)
07:44:02 Viking-Ice: I deliberately designed the wiki page so those
wanting to convert could side by side compare what already had been
converted for you
know ah.. they solve this problem that way moment..
07:45:14 <-- juhp [~petersen(a)66.187.239.10] has quit (Ping timeout: 240
seconds)
07:46:51 Viking-Ice: jlaska: throw this link into your pool
http://0pointer.de/blog/projects/systemd-for-admins-3.html
07:48:21 Viking-Ice: jlaska: what he mentioned there is the skeleton to
be built upon as inn the first example of the service file. Always start
like that
then gradually build on top of that if needed
}}}
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/271>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
12 years, 11 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] #268: Rename lib/python to lib/autoqa
by fedora-badges
#268: Rename lib/python to lib/autoqa
----------------------+-----------------------------------------------------
Reporter: jskladan | Owner:
Type: task | Status: new
Priority: minor | Milestone: Finger Food
Component: core | Keywords:
----------------------+-----------------------------------------------------
It would make more sense to have it named as 'autoqa' rather than 'python'
- e.g. when we want to import the library from inside the git, etc.
Of course, adequate changes need to be made in Makefile and autoqa.spec
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/268>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
13 years
[AutoQA] #272: Tell test which arch it is supposed to test
by fedora-badges
#272: Tell test which arch it is supposed to test
-------------------------+--------------------------------------------------
Reporter: kparal | Owner:
Type: enhancement | Status: new
Priority: major | Milestone: Finger Food
Component: core | Keywords:
-------------------------+--------------------------------------------------
Some tests need to know which architecture to check. But currently we
don't pass that information (in the control file). The test can take a
guess by detecting operating system architecture (not hardware
architecture), but that's an ugly workaround. Pass the architecture info
from autoqa script to the test.
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/272>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
13 years
[AutoQA] #273: Change watcher-name based events 'parsing' to event names
by fedora-badges
#273: Change watcher-name based events 'parsing' to event names
-------------------------+--------------------------------------------------
Reporter: jskladan | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone: Finger Food
Component: core | Keywords:
-------------------------+--------------------------------------------------
This task consists of two sub-tasks.
First part is simply changing the 'autoqa watcher_name parameters' calls
in watchers to 'autoqa event_name parameters'.
This also brings a need to re-structure the importing of 'hook.py' - at
the moment, all watchers have hook.py file in their directory structure.
This contains additional rules for parameter parsing. We'll need to redo
the directory structure based on the event names, and change the importing
routine in autoqa script.
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/273>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
13 years