-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Infrastructure
-
None
-
Python Drivers
-
None
-
None
-
None
-
None
-
None
-
None
Context
PYTHON-6282 tracks the shrub.py fix for EvgTask dropping unknown keywords such as allowed_requesters. Two places in .evergreen/scripts/generate_config.py wait on it:
- backport-pr passes allowed_requesters=["commit"]; shrub.py drops it, so the generated task runs for any requester, patch builds included.
- The PYTHON-6178 review (PR #3215) split fuzzing into two variants because a single task cannot be kept off PR builds: PR builds run every task a pr-tagged variant selects. fuzz-regression-rhel8 (pr) covers PRs; fuzz-rhel8 (untagged, batchtime: 1440) covers nights.
Definition of done
- Bump the shrub.py requirement to a release with the PYTHON-6282 fix.
- Regenerate the config so the backport-pr task carries allowed_requesters: [commit].
- Collapse fuzzing back to one pr-tagged variant; the nightly fuzz task carries allowed_requesters: [commit, patch] so PR builds skip it, manual evergreen patch runs keep working, and batchtime keeps the nightly cadence.
- test_generate_config.py asserts both restrictions.
Pitfalls
- An older shrub.py silently drops the restrictions again; the requirement bump guards that.
- Keep patch in the allowlist; patchable: false would block manual runs too.
- The regression task must keep running on every PR; the nightly allowlist is the only thing keeping it off PRs.
- Excluding merge is intended: commit-queue checks should not pay 15 minutes of fuzzing.
- depends on
-
PYTHON-6282 shrub.py silently drops allowed_requesters from task definitions
-
- In Code Review
-