ExportXMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 9.1.0-rc0, 9.1.0-rc1025
    • Affects Version/s: None
    • Component/s: None
    • None
    • DevProd Test Infrastructure
    • Fully Compatible
    • DevProd Test Infra 2026-11-03
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Bumps setup_mongo_task_generator in evergreen/prelude_mongo_task_generator.sh from v3.9.0 to v3.10.0, used by evergreen/generate_version.sh and evergreen/generate_version_burn_in.sh.

      Picks up https://github.com/mongodb/mongo-task-generator/pull/123: generated tasks tagged requires_large_host are now routed to their build variant's large distro, matching the routing the variant's task selectors give static tasks carrying the tag. Previously only the explicit use_large_distro gen-task var was honored, so tag-only burn-in tasks (e.g. burn_in:search* on AUBSAN variants) ran on the default distro instead of xlarge and OOMed the hosts.

      Risk: low — changes only the generator binary version; v3.10.0's only behavior change is the tag routing above (plus matching the tag implies large distro during generation, which fails generation loudly rather than silently undersizing if a variant lacks a large_distro_name; escape hatch via build_variant_large_distro_exceptions in mongo-task-generator's etc/generate_subtasks_config.yml).

      Testing: validated as EVG patch 6abaec6bf5e7610007695562 (mongodb-mongo-master, base b96c6b6ba05): generation succeeded, tagged burn_in:search* tasks on AUBSAN variants moved to rhel8.8-xlarge (previously rhel8.8-large), and untagged tasks correctly stayed put.

            Assignee:
            Steve McClure
            Reporter:
            Steve McClure
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: