stage: hanging jobs
by Kamil Paral
I noticed today that we have about 50 queued x86_64/noarch depchecks on our staging server. The problem was in this job:
http://autoqa-stg.fedoraproject.org/results/2335-autotest/virt27.qa/debug/
It was hanging for two days in the "running" state. This seems like an autotest problem, it should detect when connection times out and it should abort the job automatically. (But now I'm not sure if we didn't make some adjustments the autotest's watchdog timer, we need to investigate).
I aborted the hanging job and all but the last two depchecks.
If this happens again we should investigate and report to autotest devs.
12 years, 4 months
[AutoQA] #355: Determine Use Cases for Functional Self Tests
by fedora-badges
#355: Determine Use Cases for Functional Self Tests
---------------------------+------------------------------------------------
Reporter: tflink | Owner:
Type: task | Status: new
Priority: minor | Milestone: 0.6.0
Component: documentation | Keywords:
---------------------------+------------------------------------------------
== Description ==
In order to [ticket:352 create functional test cases] and [ticket:353
create mockups for fedora services], we need to have some idea of the use
cases that we would want to test for.
Once this information is gathered, we can start creating the tools that we
need for better self testing in AutoQA.
== Questions to answer ==
NOTE: please add to this list if anything is missing.
* What are we looking to test
* Tests (depcheck, upgradepath etc.)
* Situations (broken deps, not breaking upgrade path etc.)
* What do we need in order to test it
* RPM details
* Repo contents
* Expected Results
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/355>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
12 years, 4 months
[AutoQA] #345: Implement file locks for all watchers
by fedora-badges
#345: Implement file locks for all watchers
-------------------------+--------------------------------------------------
Reporter: kparal | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone: Finger Food
Component: watchers | Keywords:
-------------------------+--------------------------------------------------
In ticket #342 we implemented file lock for koji-bodhi watcher so that it
is not run concurrently in multiple instances. Implement the same for all
the remaining watchers.
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/345>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
12 years, 4 months
AutoQA 0.8.0 Planning
by Tim Flink
Now that 0.7.0 has pretty much been released, it's time to start
thinking about 0.8.0. Kamil and I talked about this earlier today and
would like to get started on that sooner than later.
We'd like to do a phone conference again and the currently proposed
time is Thursday, December 1 at 13:30 UTC (05:30 PST, 08:30 EST, 14:30
CET). It's a little early for those of us who are in the US but it
seems like a fair compromise with the folks who are in or near Brno
time.
If you're interested and that time doesn't work for you, let us know
and we'll try to come up with a time that works for everyone. It would
pretty much need to be this week, though.
Tim
12 years, 4 months
Anaconda UI rewrite + AutoQA
by Kamil Paral
On our last QA meeting Adam Williamson notified us that there would be an Anaconda hackfest at the next FUDCon and we should raise our concerns (if we had some) regarding AutoQA and the UI re-write. Well, I don't know much about anaconda testing inside AutoQA, I just know we execute some anaconda tests, that's all. But I decided to kick off the discussion and CC relevant people.
>From what I know, we have two kind of anaconda tests inside AutoQA:
1. older rats_install test written by Will Woods and executed James Laska in the past
2. newer anaconda_storage, anaconda_checkbot and compose_tree written by Chris Lumens and James Laska
I am not sure which of those tests provide important feedback to the anaconda team and whether they are being used at all. Can relevant people provide more details about it?
Anaconda team, do you have some specific questions about AutoQA integration and the UI re-write? Will you want to change your tests inside AutoQA in response the new UI and need to have some information from us? I'll happy to answer them if I can.
Also, if the test authors have some comments or recommendation about the new UI architecture in order to allow simple automated testing, please post them here.
Thanks,
Kamil
12 years, 4 months
[AutoQA] #368: reconstructe Fedora install test automation framework
by fedora-badges
#368: reconstructe Fedora install test automation framework
----------------------+-----------------------------------------------------
Reporter: hongqing | Owner: hongqing
Type: task | Status: new
Priority: major | Milestone: Automate installation test plan
Component: autotest | Keywords:
----------------------+-----------------------------------------------------
A new framework should be constructed to mapping the test cases and
kickstart files, and it also should be easy for the users to contribute.
A big idea is that one text file will be used to map the test case names
and kickstart files, and the kickstart files will be keeped in a
directory, during test, the test will iterate all the kickstart in the
directory. Users can create new kickstart files in the directory and write
the relationship between test case and kickstart in the text file, of
course, they can also pass it by arguments instead of doing this.
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/368>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
12 years, 4 months
[AutoQA] #383: Depcheck and Upgradepath crash if yourls is not configured
by fedora-badges
#383: Depcheck and Upgradepath crash if yourls is not configured
----------------------+-----------------------------------------------------
Reporter: tflink | Owner:
Type: defect | Status: new
Priority: critical | Milestone: 0.7.0
Component: core | Keywords:
----------------------+-----------------------------------------------------
If yourls is not configured (empty configuration file), depcheck and
upgrade path crash at the end of the test when URL shortening is
attempted.
There is an example of this in the staging environment:
http://autoqa-
stg.fedoraproject.org/results/4194-autotest/virt24.qa/debug/client.0.DEBUG
{{{
11/11 15:28:23 INFO | test:0358| Log created:
/usr/share/autotest/results/default/depcheck/results/wicd-
kde-0.2.3-3.fc1.html
11/11 15:28:23 ERROR| test:0473|
--------------------------------------------------------------------------------
11/11 15:28:23 ERROR| test:0473| Traceback (most recent call last):
11/11 15:28:23 ERROR| test:0473| File "/usr/lib/python2.7/site-
packages/autoqa/decorators.py", line 72, in newf
11/11 15:28:23 ERROR| test:0473| f_result = f(*args, **kwargs)
#call the decorated function
11/11 15:28:23 ERROR| test:0473| File
"/usr/share/autotest/tests/depcheck/depcheck.py", line 362, in run_once
11/11 15:28:23 ERROR| test:0473| self.post_results(td, bodhi =
{'title': title})
11/11 15:28:23 ERROR| test:0473| File "/usr/lib/python2.7/site-
packages/autoqa/test.py", line 231, in post_results
11/11 15:28:23 ERROR| test:0473| self._send_email(test_detail,
optin=optin, logname=logname)
11/11 15:28:23 ERROR| test:0473| File "/usr/lib/python2.7/site-
packages/autoqa/test.py", line 292, in _send_email
11/11 15:28:23 ERROR| test:0473| logname=logname)
11/11 15:28:23 ERROR| test:0473| File "/usr/lib/python2.7/site-
packages/autoqa/test.py", line 334, in _create_email_body
11/11 15:28:23 ERROR| test:0473| url =
self._shorten_url(self.url['result_dir'] + urllib.quote(logname),
test_detail)
11/11 15:28:23 ERROR| test:0473| File "/usr/lib/python2.7/site-
packages/autoqa/test.py", line 179, in _shorten_url
11/11 15:28:23 ERROR| test:0473| url =
self._yourls_client.shorten(url)
11/11 15:28:23 ERROR| test:0473| File "/usr/lib/python2.7/site-
packages/yourls/client.py", line 104, in shorten
11/11 15:28:23 ERROR| test:0473| raw_data =
json.loads(self._send_request(args))
11/11 15:28:23 ERROR| test:0473| File "/usr/lib/python2.7/site-
packages/yourls/client.py", line 81, in _send_request
11/11 15:28:23 ERROR| test:0473| r = urllib2.urlopen(req)
11/11 15:28:23 ERROR| test:0473| File
"/usr/lib64/python2.7/urllib2.py", line 126, in urlopen
11/11 15:28:23 ERROR| test:0473| return _opener.open(url, data,
timeout)
11/11 15:28:23 ERROR| test:0473| File
"/usr/lib64/python2.7/urllib2.py", line 384, in open
11/11 15:28:23 ERROR| test:0473| protocol = req.get_type()
11/11 15:28:23 ERROR| test:0473| File
"/usr/lib64/python2.7/urllib2.py", line 245, in get_type
11/11 15:28:23 ERROR| test:0473| raise ValueError, "unknown url
type: %s" % self.__original
11/11 15:28:23 ERROR| test:0473| ValueError: unknown url type:
}}}
This may end up being a bug in python-yourls but that's not clear yet.
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/383>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
12 years, 4 months
Mocking Fedora Infrastructure for Fun and for Profit!
by Tim Flink
OK, I finished an initial version of the mock fedora infrastructure
application that I've been working on and the code is up on github.
- https://github.com/tflink/mock_fedorainfra
At the moment, it is capable of proxying bodhi queries and using local
comments instead of the ones from production Bodhi. This means that you
can run a development instance of AutoQA with comments enabled without
having to worry about disrupting production. It also means that you can
re-run jobs multiple times by deleting comments from the html interface.
Since this will be useful for development as well (ability to rerun
jobs at will instead of praying you time it right so that it runs before
production), I have documentation for how to deploy as either a WSGI
app or using the built-in development server:
- http://tflink.github.com/mock_fedorainfra/
The code is still pretty rough but I'm planning to improve it as time
goes on and features are added. If you have problems, please let me
know.
Tim
12 years, 4 months