Small improvements to payload cleanup fixture

[bdraco]

#10915 (comment) #10915 (comment)

[codspeed-hq]

CodSpeed Performance Report

Merging #10943 will not alter performance

_{Comparing payload_cleanup_fixtures (94321af) with master (6512aaa)}

Summary

✅ 59 untouched benchmarks

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 98.77%. Comparing base (38c23ed) to head (94321af).
⚠️ Report is 3145 commits behind head on master.
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@            Coverage Diff             @@
##           master   #10943      +/-   ##
==========================================
+ Coverage   98.16%   98.77%   +0.60%     
==========================================
  Files         130      129       -1     
  Lines       39652    39458     -194     
  Branches     2240     2185      -55     
==========================================
+ Hits        38925    38973      +48     
+ Misses        555      337     -218     
+ Partials      172      148      -24     

Flag	Coverage Δ
CI-GHA	98.65% <100.00%> (+0.59%)	⬆️
OS-Linux	98.36% <100.00%> (+0.57%)	⬆️
OS-Windows	96.53% <100.00%> (+1.27%)	⬆️
OS-macOS	97.51% <66.66%> (+0.55%)	⬆️
Py-3.10.11	97.40% <100.00%> (+0.55%)	⬆️
Py-3.10.17	97.93% <100.00%> (+0.55%)	⬆️
Py-3.11.12	97.97% <100.00%> (+0.49%)	⬆️
Py-3.11.9	97.48% <100.00%> (+0.54%)	⬆️
Py-3.12.10	98.42% <100.00%> (+0.57%)	⬆️
Py-3.13.3	98.41% <100.00%> (+0.57%)	⬆️
Py-3.9.13	97.27% <100.00%> (+0.56%)	⬆️
Py-3.9.22	97.80% <100.00%> (+0.53%)	⬆️
Py-pypy7.3.16	97.36% <100.00%> (+0.54%)	⬆️
VM-macos	97.51% <66.66%> (+0.55%)	⬆️
VM-ubuntu	98.36% <100.00%> (+0.57%)	⬆️
VM-windows	96.53% <100.00%> (+1.27%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[patchback]

Backport to 3.12: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply b1e9462 on top of patchback/backports/3.12/b1e94620e2995d2d8f9f6dae5ea793e3279f04c2/pr-10943

Backporting merged PR #10943 into master

1. Ensure you have a local repo clone of your fork. Unless you cloned it
   from the upstream, this would be your origin remote.
2. Make sure you have an upstream repo added as a remote too. In these
   instructions you'll refer to it by the name upstream. If you don't
   have it, here's how you can add it:

   $ git remote add upstream https://github.com/aio-libs/aiohttp.git

3. Ensure you have the latest copy of upstream and prepare a branch
   that will hold the backported code:

   $ git fetch upstream
   $ git checkout -b patchback/backports/3.12/b1e94620e2995d2d8f9f6dae5ea793e3279f04c2/pr-10943 upstream/3.12

4. Now, cherry-pick PR Small improvements to payload cleanup fixture #10943 contents into that branch:

   $ git cherry-pick -x b1e94620e2995d2d8f9f6dae5ea793e3279f04c2

   If it'll yell at you with something like fatal: Commit b1e94620e2995d2d8f9f6dae5ea793e3279f04c2 is a merge but no -m option was given., add -m 1 as follows instead:

   $ git cherry-pick -m1 -x b1e94620e2995d2d8f9f6dae5ea793e3279f04c2

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Small improvements to payload cleanup fixture #10943 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/3.12/b1e94620e2995d2d8f9f6dae5ea793e3279f04c2/pr-10943

7. Create a PR, ensure that the CI is green. If it's not — update it so that
   the tests and any other checks pass. This is it!
   Now relax and wait for the maintainers to process your pull request
   when they have some cycles to do reviews. Don't worry — they'll tell you if
   any improvements are necessary when the time comes!

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.