[AutoQA] #385: autotest user does not have permissions to access /var/log/autoqa.log
by fedora-badges
#385: autotest user does not have permissions to access /var/log/autoqa.log
--------------------+-------------------------------------------------------
Reporter: tflink | Owner:
Type: defect | Status: new
Priority: major | Milestone: 0.7.0
Component: core | Keywords:
--------------------+-------------------------------------------------------
After installing 0.7.0, whenever I try to run a job as autotest, I get the
following error:
{{{
[Errno 13] Permission denied: '/var/log/autoqa.log'
}}}
Logging should work out of the box with no farther user intervention.
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/385>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
12 years, 5 months
[AutoQA] #384: delete guest when keyboard interrupt occurs during create virt disk
by fedora-badges
#384: delete guest when keyboard interrupt occurs during create virt disk
----------------------+-----------------------------------------------------
Reporter: hongqing | Owner:
Type: task | Status: new
Priority: major | Milestone: Automate installation test plan
Component: core | Keywords:
----------------------+-----------------------------------------------------
The guest cannot be deleted when the keyboard interrupt exception occurs
during create virt disk with guestfs currently. [[BR]]
This should be solved in case server crashes for too many guests in Virt
Manager
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/384>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
12 years, 5 months
[AutoQA] #196: Log failed job scheduling
by fedora-badges
#196: Log failed job scheduling
-------------------------+--------------------------------------------------
Reporter: kparal | Owner: kparal
Type: enhancement | Status: new
Priority: major | Milestone:
Component: harness | Version: 1.0
Keywords: |
-------------------------+--------------------------------------------------
Currently when we schedule a job and it fails, we just print it out and
forget about it:
{{{
retval = schedule_job(control, email=email, name=testname,
required_arch=arch, dryrun=opts.dryrun,
labels=aq_labels)
if retval != 0:
print "ERROR: failed to schedule job %s" % testname
}}}
That should not be the case. We should:
* use syslog and log important stuff to /var/log/autoqa.log or similar
* send an email about failed scheduling to autoqa-results
That way we will know something is wrong and will be able to fix it.
Otherwise it just silently fails and we don't know about it.
Feel free to reassign the ticket if you want to work on it.
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/196>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
12 years, 5 months
AutoQA 0.7.0 Status
by Tim Flink
Now that Fedora 16 has gone gold, we can start focusing on AutoQA again.
How do we feel about evaluating release readiness in 2 weeks? I really
want to get the bodhi link shortening feature done. It's been WAY too
long already.
I know that the link shortening feature could be ready in 2 weeks but
I'm not as sure about the other tickets currently listed as part of
0.7.0 because I haven't been paying as much attention to them.
These are the tickets currently flagged for 0.7.0. I've added what I
know about them but if you know more, could you add information?
Thanks,
Tim
[347] - Test results are sometimes linked incorrectly in Bodhi
- https://fedorahosted.org/autoqa/ticket/347
This is moving along. I've tested the current patch and it does work
but I still have some questions about the form these shortened links
will take. When we figure that out, it shouldn't take long to finish
[373] - ResultsDB: Add 'store to ResultsDB' functionality to test.py
- https://fedorahosted.org/autoqa/ticket/373
How is this coming along? I haven't had the chance to review the code
yet but I'm wondering how close we are to being able to deploy
ResultsDB into staging.
[196] - Use standard logging facilities
- https://fedorahosted.org/autoqa/ticket/196
Again, I haven't had the chance to look at this code yet but from an
initial look at the ticket, it sounds like progress is being made.
[254] - Transfer autoqa library to autotest clients
- https://fedorahosted.org/autoqa/ticket/254
I think this is pretty much done, sans documentation. I haven't
noticed any issues in the staging environment.
[350] - Add support for using file proxy
- https://fedorahosted.org/autoqa/ticket/350
It sounds like Kamil has been making progress but I'm wondering if
this would be ready in 2 weeks.
[355] - Determine Use Cases for Functional Self Tests
- https://fedorahosted.org/autoqa/ticket/355
Honestly, I haven't touched this yet but I don't think that we really
need it for 0.7.0.
12 years, 5 months
[AutoQA] #382: Pony: have a string freeze check for packages
by fedora-badges
#382: Pony: have a string freeze check for packages
-------------------------+--------------------------------------------------
Reporter: adamwill | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone: Future test cases
Component: tests | Keywords:
-------------------------+--------------------------------------------------
An idea for a new test just came up in the release readiness meeting - an
rpmdiff-style check for whether translatable strings have changed in a new
package build, which we could use to enforce the string freeze (flag up
packages with changed strings after the string freeze).
In vague hand-wavy theory this should just come down to diffing the files
flagged with %lang in the package list, I guess?
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/382>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
12 years, 5 months