without it. The idea of parserTests.php was to detect issues before commit, wasn't it? Not to wait a day for the email?
I would hope so. It appears the recent additions were aimed more at the audience of people who *do* wait for the emails, however, this should not prevent people who are working on the software from continuing to run regression tests when altering the parser.
Related to this, what might be useful is an IRC bot that sits on #mediawiki, and every time there was a commit, it would: * Run parserTests --record, and inform the channel of any tests whose status changes. * Run a check for Native EOL style, and inform the channel of any new files that needed native EOL style set. * Run a "php -l" lint-check over the code, and report back any failures.
Finding the above stuff before commit is best, although finding it immediately after a commit is probably the next best option.
-- All the best, Nick.