The Linux / mbedtls job fails here. Was that just a temporary glitch or is this PR making it fail?

The Linux / mbedtls job fails here. Was that just a temporary glitch or is this PR making it fail?

I don't know, it looked so. The first commit could not interrupt mbed_connect_step2() because the result of collect_server_cert() was ignored, hence it could not fail the tests.

tests/http/test_10_proxy.py::TestProxy::test_10_02_proxys_down[0-http/1.1] FAILED [ 63%]
tests/http/test_10_proxy.py::TestProxy::test_10_02_proxys_down[0-h2] FAILED [ 63%]
tests/http/test_10_proxy.py::TestProxy::test_10_14_proxys_ip_addr[0-http/1.1] FAILED [ 82%]
tests/http/test_10_proxy.py::TestProxy::test_10_14_proxys_ip_addr[0-h2] FAILED [ 82%]

I am experimenting with what is wrong with the proxy tests on Linux/mbedtls. I've disabled SSLSUPP_CERTINFO and got the tests passed. All looks well in other tests, I might miss something in other files.

I will fix and finish this PR. Just I am getting troubles with running and debugging the python tests locally.

I think you want something like this?

diff --git a/tests/test1275.pl b/tests/test1275.pl
index 47ce799578..353391d2f3 100755
--- a/tests/test1275.pl
+++ b/tests/test1275.pl
@@ -30,10 +30,11 @@ my @m = `git ls-files -- $root`;
 my $errors;
 
 my %accepted=('curl' => 1,
               'libcurl' => 1,
               'macOS' => 1,
+              'mbedTLS' => 1,
               'c-ares' => 1);
 
 sub checkfile {
     my ($f) = @_;
     chomp $f;

Thanks!