<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 1/22/17 4:04 AM, Ankit Chopra wrote:<br>
<blockquote
cite="mid:CAOYWu2v4ANizJdu15vmrCjTwCp_0YVP8eP5kxr0WPh8RkJ-OrA@mail.gmail.com"
type="cite">
<div dir="ltr"><span style="font-size:12.8px">Hi All, </span>
<div style="font-size:12.8px"><br>
</div>
<div style="font-size:12.8px">We want to run coverage.py in our
production application. We want to discover the obsolete code
and see the report with actual production load. </div>
<div style="font-size:12.8px"><br>
</div>
<div style="font-size:12.8px">I have played with coverage.py
tool and have seen that it creates the report after
execution/termination and till that time it keeps everything
in memory. </div>
<div style="font-size:12.8px"><br>
</div>
<div style="font-size:12.8px">Is there a way I can configure it
to dump the report at regular interval like every hour or
daily without stopping my application. and Later on I can
merge and create a consolidated report. </div>
<br>
</div>
</blockquote>
What kind of application is it, why does it run so long, and is
there a natural unit of work that you could take advantage of? For
example, if it's a web application, the simplest thing would be to
measure coverage on a worker process, and start and stop workers on
the frequency you want.<br>
<br>
--Ned.<br>
</body>
</html>