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?
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_TOKENenv 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?