-
Type:
Bug
-
Resolution: Done
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Testing Infrastructure
-
None
-
DevProd Build
-
ALL
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
-
None
This was caused by the changes from 41077f8 as part of SERVER-97696. The YAML syntax
tasks:
- name: compile_ninja_quick_TG
- amazon2-arm64-latest-nvme
is interpreted as the combined string
{'tasks': [{'name': 'compile_ninja_quick_TG - amazon2-arm64-latest-nvme'}]}
It looks like this isn't considered an error despite not being the name of an Evergreen task. Perhaps it is being interpreted as an Evergreen task tag selector instead?
$ evergreen validate etc/evergreen.yml ... WARNING: buildvariant 'amazon-linux2-arm64-static-compile' has unmatched selector: 'compile_ninja_quick_TG - amazon2-arm64-latest-nvme', '.release_critical .requires_compile_variant .requires_large_host !.incompatible_development_variant !.stitch !.crypt', '.default .requires_compile_variant .requires_large_host !.incompatible_development_variant' WARNING: buildvariant 'amazon-linux2-arm64-static-compile' has unmatched criteria: '-', 'amazon2-arm64-latest-nvme'
Hopefully we can additionally improve the Evergreen YAML project configuration validation rules to avoid these kind of mistakes.
- is caused by
-
SERVER-97696 Run archive_jstestshell tasks on nvme systems
-
- Closed
-
- is related to
-
SERVER-86530 Make evergreen validate have zero lint warnings for etc/evergreen.yml and etc/evergreen_nightly.yml
-
- Investigating
-