Skip to content

Async test runner for comparison#1

Closed
dave-shawley wants to merge 7 commits intomasterfrom
async-test-runner
Closed

Async test runner for comparison#1
dave-shawley wants to merge 7 commits intomasterfrom
async-test-runner

Conversation

@dave-shawley
Copy link
Copy Markdown
Owner

No description provided.

This is the core of running a test.  It is also the portion of run()
that requires specialization for asyncio support.
This method is essentially ``_runTest`` with a Outcome object that does
nothing.  This commit inserts a new class that is a no-op Outcome so
that the method can be re-used.
This makes AsyncioTestCase.doCleanups() safe to call at any time.  The
previous version terminated the event loop unnecessarily.
@dave-shawley dave-shawley deleted the async-test-runner branch November 2, 2018 10:43
dave-shawley pushed a commit that referenced this pull request Mar 5, 2023
The existing volatile `left`/`right` pointers guarantee that the reads will all occur, but does not guarantee that they will be _used_. So a compiler can still short-circuit the loop, saving e.g. the overhead of doing the xors and especially the overhead of the data dependency between `result` and the reads. That would change performance depending on where the first unequal byte occurs. This change removes that optimization.

(This is change GH-1 from https://bugs.python.org/issue40791 .)
(cherry picked from commit 3172936)

Co-authored-by: Devin Jeanpierre <jeanpierreda@google.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant