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 action should also have automatically created this issue, but I misconfigured the GITHUB_TOKEN env variable and it didn't.
As for the test itself, we could simply increase the timeout, but I think @Haroenv mentioned also adding a retry mechanism. Any preference? @MartinKolarik have you seen just being slow and waiting long would work, or does it make more sense to retry?
The text was updated successfully, but these errors were encountered:
I suggest at least five attempts in total with up to a few minutes between each. The API is occasionally very slow or just straight up failing with 502 errors.
Seems like the API Control tests we moved into their own weekly CRON job has had its first fail: https://github.com/algolia/npm-search/actions/runs/6704941688/job/18218376954. This is partly expected, as those tests are flaky.
The action should also have automatically created this issue, but I misconfigured the
GITHUB_TOKEN
env variable and it didn't.As for the test itself, we could simply increase the timeout, but I think @Haroenv mentioned also adding a retry mechanism. Any preference? @MartinKolarik have you seen just being slow and waiting long would work, or does it make more sense to retry?
The text was updated successfully, but these errors were encountered: