Re: Scalability of Devel::Cover

2005-06-22 Thread Kevin Scaldeferri
On Jun 21, 2005, at 5:59 PM, Geoffrey Young wrote: This seems unfortunate for at least two reasons: 1) it ends up taking a really long time to run the tests. At some point, maybe long enough that nightly tests become prohibitive (even more so for continuous integration). We have a

Re: Scalability of Devel::Cover

2005-06-21 Thread Kevin Scaldeferri
On Jun 21, 2005, at 1:09 PM, James E Keenan wrote: Kevin Scaldeferri wrote: It seems to me like the time Devel::Cover takes to do its book-keeping when a process terminates is linear in the total number of files in the cover_db, rather than linear in the number of files involved

Re: Scalability of Devel::Cover

2005-06-16 Thread Kevin Scaldeferri
On Jun 14, 2005, at 1:32 PM, Kevin Scaldeferri wrote: A little more interesting information. I ran a coverage test for the full code base. Then I did this: [kevin]% time perl -MDevel::Cover -e 1 ... perl -MDevel::Cover -e 1 14.19s user 0.88s system 79% cpu 18.997 total After spending

Scalability of Devel::Cover

2005-06-14 Thread Kevin Scaldeferri
It seems to me like the time Devel::Cover takes to do its book-keeping when a process terminates is linear in the total number of files in the cover_db, rather than linear in the number of files involved in that particular process. This means that as your code base grows, the time to run unit

Re: Scalability of Devel::Cover

2005-06-14 Thread Kevin Scaldeferri
that prevent it, but it seems like this ought to take pretty close to no time at all. A little information about the database: [kevin]% ls cover_db/structure | wc -l 599 [kevin]% ls cover_db/runs | wc -l 46 -kevin On Jun 14, 2005, at 11:27 AM, Kevin Scaldeferri wrote: It seems to me like

Re: Devel::cover bug?

2005-06-03 Thread Kevin Scaldeferri
On Jun 3, 2005, at 1:40 PM, Paul Johnson wrote: Certainly. Of course, it's always possible and quite likely that there is a bug in my code somewhere. But there is also a chance that I am conflating two ops, since I have yet to come up with a way to uniquely identify an op (suggestions

Re: Phalanx 100 list

2005-06-02 Thread Kevin Scaldeferri
On Jun 2, 2005, at 3:48 AM, Dave Paris wrote: Greetings, It was brought to my attention that Crypt::DES is included in the Phalanx 100 list. While I'm flattered, I think this should be replaced by a better symmetrical crypto module like Crypt::Rijndael. The reasoning is simple.

Re: Devel::cover bug?

2005-06-01 Thread Kevin Scaldeferri
On Jun 1, 2005, at 12:49 AM, Paul Johnson wrote: If you look at the subroutine coverage page, it claims that there is a BEGIN block uncovered at that line. That does sound a little strange. Are you able to produce an example showing this problem? No. In fact, it isn't consistent. Last

Re: Devel::cover bug?

2005-06-01 Thread Kevin Scaldeferri
On Jun 1, 2005, at 2:35 PM, James E Keenan wrote: Kevin Scaldeferri wrote: I'm looking at a bit of output from Devel::Cover that I imagine has to be a bug. I'll try my best to reproduce the HTML output: stmt branch cond sub time code 221862 100 100

Re: Devel::cover bug?

2005-06-01 Thread Kevin Scaldeferri
On Jun 1, 2005, at 12:49 AM, Paul Johnson wrote: On Tue, May 31, 2005 at 04:00:12PM -0700, Kevin Scaldeferri wrote: I'm looking at a bit of output from Devel::Cover that I imagine has to be a bug. I'll try my best to reproduce the HTML output: You might find it slightly easier

Re: testing that processes terminate

2005-05-23 Thread Kevin Scaldeferri
On May 23, 2005, at 7:08 AM, Ian Langworth wrote: The test is happy when I run it normally, and even when I run it under Devel::Cover, but it consistently fails in our nightly test run (under Devel::Cover). As best I can figure, Devel::Cover is slowing things down so much that my test

testing that processes terminate

2005-05-18 Thread Kevin Scaldeferri
I recently had to deal with a bug where under certain circumstances a server process would never terminate, but would block indefinitely in the shutdown process. Being a good coder, I wrote a unit test to reproduce the problem before I fixed it. The test is happy when I run it normally, and

Re: Test automation with perl.

2005-04-14 Thread Kevin Scaldeferri
On Apr 14, 2005, at 12:43 AM, suresh babu wrote: Hi Experts, I would like to reiterate my request. For our students i need these projects. Basically i want some open source projects and their test suits(developed using perl). We would like to use these projects as case studies to demonstrate

Re: Testing Ties

2005-04-12 Thread Kevin Scaldeferri
On Apr 12, 2005, at 3:58 PM, James E Keenan wrote: How do you test that a variable has been tied to a class? I looked through Test::More; the term 'tie' is conspicuous by its absence. I also searched the archives of this list and couldn't locate anything. I'm looking for something along the

Re: Devel::Cover error from Storable

2004-12-09 Thread Kevin Scaldeferri
On Dec 9, 2004, at 9:50 AM, Steve Peters wrote: On Thu, Dec 09, 2004 at 09:34:18AM -0800, Kevin Scaldeferri wrote: My unit test suite recently started spitting out this error when run under Devel::Cover. It runs normally and successfully without. Has anyone seen this before: Magic number

Re: Devel::Cover error from Storable

2004-12-09 Thread Kevin Scaldeferri
On Dec 9, 2004, at 10:16 AM, Kevin Scaldeferri wrote: Hmm... if there were two versions of Storable installed, and Devel::Cover initially found one, and then later IPC::Shareable somehow caused the other to be loaded instead, that might cause this... I will go investigate that possibility

Re: Devel::Cover error from Storable

2004-12-09 Thread Kevin Scaldeferri
On Dec 9, 2004, at 11:21 AM, Paul Johnson wrote: Whether this is related to your main problem I can't tell, though I have have seen that warning plenty of times before but never encountered your main problem. Yeah, it's probably unrelated. My latest theory was that my forked processes were

Pipe dream - Devel::Cover::Regex

2004-12-07 Thread Kevin Scaldeferri
I'm wondering if I'm the only one who would love to see Devel::Cover::Regex? Many (most?) perl programs are pretty regex heavy, and if we are honest with ourselves, we have to admit that each regex is actually a program in itself. You can try to throw lots of inputs at it and hope that you

Re: running Devel::Cover in mod_perl (1.3)

2004-09-21 Thread Kevin Scaldeferri
On Sep 21, 2004, at 2:58 AM, [EMAIL PROTECTED] wrote: On Mon, 20 Sep 2004, Kevin Scaldeferri wrote: The current version of Devel::Cover asserts that running it on a mod_perl server ought to be as simple as adding 'use Devel::Cover' to your startup script. However, when I do this, I get

running Devel::Cover in mod_perl (1.3)

2004-09-20 Thread Kevin Scaldeferri
The current version of Devel::Cover asserts that running it on a mod_perl server ought to be as simple as adding 'use Devel::Cover' to your startup script. However, when I do this, I get the following failure: Syntax error on line 1225 of /home/kevin/.../conf/httpd.conf: Can't use an

Re: [Devel::Cover] return conditions

2004-09-16 Thread Kevin Scaldeferri
On Sep 16, 2004, at 2:47 PM, Tels wrote: -BEGIN PGP SIGNED MESSAGE- Moin, On Thursday 16 September 2004 23:37, Geoffrey Young wrote: hi paul :) I think this has come up before, but I'm not sure what the resolution was. I just came across (production) code that looks like this: return 1