ExportXMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 9.0.0-rc1
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When an Evergreen command definition lacks a display_name, a CI failure emits only a generic message that names the command type but not which step failed:

      > Command 'subprocess.exec' in function 'run generated tests' (step 6.23 of 6) failed: process encountered problem: exit code 1.

      With a display_name set, the failing step is named, making failures far easier to locate:

      > Command 'subprocess.exec' ('multiversion exclude tags generate') in function 'run generated tests' (step 6.23 of 6) failed: ...

      Motivation — Build Failure (BF) automation: Beyond readability, the missing display_name blocks BF automation. A BF auto-closing rule cannot use a narrowed regular expression that matches exactly the failures on a specific command, because the generic message only contains the command type (e.g. subprocess.exec), which is shared by hundreds of unrelated steps — any regex keyed on it would over-match. With a display_name, the rule can key off the step's unique name and match precisely the intended failure.

      Proposed change: backfill display_name on the "generic runner" command types whose type name reveals nothing about what the step does — subprocess.exec, shell.exec, and generate.tasks. Self-describing types (s3.put, s3.get, git.get_project, manifest.load, expansions.update, …) are intentionally left out, since their type already identifies the step. Display names are derived from the script/binary each command runs.

      Scope: the functions: block of definitions.yml, the task files included by etc/evergreen.yml (compile/misc/coverity/resmoke task files), and the Atlas module configs (src/mongo/db/modules/atlas/atlas_dev.yml, src/mongo/db/modules/atlas/atlas_sls_pin_bump.yml). Two display_name fields that were misplaced inside params: (where Evergreen ignores them) are also relocated. ~142 additions across 11 files, validated with evergreen evaluate and yamllint.

      Out of scope / follow-up: separate Evergreen projects not owned by this team — WiredTiger (src/third_party/wiredtiger, ~116 commands) and Monguard (~36) — left for their owners.

      Related prior work: SERVER-86475.

            Assignee:
            Tommaso Tocci
            Reporter:
            Tommaso Tocci
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: