Chris, There's nothing in the wiki to terribly detailed. It's just http://wiki.cpantesters.org/wiki/GettingStarted and http://wiki.cpantesters.org/wiki/SmokeTools. GettingStarted is the page which suggests the CPANPLUS route for automated testing without explaining further.
Regardless, you hit the nail on the head. I recently ran out of disk on the smoker and cleaned the build directories. It appears just adding the --indices switch to minismokebox should fix the problem. Is there a way to suppress NA and UNKNOWN reports? Thanks, Chad On Tue, Jul 9, 2013 at 2:53 PM, Chris 'BinGOs' Williams < ch...@bingosnet.co.uk> wrote: > On Tue, Jul 09, 2013 at 09:49:15AM -0400, Chad Thomas wrote: > > I merely setup my smoker following the instructions in the cpantesters > > wiki for CPANPLUS-YACSmoke. The wiki also seems to indicate > > that CPANPLUS-YACSmoke is the preferred choice for automated testing > > versus CPAN::Reporter. I'd appreciate any guidance on how to better > > configure my smoker to prevent spamming distribution developers with > these > > reports. > > Thanks, > > Chad Thomas > > Chad, could you send me the link to those instructions, I can't seem to > find them on the wiki right now. > > I might be able to comment further after I have seen these. > > One point which might have a bearing is that if you clear the CPANPLUS > build directory that you also reindex. As the indexes are accumulating > state, they do assume that there have been no changes to the state of > the build directories. This might be what is happening in your case. > > My smokers generate new indexes at the beginning of a smoke run, > and then no reindexing is done until they finish and the build dir > is then removed and so is the index file. > > -- > Chris Williams > aka BinGOs > PGP ID 0x4658671F > http://www.gumbynet.org.uk > ========================== >
