[Development] CI failing regularly

Laszlo Papp lpapp at kde.org
Thu Aug 22 10:10:52 CEST 2013

On Wed, Aug 21, 2013 at 7:49 PM, Nicolás Alvarez
<nicolas.alvarez at gmail.com>wrote:

> > In the long run if we want to have a mechanism that detects what has
> been changed and which tests should be run, then we need to start designing
> it. How would it work?
> I don't think you can reliably figure out when a test is or isn't
> relevant to a change. And the only good reason to do it is if the
> tests take too long. If unrelated tests fail, they should be *fixed*,
> not skipped when they aren't relevant to the change.

Yes, in an ideal world ... However, sometimes people need to become
pragmatic to get things done step by step.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20130822/bd6cd469/attachment.html>

More information about the Development mailing list