investigate random fails in knot-resolver CI
The deckard
job often fails in the CI like this with E RuntimeError: Server took too long to respond
and other random fail which in the current setup will trigger a rerun of the whole test suite.
Investigate the cause of the random errors, if that becomes too hard, consider adding some logic to rerun only the randomly failed tests (there is some retry logic in Deckard already, so maybe use that). Alternatively, making the timeout for queries longer might help as well.