public inbox for
 help / color / mirror / Atom feed
* Automated build-and-test summary reports
@ 2007-07-23 15:15 Kris Van Hees
  0 siblings, 0 replies; only message in thread
From: Kris Van Hees @ 2007-07-23 15:15 UTC (permalink / raw)
  To: frysk-testresults, frysk

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.


^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2007-07-23 15:15 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-07-23 15:15 Automated build-and-test summary reports Kris Van Hees

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).