-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Reduce Windows runtime duration of some linkcheck tests by enabling timeouts #14133
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
Reduce Windows runtime duration of some linkcheck tests by enabling timeouts #14133
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
|
@AA-Turner @FazeelUsmani I usually focus intensely on pointless annoying quirks/puzzles such as this one until I find some kind of answer -- in this case, I am really, really struggling to figure out why the I've tested a bunch of theories and attempted various things to try to narrow it down -- and I still don't even have a sense of what the factor that affects it is. I don't know whether it's worth spending much/any time on, but if you do have a few moments, I'd be glad for your help and ideas. |
|
Perhaps I've been too focused on what does exist within the scope of this test case -- without stopping to consider what doesn't exist in it, but is found in the other Specifically: I am thinking of the presence of |
|
Self-quoting, and cc @FazeelUsmani @AA-Turner:
Yes, the absence of the This may affect a few other |
|
Requested $ grep -o "testroot='[a-z\-]*'" tests/test_builders/test_build_linkcheck.py | sort | uniq -c
2 testroot='linkcheck'
1 testroot='linkcheck-anchors-ignore'
1 testroot='linkcheck-anchors-ignore-for-url'
1 testroot='linkcheck-case-check'
18 testroot='linkcheck-localserver'
3 testroot='linkcheck-localserver-anchor'
6 testroot='linkcheck-localserver-https'
1 testroot='linkcheck-localserver-warn-redirects'
1 testroot='linkcheck-raw-node'
1 testroot='linkcheck-too-many-retries'
6 testroot='root'Configured $ grep -rwl linkcheck_timeout tests/roots | sort
tests/roots/test-linkcheck-anchors-ignore-for-url/conf.py
tests/roots/test-linkcheck-anchors-ignore/conf.py
tests/roots/test-linkcheck-case-check/conf.py
tests/roots/test-linkcheck-documents_exclude/conf.py
tests/roots/test-linkcheck-localserver-anchor/conf.py
tests/roots/test-linkcheck-localserver-https/conf.py
tests/roots/test-linkcheck-localserver-warn-redirects/conf.py
tests/roots/test-linkcheck-localserver/conf.py
tests/roots/test-linkcheck-raw-node/conf.py
tests/roots/test-linkcheck-too-many-retries/conf.py
tests/roots/test-linkcheck/conf.pySo: I think the only other affected testroot -- that would benefit the test suite duration on Windows by enabling |
|
Result from commit 2e81411: one test, I'll rebase the |
2e81411 to
d57aec6
Compare
|
Timeouts were first added in 97f07ca (several subsequent commits tweak the values). A |
|
Thanks @AA-Turner 👍 |
Purpose
This pull request is an experiment to prove/disprove a theory I have about the reason for some recently-added
linkcheckbuilder case sensitivity tests taking unexpectedly long durations of time (4 seconds plus) to run on Windows in GitHub Actions CI.I think that there may be some network/resource-cleanup side-effects from calling
socket.setdefaulttimeoutin an earlier test -- and I would like to confirm whether this is the case, and also if it is, then whether we can undo the effects of that (and/or report upstream if it is not already a known problem).Result: the theory was disproven; the
socket.setdefaulttimeoutis not the direct cause. The absence of configuredlinkcheck_timeoutsettings for thelinkcheck-case-checkwas determined to be the fault.To reduce the cost of this experiment, non-Windows GitHub Actions CI workflows and jobs are disabled.References