On 4 October 2013 17:03, "Paweł Hajdan, Jr." <[email protected]> wrote:
> but even what you're describing > above won't cover _everything_, and this is mostly what I'm saying. > Yeh, its a given that it won't cover /all/ scenarios. Its obviously not intended to /replace/ arch testers, just supplementary context. Also, something else that I forgot to mention, is the real benefit you see with automated test reporting, is the turn around time. Within 24-48 hours of the changes hitting the rsync mirrors, you'll have a batch of results showing you if the recent change broke the build or not. And that could greatly improve the effective stability of (~ARCH) for those who use it, as long as devs check the report stats. And the effective stability of (~ARCH) increases the rate at which (~ARCH) can afford to move, and increased fluidity and movement there would be rather helpful. -- Kent
