Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[CN-Exec/CN-Test-Gen] Configuring traces for runtime errors #783

Open
2 tasks
ZippeyKeys12 opened this issue Dec 23, 2024 · 0 comments
Open
2 tasks

[CN-Exec/CN-Test-Gen] Configuring traces for runtime errors #783

ZippeyKeys12 opened this issue Dec 23, 2024 · 0 comments
Labels
CN spec testing cn CN-exec Related to CN executable spec generation, called using `cn instrument` enhancement New feature or request ui/ux Issue with presentation or user experience

Comments

@ZippeyKeys12
Copy link
Collaborator

Since #651, the instrumentation now prints out traces, which can be quite long. We might not always want this, such as when running one of our testing tools with multiple failing tests.

There should be a way to configure whether you want full traces, or perhaps even the level of coarseness/descriptivity.

This could either be within (or by expanding) the current logging levels, or an orthogonal setting.

  • Implement in cn-executable library
  • Support via CLI option for cn test
@ZippeyKeys12 ZippeyKeys12 added cn CN spec testing CN-exec Related to CN executable spec generation, called using `cn instrument` labels Dec 23, 2024
@ZippeyKeys12 ZippeyKeys12 added enhancement New feature or request ui/ux Issue with presentation or user experience labels Jan 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
CN spec testing cn CN-exec Related to CN executable spec generation, called using `cn instrument` enhancement New feature or request ui/ux Issue with presentation or user experience
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ZippeyKeys12