comment on

(OK, this only vaguely fits in 'seekers', but there's no 'volunteer help wanted' section :)

So far it appears that the work for the new Test::Harness is going really well. There are a couple of bumps, but nothing major we know of ... except VMS (and maybe z/OS). Abe Timmerman has been sending us test runs, but what we really need is for someone with access to VMS to either have the time to debug some of the issues or allow Andy Armstrong remote login access.

Right now it mainly looks like issues with the wait status and the fact that VMS doesn't fork (not a big deal for us, really). These things should be easy to fix, but doing so remotely isn't working.

If you might be able to help, reply here or sign up for the TAP::Parser developers list.

Cheers,
Ovid

New address of my CGI Course.

In reply to Needing VMS shell access or a VMS volunteer! by Ovid

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


No such thing as a small change
	PerlMonks