At 8:11 PM +0100 11/13/04, Abe Timmerman wrote: >I realize i have been sending my smokereports to this list without even asking >what the policy/opinion is. > >So I'll ask now. >>From Test::Smoke there are three options: >1) always (PASS or FAIL) (current setting) >2) only on FAIL >3) never > >Please let me know what you want!
Personally I would vote for always, at least until we get more of the kinks worked out of Test::Smoke. For the benefit of vmsperlers who may not know what the fuss is about, these automated test reports allow the committers to know within a matter of hours how code changes checked into the repository affect the test results on a whole range of platforms with various configurations. Until now, this has not been available on VMS, so we've depended on my manual tests to know how things stand. Abe has gotten things pretty far and even seems to be brave enough to do a little DCL :-). I think there is some additional work to do, though. For example, I don't think Test::Smoke knows how to add qualifiers to MMS or MMK, such as with the /MACRO="__DEBUG__"=1 case to do a vmsdebug build. I also see tests failing when I know they pass outside of Test::Smoke. So we are getting close but there is more to do. -- ________________________________________ Craig A. Berry mailto:[EMAIL PROTECTED] "... getting out of a sonnet is much more difficult than getting in." Brad Leithauser
