While investigating T114557, someone uploaded a new version of https://commons.wikimedia.org/wiki/File:The_President_Delivers_a_Statement_on_the_Shooting_in_Oregon.webm in the middle of testing, which I had to revert to finish testing.
There *appear* to have been transcode jobs from the previous version which survived the revert process, showing bogusly short encoding times like 42 seconds:
These appear to be being replaced over time with new transcodes from after the revert, but it's all very mysterious.
Ideal behavior is that uploading a new version should halt any running transcode jobs on old versions... but there's no infrastructure for halting jobs remotely. At the least, the existing job should cleanly die out when it finishes, or something.... argh. Need to run this in an isolated environment to make sure I can tell what's going on.