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
80-test_cmp_http.t: Prevent hangs on server not launching/behaving correctly, Improve the way the test server is launched and killed #15642
Conversation
49eab56
to
554536a
Compare
Maybe have the server write it's process ID into a file in the test-runs directory. I am surprised that this is so complicated, given that the TLSProxy etc do not have these problems. |
This appears to now cause a few more infinite loops.. |
554536a
to
89c1723
Compare
That's a good thought, thank you - I now let the server simply emit its PID along with the ACCEPT string. |
These are gone now :) |
TLSProxy doesn't start the subprocess with an It's also possible that using perl's IPC modules directly would be better in the longer run. I don't know, I've never done that myself, but that might be something worth looking into at some point. (also gotta be careful that the modules used are perl's core modules since version n5.10) |
We already have that in |
89c1723
to
5b1456a
Compare
NIce that this is now done automatically by calling |
I think this PR is good state now. |
Please rebase this on top of a fresh master. I would say that the approvals stand |
rel2abs() doesn't clean the path well enough, which may lead to odd results when calculating new paths. abs_path() works better for this sort of thing.
…g/behaving correctly
5b1456a
to
98287d8
Compare
Done (though there is not even a real merge conflict with commit 8e2b2336fb). |
24 hours has passed since 'approval: done' was set, but as this PR has been updated in that time the label 'approval: ready to merge' is not being automatically set. Please review the updates and set the label manually. |
For some reason, that commit hadn't made its way to github... now it has. |
I think I just referred to an outdated commit ID, which must have changed due to rebasing - sorry for the confusion. |
No, you didn't. That commit hadn't travelled from OpenSSL's main repository (which isn't on github) to github (openssl/openssl is just a mirror). I had to push that manually. |
…g/behaving correctly Reviewed-by: Paul Dale <pauli@openssl.org> (Merged from #15642)
…illed Reviewed-by: Paul Dale <pauli@openssl.org> (Merged from #15642)
Merged - thanks |
…g/behaving correctly Reviewed-by: Paul Dale <pauli@openssl.org> (Merged from openssl#15642)
…illed Reviewed-by: Paul Dale <pauli@openssl.org> (Merged from openssl#15642)
This is a follow-up of #15580, picking up loose ends discussed there.
This should have help diagnosing tricky issues such as Test test_cmp_http failed with icc build #15557 and Test 80-test_cmp_http fails at alpha17 on NonStop x86/ia64 (round 2) #15571.
This should fix test/recipes/80-test_cmp_http.t: Simplify test_cmp_http() #15580 (comment).