*Most* implementations of ContentHandler::fillParserOutput() ensure that the returned ParserOutput has had ParserOutput::resetParseStartTime() called on it at an appropriate time -- but not *all*. This is a belt-and-suspenders fix that ensures that every code path which creates a ParserOutput has *some* "start time" defined. This could be misleading if the parsing is done first and the parser output is created at the very end of the parse, but in all the code that I've looked at the ParserOutput is the first thing created and so this default should be reasonable. While we're at it, remove the parseStartTime from the serialized form of the ParserOutput, because it is useless after the object is unserialized. Bug: T376433 Change-Id: I3bdf3996401a7d5ac4d8e1e5e6afb7ca410cbe6c |
||
|---|---|---|
| .. | ||
| BlobStoreFactoryTest.php | ||
| EditResultBuilderTest.php | ||
| EditResultCacheTest.php | ||
| EditResultTest.php | ||
| PageUpdaterFactoryTest.php | ||
| PageUpdateStatusTest.php | ||
| PreparedEditTest.php | ||
| RevertedTagUpdateManagerTest.php | ||
| RevertedTagUpdateTest.php | ||