Motivation & Background

There are multiple tests failing on the Evergreen waterfall, labeled under:

• failing-on-waterfall
• flaky-tests

When these are determined not to require an immediate fix, this causes two problems:

1. The failures reduce the number of tests run on Evergreen. Non-Windows tasks in Evergreen run test-libmongoc with the --no-fork options. They abort on the first test failure.
2. It slow downs the development process. Authors and reviewers need to inspect logs on Evergreen patches to determine whether their changes have introduced new failures.

Scope

• Investigate and decide how to skip individual tests in test-libmongoc.
• Add a workflow for opting in to skip individual tests run on Evergreen.