See this Slack discussion for more detail. Currently the task name is shown at the top level of patch build UI, but I think showing the suite name would be more useful, as suite name is relevant for reproducing the failure via resmoke.py whereas task name is an internally generated name (that often, but not always, matches the suite name).

Maybe there are still reasons not to do this, like it would create too many aliases on the UI display.

Original description:

The Evergreen patch build UI shows at least the following nonexistent suite names:

• noPassthrough
• noPassthroughWithMongod

The correct names of these two suites are:

• no_passthrough
• no_passthrough_with_mongod

Showing nonexistent names makes it hard for developers to reproduce these failures, as they need the correct suite name for the resmoke.py --suite flag or they get a failure like:

[resmoke] 22:50:16.883Z verbatim resmoke.py invocation: build/install/bin/resmoke.py run --installDir build/install/bin --dbpathPrefix /home/ubuntu/data --suite=noPassthroughWithMongod jstests/noPassthroughWithMongod/now_variable.js
...
[resmoke] 22:50:17.041Z Failed to parse YAML suite definition: Unknown suite 'noPassthroughWithMongod'
[resmoke] 22:50:17.041Z Suites available to execute:
aggregation
aggregation_auth
aggregation_column_store_index_passthrough
...
no_passthrough
no_passthrough_with_mongod
...
vector_search
watchdog
write_concern_majority_passthrough
[resmoke] 22:50:17.041Z Exiting with code: 1

There are 369 suites in the output list, making it non-trivial for a developer to find the correct suite.