Fix unstable tests by adding 'retry_until()'

[jiahuili430]

Overview

Add retry_until() to avoid request timeout error in search_test.exs.

Error logs:

1) test search returns all items for GET (SearchTest)
   test/elixir/test/search_test.exs:67
   ** (KeyError) key :status_code not found in: %HTTPotion.ErrorResponse{message: "req_timedout"}
	 code: assert resp.status_code == 200
	 stacktrace:
	   test/elixir/test/search_test.exs:74: (test)

Testing recommendations

make elixir-search

Related Issues or Pull Requests

Checklist

• Code is written and works correctly
• Changes are covered by tests
• Any new configurable parameters are documented in rel/overlay/etc/default.ini
• Documentation changes were made in the src/docs folder
• Documentation changes were backported (separated PR) to affected branches

[nickva]

Maybe we can do on extra single assert below, just to ensure it's not flapping and once it's hits 200 it stays 200

[nickva]

How does retry_until work? Do it have any magic to throw an exception and the whole test body up to that point is retried. Otherwise, if it's as simple as it looks in retry_until(fn -> resp.status_code == 200 end) we'd just be checking the same response and always fail, then we'd have to retry the whole Couch.get(...)?