mjolnir
mjolnir copied to clipboard
The Logging in integration tests is problematic
-
We have far too many irrelevant calls to
LogService.errorfrom the matrix-bot-sdk MatrixClient for things that are expected ie getting a 404 when checking for the existence of a room alias or querying state events. This is causing a sort of alarm fatigue and makes it harder to look for the causes of problems in a full run (yarn test:integration). -
Mocha writes to the output stream in a completely inconsistent order to
LogService. it can make the logs fromMatrixClientor other components appear as though they are a result of a calls from a different test than what Mocha says has failed or has started running. Not sure if this is something from Mocha not awaiting test callbacks or something else.