You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The issue of "Started but not completed" speed tests has been discussed in a couple of other tickets including the following: #1591
My request is that SpeedTest-Tracker shows the correct status for such failed tests, instead of just showing "Started" with no further data or error message for that record. Something like "Server not exist/available" and the Server ID should also be included on the record. Or the status could be "Error" with some description/comment on that test record explaining the actual failure reason (no such server ID exists).
Currently the only thing you see are the timestamp and the test ID. By seeing the Server ID and the correct status, admins will be able to quickly identify the servers which do not exist anymore. And if it happens all the time for the same server(s), they'll know that they need to remove those servers from the servers list.
The text was updated successfully, but these errors were encountered:
Not really, I'm not the one merging it, as im not the owner. In the last review by Alex, it was found that not all senarios where covered in it. That should be the case now. Its waiting for Alex to review, test it again before merging it. But he is very busy so it might take some time.
The issue of "Started but not completed" speed tests has been discussed in a couple of other tickets including the following:
#1591
My request is that SpeedTest-Tracker shows the correct status for such failed tests, instead of just showing "Started" with no further data or error message for that record. Something like "Server not exist/available" and the Server ID should also be included on the record. Or the status could be "Error" with some description/comment on that test record explaining the actual failure reason (no such server ID exists).
Currently the only thing you see are the timestamp and the test ID. By seeing the Server ID and the correct status, admins will be able to quickly identify the servers which do not exist anymore. And if it happens all the time for the same server(s), they'll know that they need to remove those servers from the servers list.
The text was updated successfully, but these errors were encountered: