public inbox for frysk-testresults@sourceware.org help / color / mirror / Atom feed
From: Kris Van Hees <kris.van.hees@oracle.com> To: frysk-testresults@sourceware.org, frysk@sourceware.org Subject: Automated build-and-test summary reports Date: Mon, 23 Jul 2007 15:15:00 -0000 [thread overview] Message-ID: <20070723151536.GB1451@ca-server1.us.oracle.com> (raw) 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
reply other threads:[~2007-07-23 15:15 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20070723151536.GB1451@ca-server1.us.oracle.com \ --to=kris.van.hees@oracle.com \ --cc=frysk-testresults@sourceware.org \ --cc=frysk@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).