tests.unit.test_flow.TestInstalledAppFlow: test_run_local_server_audience failed #381
Assignees
Labels
flakybot: flaky
Tells the Flaky Bot not to close or comment on this issue.
flakybot: issue
An issue filed by the Flaky Bot. Should not be added manually.
priority: p3
Desirable enhancement or fix. May not be included in next release.
type: bug
Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Comments
flaky-bot
bot
added
flakybot: issue
|
Looks like this issue is flaky. 😟 I'm going to leave this open and stop commenting. A human should fix and close this. When run at the same commit (f0ea4c3), this test passed in one build (Build Status, Sponge) and failed in another build (Build Status, Sponge). |
|
sent in a pull request #394 to fix this |
|
Oops! Looks like this issue is still flaky. It failed again. 😬 I reopened the issue, but a human will need to close it again. commit: 9a1dfab |
sai-sunder-s
added
priority: p3
nolanleastin
added a commit
that referenced
this issue
Apr 1, 2025
tests.unit.test_flow.TestInstalledAppFlow attempts to create a new server at the specified host:port. New server creation occasionally results in 'address already in use' because the socket will be unavailable for a period of time after the socket is closed, resulting in flaky test failures. Work around this in the tests by letting the OS pick an available port each time. Fixes #381
nolanleastin
added a commit
that referenced
this issue
Apr 1, 2025
tests.unit.test_flow.TestInstalledAppFlow attempts to create a new server at the specified host:port. New server creation occasionally results in 'address already in use' because the socket will be unavailable for a period of time after the socket is closed, resulting in flaky test failures. Work around this in the tests by letting the OS pick an available port each time. Fixes #381
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Note: #308 was also for this test, but it was closed more than 10 days ago. So, I didn't mark it flaky.
commit: f0ea4c3
buildURL: Build Status, Sponge
status: failed
The text was updated successfully, but these errors were encountered: