Well, I have two sets in my smoke directory, one for "maint" (Aka Perl 5.8.x) and one for "current" (Aka Perl 5.9.x). You didnt run perldoc yet did you? :-)

Seems to me that if Test::Smoke were included in the distribution, a) it would save another install step; b) it could be set up to test the distribution is was a part of and each distribution would be 'self-contained'.

Alternatively, a command line parameter to the batchfile could identify the relative path of the distribution to be tested.

And no, I didn't run perldoc yet. I thought I'd get through the first run with the default settings before getting sidetracked in to looking at what options were available and being tempted to try them out. Just trying to get a consistant set of notes written down vefore thinking about variations :)

Personally I'd just tell your firewall to ignore anything in the smoke tree.

I don't think my firewall has that option, (and I'm not sure I like the implications of it if it has), but I'll look into it.

BTW. The smoketest just finished. It ended with: 

c:\Perl\src\run>smokecurrent.cmd
mkdir : No such file or directory at lib\archiverpt.pl line 115

[download]

I saw an option during configuration asking about archiving, I selected the default which I think was 'Don't keep an archive'. Does that explain the above message? Or has something failed that invalidates the test?

I was antisipating seeing some message telling me what to send where to complete the process, but I haven't. So, what should I be sending and where?

Note: I chose not to configure an email address during the setup. I don;t like automated transmissions--I like to know what is being sent--does that screw things up?

Phew! 9 hours and about 200 manual interventions. And I'm meant to do this daily?

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
"Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."

In reply to Re^17: 5.10 imminent? by BrowserUk
in thread 5.10 imminent? by BrowserUk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.