Skip to content
This repository was archived by the owner on Oct 12, 2022. It is now read-only.

Run more test_concurrent_futures tests#10

Closed
paulproteus wants to merge 1 commit into
beeware:devfrom
paulproteus:run-more-test-concurrent-futures-tests
Closed

Run more test_concurrent_futures tests#10
paulproteus wants to merge 1 commit into
beeware:devfrom
paulproteus:run-more-test-concurrent-futures-tests

Conversation

@paulproteus

Copy link
Copy Markdown
Contributor

In the process, call quilt push -a, which pushes all patches,
which is what I meant to do originally.

This imports a fix for https://bugs.python.org/issue40692 aka
python/cpython#20239
that hasn't been formally reviewed yet, but seems reasonable
to me.

It mostly only changes the test suite, but it does also fix
the compileall module in a tiny but useful way.

In the process, call `quilt push -a`, which pushes all patches,
which is what I meant to do originally.

This imports a fix for https://bugs.python.org/issue40692
that hasn't been formally reviewed yet, but seems reasonable
to me.

It mostly only changes the test suite, but it does also fix
the `compileall` module in a tiny but useful way.
@paulproteus
paulproteus requested a review from freakboy3742 May 22, 2020 05:07
@paulproteus
paulproteus marked this pull request as draft May 22, 2020 05:50
@paulproteus

Copy link
Copy Markdown
Contributor Author

I've marked this a draft because in my testing of this with the CPython test suite, the tests all print that they passed, but then at the end, something prints that a thread has timed out waiting 2 minutes, and then kills the Python interpreter. I think. It's confusing. I need to repro. I may as well repro & report back before we merge this.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants