Taskotron (was: Re: Unannounced ABI change without soname bump in libevdev-0.6 in Rawhide (and F19 and F20...) breaks GNOME, probably other consumers)

Kamil Paral kparal at redhat.com
Mon Jan 6 13:00:23 UTC 2014


> On Thu, Dec 26, 2013 at 07:52:04PM -0800, Adam Williamson wrote:
> > No. There's a bad one, which is AutoQA. The problem with it is it's more
> > or less considered obsolete now as far as new development goes; the devs
> > are working on Taskotron to replace it, but I don't believe it's ready
> > for test contributions yet, unfortunately.
> > 
> > Once we have Taskotron up and going (which I believe is aimed for the
> > first half of 2014), we can start adding more automated tests, which
> > we'd very much like to do, but I don't think anyone's keen on adding
> > extra tests to AutoQA at this point, as any time spent implementing them
> > and keeping them working takes away from time spent developing
> > Taskotron.
> 
> Please can I *urge* the Taskotron developers to fix the major
> deficiency with AutoQA: Allow package maintainers to flexibly upload
> tests to run on their package.  Ideally these tests would be contained
> in dist-git; for example Taskotron could look in the current branch
> for a 'test.sh' file and run it.  Thus allowing the developer to
> associate tests with the package, have them run after a build, and be
> able to change/disable the tests at any time.
> 
> (I did read the Taskotron wiki page before posting this .. I could not
> see any place where this AutoQA shortcoming would be fixed, but my
> apologies if this is already planned)
> 
> Rich.

Thanks, Richard, for your feedback. That's exactly one of the problems in AutoQA that we want to improve in Taskotron. The package maintainers or test maintainers should have a direct and simple control over their tests.


More information about the devel mailing list