AutoQA and Fedora Messaging
by Tim Flink
I think that we had plans to use Fedora Messaging back when it was
first proposed but I don't think that we've talked about it recently.
The current timeline predicts that fedmsg will be deployed into
production by the end of the calendar year, potentially sooner. From
what I can gather, there is an expectation that AutoQA will eventually
use fedmsg to broadcast results and schedule tests, replacing the
current method of direct Bodhi comments and cron jobs to poll
Bodhi/Koji.
I don't think that it's anything we have to worry about right now but
it's probably something that we want to start thinking about in the
near future. Hopefully there will be some test support code coming with
fedmsg (mocks/stubs, mostly) that would help us in development but
AFAIK, none of that has been written yet.
I'm planning to keep attending the Messaging meetings and will pass on
updates as I learn about them.
Tim
12 years
[AutoQA] #206: Update bodhi to enforce Package Update Acceptance policy
by fedora-badges
#206: Update bodhi to enforce Package Update Acceptance policy
----------------------------+-----------------------------------------------
Reporter: wwoods | Owner:
Type: task | Status: new
Priority: major | Milestone: Package Update Acceptance Test Plan
Component: infrastructure | Version: 1.0
Keywords: |
----------------------------+-----------------------------------------------
In order to enforce the Package Update Acceptance Test Plan, Bodhi will
need be modified to reject the push of any package that fails acceptance
testing.
The acceptance tests may need to send status/data to bodhi in order for it
to make decisions about policy (see e.g. ticket #205). Later bodhi might
just get data from resultdb (see that milestone for details).
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/206>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
12 years
[AutoQA] #252: Provide all autotest client combinations that we need
by fedora-badges
#252: Provide all autotest client combinations that we need
------------------------+---------------------------------------------------
Reporter: kparal | Owner:
Type: task | Status: new
Priority: major | Milestone: 0.5.0
Component: production | Keywords:
------------------------+---------------------------------------------------
Currently our production server at http://autoqa.fedoraproject.org/ has 6
autotest clients assigned, all bare metals with Fedora 13 installed, with
mixed architectures. But we need more.
According to https://fedoraproject.org/wiki/Managing_autotest_labels we
have two architecture labels, two fedora release labels (the two currently
supported Fedora releases, I would omit Rawhide for now) and two virt
labels (virtual machine or bare metal). We need machines for every
combination of those labels (that is 8 IICC - if I count correctly). And
we would like to see a bit more 64bit machines, because we use them for
noarch tests.
Currently the only test that really requires all those combinations is
initscripts test. But there will be more in the future. It is quite some
farm, but it seems we'll have to build it.
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/252>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
12 years, 1 month
[AutoQA] #413: conflicts: yum.Errors.NoMoreMirrorsRepoError: failure: Packages/cernlib-g77-devel-2006-33.fc12.i686.rpm from parent-2: [Errno 256] No more mirrors to try.
by fedora-badges
#413: conflicts: yum.Errors.NoMoreMirrorsRepoError: failure:
Packages/cernlib-g77-devel-2006-33.fc12.i686.rpm from parent-2: [Errno 256]
No more mirrors to try.
---------------------+---------------------
Reporter: kparal | Owner: mkrizek
Type: defect | Status: new
Priority: major | Milestone: 0.8.0
Component: tests | Keywords:
Blocked By: | Blocking:
---------------------+---------------------
This is really weird, I already saw it several times. I don't see
'conflicts' test as very important, but still, Martin, can you have a look
at it? How does it happen that there's a package that is not available
from any repos? Please note the package name is different for different
repos. Are we having just connection issues?
{{{
Traceback (most recent call last):
File "./potential_conflict.py", line 243, in <module>
elif file_conflict(fn, pkglist):
File "./potential_conflict.py", line 140, in file_conflict
pkg.repo.getHeader(pkg)
File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 883, in
getHeader
cache=cache, size=size,
File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 842, in
_getFile
raise Errors.NoMoreMirrorsRepoError, errstr
yum.Errors.NoMoreMirrorsRepoError: failure:
Packages/cernlib-g77-devel-2006-33.fc12.i686.rpm from parent-2: [Errno
256] No more mirrors to try.
}}}
http://autoqa-
stg.fedoraproject.org/results/32302-autotest/qa07.qa.fedoraproject.org/co...
-updates-testing-.html
http://autoqa-
stg.fedoraproject.org/results/32311-autotest/virt23.qa/conflicts/results/f16
-updates-testing-.html
http://autoqa-
stg.fedoraproject.org/results/32308-autotest/virt24.qa/conflicts/results/f16
-updates-x86_64.html
http://autoqa-
stg.fedoraproject.org/results/32296-autotest/virt27.qa/conflicts/results/f15
-updates-x86_64.html
http://autoqa-
stg.fedoraproject.org/results/32001-autotest/virt24.qa/conflicts/results/...
http://autoqa-
stg.fedoraproject.org/results/32488-autotest/virt24.qa/conflicts/results/...
http://autoqa-
stg.fedoraproject.org/results/32617-autotest/virt26.qa/conflicts/results/f17
-updates-testing-.html
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/413>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
12 years, 1 month
Fedora Message Bus
by Tim Flink
I had a chance to talk with lmacken and 3bean while at PyCon and
learned that the Fedora Message Bus project [1] is being worked on
again.
It sounds like there is still a lot of work that needs to happen before
we see it implemented but it might be a good way out of our current
method of test scheduling.
I'm planning to attend the meetings for now and we'll see where this
goes. I expect that it will eventually change the way that we schedule
tests in AutoQA.
Tim
[1] https://fedoraproject.org/wiki/Messaging_SIG
12 years, 1 month
