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

[ci] Automatic comparison of traces #176

Closed
nasahlpa opened this issue Oct 10, 2023 · 3 comments · Fixed by #179
Closed

[ci] Automatic comparison of traces #176

nasahlpa opened this issue Oct 10, 2023 · 3 comments · Fixed by #179
Assignees
@nasahlpa

Comments

@nasahlpa
Copy link
Member

Currently, traces generated in the CI need to be manually inspected. Ideally, an automated comparison of generated traces to a golden model is conducted.
@nasahlpa nasahlpa self-assigned this Oct 10, 2023
@johannheyszl
Copy link
Collaborator

Sg, will mostly be useful for CI of capture tooling improvements where we assume that traces are in fact 'unchanged'. For CI of OT-side dev, traces will change appearance more often I guess, e.g. cycle delay after trigger etc.

@nasahlpa
Copy link
Member Author

Yes, I agree. We (@vogelpi @vrozic) were thinking that this could be useful to test upcoming changes in the SCA infrastructure. For this purpose, I think it might be an option to generate traces with a fixed OT version and compare to golden traces.

@johannheyszl
Copy link
Collaborator

makes sense :)

@nasahlpa nasahlpa mentioned this issue Oct 12, 2023
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@nasahlpa nasahlpa

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[ci] Automatic comparison of traces nasahlpa/ot-sca
2 participants
@nasahlpa @johannheyszl