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

Add a --bogus-trace #58

Open
tmplt opened this issue Oct 31, 2021 · 2 comments
Open

Add a --bogus-trace #58

tmplt opened this issue Oct 31, 2021 · 2 comments
Labels
enhancement New feature or request

Comments

@tmplt
Copy link
Member

tmplt commented Oct 31, 2021 •
edited
Loading

To test frontends we need a recorded trace. To make it as simple as possible to CI, a --bogus-trace or similar option should provide a source of randomized ITM packages that follow expected behavior (i.e., no re-entry errors unless requested).
@tmplt tmplt added the enhancement New feature or request label Oct 31, 2021
@tmplt tmplt added this to the v0.3.0 milestone Oct 31, 2021
@tmplt
Copy link
Member Author

tmplt commented Nov 1, 2021

CC @Yatekii

@tmplt tmplt mentioned this issue Nov 2, 2021
Closed
@tmplt
Copy link
Member Author

tmplt commented Nov 10, 2021

Not required for a v0.3.0 release. Postponing.

@tmplt tmplt removed this from the v0.3.0 milestone Nov 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Implement --bogus-trace rtic-scope/cargo-rtic-scope
1 participant
@tmplt