#462: wrong TestdayApp event
--+
Reporter: tagoh | Owner: tflink
Type: defect| Status: new
Priority: major | Milestone: Fedora 22
Component: Blocker bug
do it. We just use the
'release' attribute of the current validation event for this purpose.
In practice this is pretty robust; I can't think of a time when this
will do the wrong thing.
It's *possible* to make fedfind discover the Branched release number,
but it's pret
On Wed, 2015-02-18 at 09:53 -0800, Adam Williamson wrote:
>
> Patch attached which more or less brings it to my intended version,
> with !='s and get_release() exception handling added and your
> cleanups preserved. sorry for the mixup! Consider the previous
> version an example of my personal
On Wed, 2015-02-18 at 05:33 -0500, Josef Skladanka wrote:
> Adam,
>
> the run_all code does not really make much sense to me, to be
> honest. After some minor cleanup, the code looks like this:
>
> 171 def run_all(args, wiki=None):
> 172 """Do everything we can: test both Rawhide and Branche
Adam,
the run_all code does not really make much sense to me, to be honest.
After some minor cleanup, the code looks like this:
171 def run_all(args, wiki=None):
172 """Do everything we can: test both Rawhide and Branched nightlies
173 if they exist, and test current compose if it's diffe
This adds an 'all' mode which runs for the current validation event
compose if it hasn't already been done, then runs for the current
date's Rawhide and Branched nightlies, if they exist and aren't the
same as the current validation event. Has a --yesterday parameter to
run on the nightlies fro
