CodSpeed Performance Report

Merging #10121 will not alter performance

_{Comparing christianwbrock:cwb/aiohttp_server_host_parameter (a00b2cb) with master (6200513)}

Summary

✅ 47 untouched benchmarks

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.75%. Comparing base (703ce61) to head (a00b2cb).
Report is 333 commits behind head on master.

@@            Coverage Diff             @@
##           master   #10121      +/-   ##
==========================================
- Coverage   98.76%   98.75%   -0.01%     
==========================================
  Files         122      122              
  Lines       36958    36954       -4     
  Branches     4408     4411       +3     
==========================================
- Hits        36500    36494       -6     
- Misses        311      313       +2     
  Partials      147      147              

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

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

❌ Failed to cleanly apply 7f8e2d3 on top of patchback/backports/3.12/7f8e2d35ad4d0d5fed82721060bafd1bafa264b8/pr-10121

Backporting merged PR #10121 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/7f8e2d35ad4d0d5fed82721060bafd1bafa264b8/pr-10121 upstream/3.12

4. Now, cherry-pick PR Add host parameter to aiohttp_server fixture (#10120) #10121 contents into that branch:

   $ git cherry-pick -x 7f8e2d35ad4d0d5fed82721060bafd1bafa264b8

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

   $ git cherry-pick -m1 -x 7f8e2d35ad4d0d5fed82721060bafd1bafa264b8

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Add host parameter to aiohttp_server fixture (#10120) #10121 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/3.12/7f8e2d35ad4d0d5fed82721060bafd1bafa264b8/pr-10121

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.