Yes, it is, but parts of the test suite are failing for both the tip of enzo-dev and for the MHD-CT fork (albeit in exactly the same way, and with the same values, so it's not because of the MHD-CT). So, it needs to be updated. That said, I do think it's good to mention what results have changed and so on.
My point was, why update now when it will have to be updated when mhdct merged in? That isn't a problem if this new version contains those new tests.
Sam has convinced me that it's not terribly useful to use the amazon gold standard for regression testing, it's much better to generate your own local gold standard on a known working changeset and then compare with that.