Well I have managed to upload a perl module to CPAN (Math::StochasticProcess). However I have the embarrassment of two tests having failed so I am forced to produce a new version. I will deal with the CPAN testers who so rudely failed my test scripts myself. Unfortunately I crave and beg for some human and/or monastical feedback. Are there any other changes that should go into a version 0.03?

The only desirable change that occurs to me is a class that would sit between Math::StochasticProcess::Event and Math::StochasticProcess::Event::Tupe and would handle probability. I did not put this directly in the base class for the following reasons:

  1. Some probability spaces may have ways of defining probability that are inherent in the representation. I guess if they did they would not need my module.
  2. Someone might want to use Big numbers for more accurate calculations.

Replies are listed 'Best First'.
Re: RFC: Math::StochasticProcess
by Your Mother (Archbishop) on Dec 14, 2008 at 17:58 UTC

    I know you were being facetious -- at least I think so -- about the testers who failed your distribution. I just want to say that failing test reports are a *blessing*. Without the reports, you just have would-be users, who will rarely communicate with you, who have failed installs. They do tend to communicate with each other though and a dist with failing tests will get a reputation of being crap even if the underlying code is gold.

[reply]
      Yes I was not serious bout the CPAN tests. Specifically I was trying to keep this thread away from the subject of the 2/31 failures. I will probably need to contact those testers directly as I cannot reproduce their circumstances. Also the test reports are quite clear. Rather I was just looking for general feedback.

      edit: Also as I understand it the process is completely automated so it remains true that noone but me has probably looked at beyind the name so far.

[reply]

        I had a similar dist which was failing for users and I could not figure out why (through like 4 releases of just looking stupid twiddling stuff and waiting to see if the tests passed; mine always did). It was related to prereqs not being installed even though I was declaring them. I finally added explicit versions to everything as well as some modules that the prereqs called but my code didn't and that fixed it for testers.

        Your tests seem to be crashing at the junction of Exporter + 5.6 + Darwin (and maybe Params::Validate is related though its tester report doesn't seem to agree). You could make a note of that in the Pod/Changes/README until you get it sorted.

[reply]

Back to Meditations