From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31387 invoked by alias); 23 Jul 2007 15:15:45 -0000 Received: (qmail 31371 invoked by uid 22791); 23 Jul 2007 15:15:44 -0000 X-Spam-Status: No, hits=-1.1 required=5.0 tests=AWL,BAYES_40,DK_POLICY_SIGNSOME X-Spam-Check-By: sourceware.org Date: Mon, 23 Jul 2007 15:15:00 -0000 From: Kris Van Hees To: frysk-testresults@sourceware.org, frysk@sourceware.org Subject: Automated build-and-test summary reports Message-ID: <20070723151536.GB1451@ca-server1.us.oracle.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.11 X-Brightmail-Tracker: AAAAAQAAAAI= X-Brightmail-Tracker: AAAAAQAAAAI= X-Whitelist: TRUE X-Whitelist: TRUE Mailing-List: contact frysk-testresults-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: frysk-testresults-owner@sourceware.org Reply-To: frysk@sourceware.org X-SW-Source: 2007-q3/txt/msg00020.txt.bz2 List-Id: No automated summary reports have been generated for the past 5 days due to every single build-and-test run requiring manual intervention to complete. This has been traced down to hanging tests, although the exact details are still being investigated. One possible cause may be the re-enabling of tests that were marked as unresolved/unsupported in the past. Investigation continues into which exact test is causing the problem. On top of all this, it was found that on FC6 i386, a large mount of TestRunner instances was left hanging after completion of the testsuite. This is also being investigated. I will generate summary reports for the missing days manually and send them out. It didn't happen automaticaly because due to the manual lintervention needed to get test runs unstuck, the results did not get uploaded within the timeframe needed to get picked up by the summary report generation process. If anyone has noticed this behaviour as well, and would have a clue already about what might be going on, please let me know :) It's rather important that we can ensure that tests are guaranteed to complete, one way or another. If a test does not complete in reasonable time, there definitely should be a process in place that aborts it, with appropriate result being logged. Cheers, Kris