Currently we are working on the solution for upgrade/downgrade for durable history. We need to control what state the database is in when going from 4.4 to 4.2 (it needs to have had a clean shutdown) and between 4.4 <-> 4.0 ( in this case the database ends up in corruption). There are more cases than we anticipated. While we are working on this solution, we would like to efficiently use our time in triaging as well, so it is better we could cut down the noise from the known failures.

In this direction we would like to disable multiversion & multiversion_auth tests from evergreen.