I don't know how many people do fully automated smoking (unattended, e.g., killing off ones which prompt or loop after a time etc) but I just use CPAN::Reporter::Smoker as I like to be able to see exactly what is going on. My list of modules which prompt or loop or consume all memory etc is growing like mad (over 180 now). I can't help feeling I should be doing more than just ignoring these. The reasons I have gathered so far are:
o prompts unnecessarily (sometimes just to warn you about something e.g., there is one module which forces you to acknowledge it is unsupported). o prompts for location of library X o prompts to ask if you want feature X o prompts for something else without using "prompt" e.g., can't start firefox - start it manually and press a key o loops forever (often repeatedly saying can't do something only to do it again) o hangs o consumes all memory until my machine grinds to a halt o fails with deep recursion but for some reason the test does not spot this and it hangs Should I be reporting any of these? In most cases, I note the module and why I will add it to disabled.yml then ctrl/c it to move on to the next one. This of course, means that not even a report is sent - is there another way to do this? Martin
