Test logging

[AZWN]

Short description A debug log of an stxtest should be available, in order to have more debugging information available.

Problem description. When executing an stxtest, the final result is provided, but no information on how the solver achieved that result. This gives little insight in the underlying reasons of unexpected behavior. Even worse, when a test does not terminate, no information is available.

Describe the solution you'd like Alongside the stxresult file, an stxlog file should be generated, which contains the debug log of the solver. This feature should be configurable in the runtime.statix.testlog: <log level> option in the metaborg.yaml. When the log level is off, no log file should be generated.

Describe alternatives you've considered

• Providing warnings on certain types of suspicious behavior (such as many levels of recursion), but these are both more complicated to implement, and cover less cases.

Additional context

[AZWN]

Closed in 42bed63b43713e0331507a218efb9b605be8936a.