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
I've run into a weird case where a test was marked as a timeout, but a second later, the timeout message was overwritten with the results. Setting aside the fact that the probe shouldn't have taken 32 seconds to report the results, the API should still prevent this as it is confusing and contradicts our documentation.
We already have a check here, but when a test is marked as a timeout, we don't seem to increment probesAwaiting. Additionally, there's no check when calling recordProgress(), I think we should use a lua script with a check there as well.
The text was updated successfully, but these errors were encountered:
I've run into a weird case where a test was marked as a timeout, but a second later, the timeout message was overwritten with the results. Setting aside the fact that the probe shouldn't have taken 32 seconds to report the results, the API should still prevent this as it is confusing and contradicts our documentation.
We already have a check here, but when a test is marked as a timeout, we don't seem to increment
probesAwaiting
. Additionally, there's no check when callingrecordProgress()
, I think we should use a lua script with a check there as well.The text was updated successfully, but these errors were encountered: