Oh. I forgot that I doubled the ASAN buildbot last week: python/buildmaster-config@5a37411

    # Sometimes test_multiprocessing_fork times out after 15 minutes
    test_timeout = TEST_TIMEOUT * 2

Lib/test/libregrtest/setup.py adapts SHORT_TIMEOUT to --timeout option:

        # For a slow buildbot worker, increase SHORT_TIMEOUT and LONG_TIMEOUT
        support.SHORT_TIMEOUT = max(support.SHORT_TIMEOUT, ns.timeout / 40)

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?

cc @pablogsal

I'm ok not changing the default. I'm convinced by @sobolevn comments 👍

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?

I have no idea. I checked and the builder should have picked the change you talk about but maybe I have missed something :(

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?

I've added the information about the timeout to the error message. It can probably help the next time we have the same problem.

Closes #31205 Thank you, @notarealdeveloper for noticing it!

However, I am not sure how to proceed here:

• We can merge [bpo-46679: Don't ignore timeout argument in test.support.wait_process. bpo-46679: Don't ignore timeout argument in test.support.wait_process. #31205](bpo-46679: Don't ignore timeout argument in test.support.wait_process. #31205) first, then I rebase this PR (this way the original author will get a credit for fixing the problem)
• Or we can just merge this one (it is easier)

https://bugs.python.org/issue46711

@sobolevn No worries! I don't mind not getting credit. :) This was just a minor thing I noticed while working on #30310.