WIP: test(forge): the pr create check expects the edit that allows maintainer edits #926
No reviewers
Labels
No labels
area/accessibility
area/audio
area/input
area/install
area/menu
area/renderer
area/saves
area/tooling
area/upscaling
ci: approved
good first issue
gpu/amd
gpu/igpu
gpu/intel
gpu/nvidia
help wanted
kind
bug
kind
chore
kind
docs
kind
feature
kind
performance
kind
question
needs measurements
platform/linux
platform/macos
platform/steam-deck
platform/windows
preview
priority
critical
priority
high
priority
low
regression
risk
high
risk
low
risk
medium
status
blocked
status
confirmed
status
duplicate
status
invalid
status
needs-info
status
wontfix
testing wanted
ci: approved
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Longshot!926
Loading…
Reference in a new issue
No description provided.
Delete branch "zeldaootr/Longshot:forge-pr-check-maintainer-edit"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Type: test · Risk: low · Tested on: Linux, game-free checks · Needs: none
Why
test_forge_prfails onmainsincepr createturns on "Allow edits from maintainers"(#905): every create now edits the PR once more, and one case
still counted the old writes. A red check on
mainhides new failures in every PR that touches the forge script.How to reproduce
Seen on: Linux, any PC (no game, no GPU)
Settings and switches: defaults
Steps:
python -I -B tests/test_forge_pr.pyonmainc45be62fExpected: all cases pass
Actual:
test_create_draft_is_the_default_and_wip_is_not_doubledfails:['POST', 'PATCH', 'POST', 'PATCH'] != ['POST', 'POST', 'PATCH']What changed
The case now expects what
pr createdoes: an edit after each create, both turning onallow_maintainer_edit, andthe description in the edit only where the template was filled in.
test_create_draft_is_the_default_and_wip_is_not_doubledintests/test_forge_pr.pychecks each write'smethod and fields, and that every edit allows maintainer edits.
Measurements
Verdict: nothing to measure: a game-free check, the game doesn't run it.
Flags and settings
None
Testing
Tested: Linux:
tests/test_forge_pr.pyfails onmainc45be62f(the case above) and passes here, 32 of 32;test_forge_session_lockpasses. With #831 merged on top, all37 of
test_forge_prpass.Not tested: the rest of
tests/run_all.py(this changes one case of one check, nothing else reads it).Must be tested:
Risks
What could break: Nothing: a test's expectation.
Turning it off: revert the commit
Compatibility: Nothing changes
Checklist
Everyone
type(scope): description) of the status line's type.main. Onmainc45be62f.python -I -B tests/run_all.pypasses (any failure that also fails onmainis named). Not run in full yet: only the forge checks.third_party/untouched (a new folder with aPROVENANCE.mdinstead).When it applies
Assisted-by:/Co-Authored-By:trailers.tests/that reads changed source updated in this PR, not weakened.Closing:
tests/test_forge_pr.pymoved to MagicBeanDev/Tooling with #915, and Tooling's copy already expects the edit that allows maintainer edits (MagicBeanDev/Tooling#2). Nothing left to fix here.Pull request closed