Skip to content

Structure, refactor and clean up trace messages #751

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

jorisdral
Copy link
Collaborator

@jorisdral jorisdral commented Jun 3, 2025

See the commit messages

I'm unsure whether abae6ba6d643580299bdaf985da168c94673f21 is useful, so let me know if we should include it or not.

@jorisdral jorisdral self-assigned this Jun 3, 2025
@jorisdral jorisdral marked this pull request as draft June 3, 2025 15:48
@jorisdral jorisdral force-pushed the jdral/trace-messages branch 7 times, most recently from c2602db to ff9b0df Compare June 4, 2025 12:21
jorisdral added 3 commits June 4, 2025 14:22
We give the trace message datatypes more structure (see the `$traces` Haddock
section), and we add few new messages. In the process, we apply some minor
refactorings to tracer calls and surrounding code.
The idea is to cover as much of the public API as possible to trace most (if not
all) unique trace messages at least once. The trace output is useful in two
ways:

* By using golden tests based on the trace output we can help to ensure that
  trace datatypes and their printing do not change unexpectedly.

* The trace output serves as an example that can be manually inspected to see
  whether the trace messages are printed correctly and whether they are useful.
This helps troubleshoot golden test failures that can't be reproduced locally.
For example, if a golden test fails on a Windows machine, then I can not
reproduce it locally on an Ubuntu machine.
@jorisdral jorisdral force-pushed the jdral/trace-messages branch from ff9b0df to 0abae6b Compare June 4, 2025 12:22
@jorisdral jorisdral changed the title Clean up trace datatypes Structure, refactor and clean up trace messages Jun 4, 2025
@jorisdral jorisdral marked this pull request as ready for review June 4, 2025 12:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant