-
-
Notifications
You must be signed in to change notification settings - Fork 30.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
test_imaplib
takes 40+ minutes in refleaks builds
#120048
Comments
colesbury
added
type-bug
An unexpected behavior, bug, or error
tests
Tests in the Lib/test dir
labels
Jun 4, 2024
colesbury
added a commit
to colesbury/cpython
that referenced
this issue
Jun 4, 2024
The `test_imaplib` was taking 40+ minutes in the refleak build bots because we were using LOOPBACK_TIMEOUT for tests cases that expect to timeout. LOOPBACK_TIMEOUT scales with the global timeout. We should use a fixed, very small timeout for cases that we expect to timeout.
colesbury
added a commit
that referenced
this issue
Jun 4, 2024
The `test_imaplib` was taking 40+ minutes in the refleak build bots because the tests waiting on a client `self._setup()` was creating a client that prevented progress until its connection timed out, which scaled with the global timeout. We should set `connect=False` for the tests that don't want `_setup()` to create a client. Co-authored-by: Serhiy Storchaka <[email protected]>
miss-islington
pushed a commit
to miss-islington/cpython
that referenced
this issue
Jun 4, 2024
The `test_imaplib` was taking 40+ minutes in the refleak build bots because the tests waiting on a client `self._setup()` was creating a client that prevented progress until its connection timed out, which scaled with the global timeout. We should set `connect=False` for the tests that don't want `_setup()` to create a client. (cherry picked from commit 710cbea) Co-authored-by: Sam Gross <[email protected]> Co-authored-by: Serhiy Storchaka <[email protected]>
miss-islington
pushed a commit
to miss-islington/cpython
that referenced
this issue
Jun 4, 2024
The `test_imaplib` was taking 40+ minutes in the refleak build bots because the tests waiting on a client `self._setup()` was creating a client that prevented progress until its connection timed out, which scaled with the global timeout. We should set `connect=False` for the tests that don't want `_setup()` to create a client. (cherry picked from commit 710cbea) Co-authored-by: Sam Gross <[email protected]> Co-authored-by: Serhiy Storchaka <[email protected]>
This was referenced Jun 4, 2024
colesbury
added a commit
that referenced
this issue
Jun 4, 2024
The `test_imaplib` was taking 40+ minutes in the refleak build bots because the tests waiting on a client `self._setup()` was creating a client that prevented progress until its connection timed out, which scaled with the global timeout. We should set `connect=False` for the tests that don't want `_setup()` to create a client. (cherry picked from commit 710cbea) Co-authored-by: Sam Gross <[email protected]> Co-authored-by: Serhiy Storchaka <[email protected]>
colesbury
added a commit
that referenced
this issue
Jun 4, 2024
The `test_imaplib` was taking 40+ minutes in the refleak build bots because the tests waiting on a client `self._setup()` was creating a client that prevented progress until its connection timed out, which scaled with the global timeout. We should set `connect=False` for the tests that don't want `_setup()` to create a client. (cherry picked from commit 710cbea) Co-authored-by: Sam Gross <[email protected]> Co-authored-by: Serhiy Storchaka <[email protected]>
barneygale
pushed a commit
to barneygale/cpython
that referenced
this issue
Jun 5, 2024
The `test_imaplib` was taking 40+ minutes in the refleak build bots because the tests waiting on a client `self._setup()` was creating a client that prevented progress until its connection timed out, which scaled with the global timeout. We should set `connect=False` for the tests that don't want `_setup()` to create a client. Co-authored-by: Serhiy Storchaka <[email protected]>
noahbkim
pushed a commit
to hudson-trading/cpython
that referenced
this issue
Jul 11, 2024
The `test_imaplib` was taking 40+ minutes in the refleak build bots because the tests waiting on a client `self._setup()` was creating a client that prevented progress until its connection timed out, which scaled with the global timeout. We should set `connect=False` for the tests that don't want `_setup()` to create a client. Co-authored-by: Serhiy Storchaka <[email protected]>
estyxx
pushed a commit
to estyxx/cpython
that referenced
this issue
Jul 17, 2024
The `test_imaplib` was taking 40+ minutes in the refleak build bots because the tests waiting on a client `self._setup()` was creating a client that prevented progress until its connection timed out, which scaled with the global timeout. We should set `connect=False` for the tests that don't want `_setup()` to create a client. Co-authored-by: Serhiy Storchaka <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug report
Similar to #120039,
test_imaplib
has at least one test that expects a timeout and that time out is scaled up with the global time out, so the refleaks tests unnecessarily take 40+ minutes.cpython/Lib/test/test_imaplib.py
Lines 116 to 117 in 4dcd91c
cpython/Lib/test/test_imaplib.py
Lines 461 to 472 in 4dcd91c
Linked PRs
test_imaplib
faster #120050test_imaplib
faster (GH-120050) #120069test_imaplib
faster (GH-120050) #120070The text was updated successfully, but these errors were encountered: