The max_time_ms.js test utilizes the maxTimeNeverTimeOut failpoint. This failpoint overrides a maxTimeMS deadline set by any command, allowing them to run indefinitely. If there is an assertion failure in the test after the failpoint is enabled, we may run subsequent tests in a test fixture without disabling the failpoint. This can cause issues (i.e. hangs) in other tests that expect a command to time out with a maxTimeMS expiration. We should make the test robust to exceptions by making sure that we always disable the failpoint in the case of an error.