Re: [AutoQA] #245: Add support for test re-scheduling
#245: Add support for test re-scheduling
--------------------+-------------------------------------------------------
Reporter: kparal | Owner:
Type: task | Status: new
Priority: major | Milestone: 0.5.0
Component: core | Resolution:
Keywords: |
--------------------+-------------------------------------------------------
Comment (by jlaska):
Replying to [ticket:245 kparal]:
The important thing is that the maintainer should be able to trigger
the
re-scheduling, not just us.
Oh oops, I missed this critical part of your post. If I understand
correctly, this is to capture the case when a maintainer builds updates
out of order? Meaning, they don't start with rawhide and work back? So
they start with F-14 (or older), which fails because an older package
version is in rawhide.
One way to re-schedule is to use the existing scheduling method and submit
a new update. That only applies if there are some bugs they are fixing
and they are bumping the NVR. For the case of upgradepath, they likely
won't rebuild a newer version just to resolve this test timing issue.
Assuming resultsdb was in place, the maintainer could of course WAIVE the
test result with a comment indicating that the rawhide build is
inprogress, and rescheduling wouldn't be required. Long-term, it'd be
nice to have some link/button on bodhi (or resultsdb) that would submit a
reschedule to autoqa/autotest.
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/245#comment:2>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project