Bug #76075 for ICal-QuickAdd: Unit tests fail

Tue Mar 27 14:23:58 2012 ARJONES [...] cpan.org - Ticket created

Subject:

Unit tests fail

The unit tests fail on install: <pre> Building and testing ICal-QuickAdd-1.00 for ICal::QuickAdd Building ICal-QuickAdd # Failed test 'DateTime date is correct' # at t/basic.t line 21. # got: '2012-03-27' # expected: '1976-03-31' # Failed test 'DateTime hour is correct' # at t/basic.t line 22. # got: '18' # expected: '12' # Failed test 'DateTime minute is correct' # at t/basic.t line 23. # got: '21' # expected: '0' Use of uninitialized value in lc at /Users/ajones/perl5/perlbrew/perls/perl- 5.12.1/lib/site_perl/5.12.1/Email/Simple/Header.pm line 216. # Looks like you failed 3 tests of 14. t/basic.t ......... Dubious, test returned 3 (wstat 768, 0x300) Failed 3/14 subtests t/pod-coverage.t .. ok t/pod.t ........... ok Test Summary Report ------------------- t/basic.t (Wstat: 768 Tests: 14 Failed: 3) Failed tests: 5-7 Non-zero exit status: 3 Files=3, Tests=17, 1 wallclock secs ( 0.03 usr 0.01 sys + 0.54 cusr 0.07 csys = 0.65 CPU) Result: FAIL Failed 1/3 test programs. 3/17 subtests failed. </pre> Regards, Andrew

Mon Apr 02 10:18:53 2012 MARKSTOS [...] cpan.org - Status changed from 'new' to 'open'

Mon Apr 02 10:20:36 2012 MARKSTOS [...] cpan.org - Correspondence added

Thanks for the report. I'm not using this module any more, and don't have plans to in the future. I would welcome a co-maintainer or someone else who would like to be the primary maintainer. It was stable and functional when I last used it, and may still be of interest to someone else. Mark

Mon Apr 02 14:28:05 2012 ARJONES [...] cpan.org - Correspondence added

OK, thanks for getting back to me. I'm interested in the parsing of a string to an event, which returns a Data::ICal object, but I don't need the rest of the functionality. Do you think it would be better if I took over maintenance of this module and just fixed these parts, or should I create my own module that does what I want and leave this module for someone who would use more of ICal::QuickAdd? Andrew On Mon Apr 02 10:20:36 2012, MARKSTOS wrote: Show quoted text

> Thanks for the report. > > I'm not using this module any more, and don't have plans to in the > future. I would welcome a co-maintainer or someone else who would like to > be the primary maintainer. > > It was stable and functional when I last used it, and may still be of > interest to someone else. > > Mark

Mon Apr 02 14:42:37 2012 mark [...] summersault.com - Correspondence added

Subject:	Re: [rt.cpan.org #76075] Unit tests fail
Date:	Mon, 02 Apr 2012 14:42:28 -0400
To:	bug-ICal-QuickAdd [...] rt.cpan.org
From:	Mark Stosberg <mark [...] summersault.com>

Show quoted text

> OK, thanks for getting back to me. > > I'm interested in the parsing of a string to an event, which returns a Data::ICal object, but I don't > need the rest of the functionality. > > Do you think it would be better if I took over maintenance of this module and just fixed these > parts, or should I create my own module that does what I want and leave this module for someone > who would use more of ICal::QuickAdd?

I would fork it, take what you want, and give it a name that's more precise about what the new version does. It will be easier to find the refined functionality with the more precise name, and you won't have the baggage of maintaining functionality that you don't use or care about it. If ICal::QuickAdd continues to survive, perhaps it will one day farm-out some of it's functionality to your new module. Mark

Mon Apr 02 14:47:21 2012 ARJONES [...] cpan.org - Correspondence added

OK, sounds good. Thanks! On Mon Apr 02 14:42:37 2012, mark@summersault.com wrote: Show quoted text

> > OK, thanks for getting back to me. > > > > I'm interested in the parsing of a string to an event, which returns

> a Data::ICal object, but I don't

> > need the rest of the functionality. > > > > Do you think it would be better if I took over maintenance of this

> module and just fixed these

> > parts, or should I create my own module that does what I want and

> leave this module for someone

> > who would use more of ICal::QuickAdd?

> > I would fork it, take what you want, and give it a name that's more > precise about what the new version does. > > It will be easier to find the refined functionality with the more > precise name, and you won't have the baggage of maintaining > functionality that you don't use or care about it. > > If ICal::QuickAdd continues to survive, perhaps it will one day farm- > out > some of it's functionality to your new module. > > Mark