This test uses a failpoint now that doesn't exist in v4.4. This test should be either:

1. blacklisted from multiversion suites,
2. special cased for the specific check that uses the failpoint, so as to not run that check in multiversion suites.