Thanks for the response.

http://search.frontier.com/search/?q=http://somewhere.example/myiframe&t=0

Ahh. It's not actually on my system: the same thing happens both on my phone thru WiFi at home, or on my PC. Based on the URL of frontier.com, my ISP is apparently "helping me" by injecting their search when I try to go to a domain that doesn't exist -- probably because I'm using their DNS. (The same thing happens whether through a browser on my PC, or whether on my phone thru wifi; if I switch my phone to just use its data plan, it properly tells me the domain somwehere.example doesn't exist.) Do you think that changing my DNS to a public server rather than my ISP's DNS server would get around this? I'll probably try that at some point

Sorry for not seeing the ::Troublshooting docs: I didn't see it linked from the main POD or the ::Installing POD, so didn't notice it was in there. I now see it on the main https://metacpan.org/release/CORION/WWW-Mechanize-Chrome-0.27 page, though I'm not sure I would have noticed if I didn't know there was a page named ::Troubleshooting. I guess I need to read documents more thoroughly.

I have AnyEvent installed and Log::Lo4perl as well

That probably would have helped me. I wonder why AnyEvent doesn't seem to be problematic for you, when it is for me.

"lie"

That was too strong of a word on my part -- I put it in quotes to try to imply that "lie" wasn't exactly what I meant. I just don't like it when I see a "clean" cpantesters report, and it turns out it's because all the functionality testing is skipped because of missing external components. But since external components cannot be made pre-reqs, I guess there's not much that can be done on smoke testers machines. I wish more users would report their install successes and failures to cpantesters, so we can see more "practical" installs. Thanks for pointing out the travis-ci/appveyor results: I should have thought of looking for those.

Are there any "true" failure modes -- ie, failures with your module, rather than weird system/ISP setups -- that would give a result of "3" instead of "2"? Or would it be possible to pass "2" or "3" as valid? if it really is my ISP's DNS doing it to me, then ISP=Frontier might mess up other Perl users, and there might be other ISPs who do it similarly to other people. (I mean, I know I'm not the only Frontier user in the world, though I may be the only Frontier user who also uses Perl (highly unlikely).)

Why would you want to delete that test run from CPAN testers?

since it's an invalid failure ("oops, my bad, nothing actually wrong with your module"), I guess I'd like to be able to erase that "strike" against your otherwise clean cpantesters matrix.