[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
12 years, 12 months
[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] #245: Add support for test re-scheduling
by fedora-badges
#245: Add support for test re-scheduling
--------------------+-------------------------------------------------------
Reporter: kparal | Owner:
Type: task | Status: new
Priority: major | Milestone: 0.5.0
Component: core | Keywords:
--------------------+-------------------------------------------------------
After we start sending results to Bodhi/ResultDB there will immediately
emerge a need for test re-scheduling. There may be different reasons for
that:
1. Something went wrong in the test execution, we need to run it again.
2. The environment has changed and test needs to be executed once again.
For example the upgradepath test for some update failed because of invalid
package versions in higher Fedora releases. That problem has been
corrected and we need now a new execution of the test.
The important thing is that the maintainer should be able to trigger the
re-scheduling, not just us.
Find a way how to properly reschedule tests (we will probably utilize
ResultDB for that) and add that functionality.
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/245>
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
[AutoQA] #247: upgradepath: possible broken-updates scenario for new packages
by fedora-badges
#247: upgradepath: possible broken-updates scenario for new packages
--------------------+-------------------------------------------------------
Reporter: kparal | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: tests | Keywords:
--------------------+-------------------------------------------------------
Here is a scenario that will create broken upgrade path and our current
tests will not catch it:
1. Package foo is available for F12 (foo-1.0-1.fc12), but not for F13.
2. foo-1.0-1.fc13 is sent to f13-updates-pending as a new package update.
upgradepath passes.
3. foo-2.0-1.fc12 is sent to f12-updates-pending. Since there is still no
foo in F13 (AutoQA passed but it has not been pushed by RelEng team),
upgradepath passes.
4. foo-2.0-1.fc12 is pushed to f12-updates.
5. foo-1.0-1.fc13 is pushed to f13-updates.
6. Broken upgrade path.
What can we do about it?
We can break the scenario between steps 4 and 5. But we can't probably do
that just by watching -pending tags. This requires cooperation from the
updates manager (i.e. Bodhi). Bodhi must know that if some foo build
enters f12-updates, and there is also another foo build in f13-updates-
pending, it must notify us (over Fedora Message Bus) and ask us to retest
the latter build.
We can also break the scenario between steps 2 and 3. When we run
upgradepath on foo in f12-updates-pending, we can take into account not
just f13-updates, but also f13-updates-pending. But this is quite
controversial. Some builds in -updates-pending may be denied by RelEng
team, but we could have failed some other builds because of them.
We will probably solve this ticket only when we have advanced
infrastructure ready (ResultDB, Fedora Message Bus). Without it this seems
pretty hard to be solved properly.
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/247>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
13 years