GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | ||||||||||||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | ||||||||||||||||||
GeezerVison is showing github.com — bpo-46711: increase timeout for `test_logging::test_post_fork_child_no_deadlock` by sobolevn · Pull Request #31274 · python/cpython Conversation
|
| lock_holder_thread.join() | ||
|
|
||
| support.wait_process(pid, exitcode=0) | ||
| support.wait_process(pid, exitcode=0, timeout=support.LONG_TIMEOUT) |
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Can you please change the default timeout in wait_process() instead?
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
I think it might have some consequences 🤔
Right now SHORT_TIMEOUT is just 30 seconds, while LONG_TIMEOUT is 5 minutes.
It is a 10x increase.
Secondly, current docs state (https://docs.python.org/3/library/test.html#test.support.SHORT_TIMEOUT):
If a test using SHORT_TIMEOUT starts to fail randomly on slow buildbots, use LONG_TIMEOUT instead.
Initially I've followed this recommendation.
Do we have other tests that fail due to this timeout? Is it a global problem? You totally have more data than me on this problem.
Lastly, regrtest has --timeout, which we can change for slower runners.
If you think that we still should change the default, I have several questions:
.. versionchanged:: 3.11 to wait_process docs and change the default value thereSHORT_TIMEOUT if users expect some test to be fast, am I right? Or should we just remove this from the docs completely?--timeout= flags that are used in the project somehow? https://cs.github.com/python/cpython?q=--timeout%3D
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Oh. I forgot that I doubled the ASAN buildbot last week: python/buildmaster-config@5a37411
So SHORT_TIMEOUT should now be 60 seconds rather than 30 seconds. Why did https://buildbot.python.org/all/#/builders/621/builds/466 fail at 52.5 seconds seconds in this case? Maybe my computation is wrong, or this build is older than the buildbot configuration change? |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
cc @pablogsal |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
I'm ok not changing the default. I'm convinced by @sobolevn comments 👍 |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
I have no idea. I checked and the builder should have picked the change you talk about but maybe I have missed something :( |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
I've added the information about the timeout to the error message. It can probably help the next time we have the same problem. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
@sobolevn No worries! I don't mind not getting credit. :) This was just a minor thing I noticed while working on #30310. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
The Lib/test/support/init.py change is nice. I'm no longer sure that the Lib/test/test_logging.py change is correct. Maybe revert test_logging.py change?
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.