Use plaintext for connectivity test

[WyriHaximus]

By using plaintext for connectivity testing instead of a DB related one we rule out any issues related to the database while checking if the server is up

[joanhey]

Please don't touch the toolset.
You can test any url individually.

./tfb --help

./tfb --mode verify --test reactphp --type plaintext

[joanhey]

This change breaks all tests.

[WyriHaximus]

Ok then how can I change which test to use for this check for the ReactPHP bench mark?

[WyriHaximus]

Please don't touch the toolset. You can test any url individually.

./tfb --help

./tfb --mode verify --test reactphp --type plaintext

Sure, but that isn't listed on this repos readme, and when running the tests with ./tfb --mode verify --test reactphp mentioned there it just fails. Looking for a way to see this instead:

[joanhey]

For run all the tests, start with the db test, and reactphp start to be blocked.

Never send a response, not even a 500 error, only show the errors (if configured) in the shell.
Without responses never will continue the tests, as is waiting for them, and even still will fail the rest of tests.

[joanhey]

I need to stop with ctrl+c, because is blocked there and the tests reject it after some time.
Before was worst, as don't show any error in the shell, but it was blocked.

PD: that's before in the run

https://tfb-status.techempower.com/unzip/results.2025-01-10-22-35-37-339.zip/results/20250104202231/reactphp/run/reactphp.log

[joanhey]

Also if the error is for not connect to the database, it'll be good that show that: "Error connecting to the database". And return a 500 error.

[joanhey]

Mysql versions:

So Reactphp started to fail after the update to Mysql 8.4, even with enabled mysql-native-password.
But it'll be good if fail in a more informed way.

PD: check #9009 #9175 #9183

[WyriHaximus]

For run all the tests, start with the db test, and reactphp start to be blocked.

Never send a response, not even a 500 error, only show the errors (if configured) in the shell. Without responses never will continue the tests, as is waiting for them, and even still will fail the rest of tests.

Fair, I'll have a look at fixing that. But I still think, connection tests should use the simplest end point possible to avoid complexity.

[WyriHaximus]

Mysql versions:

So Reactphp started to fail after the update to Mysql 8.4, even with enabled mysql-native-password. But it'll be good if fail in a more informed way.

PD: check #9009 #9175 #9183

Postgres is also support for the benchmarks from what I've seen. Will have a look at switching it to that