(PC-5740) feat: clear react-query cache after each test file #241
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Link to JIRA ticket: https://passculture.atlassian.net/browse/PC-5740
Stratégie
Jest conseille
yarn jest --detectOpenHandles --runInBand
pour détecter les fuites, faire cela sur notre répo donnera le même résultat qu'en CI: les tests finis en ~70s et la commande qui continue de tourner dans le vide 5min.Pour identifier la source j'ai lancé chaque test avec
yarn jest <test_name> --detectOpenHandles
Et identifier ceux qui sont anormalement longs. (script)
Certains tests prennent 5minutes lancés tout seuls
Ces tests partagent entre autre l'utilisation de
react-query
Quelques recherches dans ce sens et je tombe sur une issue:
react-query
(n° 270)On y lit notamment
Bingo. (NB: 5min <-> durée de vie par défaut du cache, possible que ce ne soit pas une coïncidence)