Skip to content
This repository was archived by the owner on Dec 14, 2022. It is now read-only.

Time entire pipeline end-to-end #206

Closed
emersonknapp opened this issue Jun 10, 2020 · 0 comments · Fixed by #217
Closed

Time entire pipeline end-to-end #206

emersonknapp opened this issue Jun 10, 2020 · 0 comments · Fixed by #217
Assignees
@darvg
Labels
enhancement New feature or request
Milestone
Sprint #21

Comments

@emersonknapp
Copy link
Contributor

emersonknapp commented Jun 10, 2020 •
edited
Loading

Description

As a user, I can get the time the entire pipeline takes to complete, so that I can make informed decisions as to whether or not my application has any inefficiencies

Related Issues

Part of #205

Completion Criteria

  • The tool outputs the time taken for the entire cross-compile pipeline into a uniquely named file under cc_internals/

Implementation Notes / Suggestions

  • Suggestion: maybe use a python context __enter__ / __exit__ construct for timers

Testing Notes / Suggestions

  • Unit test for any new functions/objects
  • End-to-end test should check for output file and some bit of its content, at least
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@darvg darvg

Labels
enhancement New feature or request
Projects
None yet
Milestone
Sprint #21
Development

Successfully merging a pull request may close this issue.

Time the cross compile pipeline from end to end ros-tooling/cross_compile
3 participants
@thomas-moulard @emersonknapp @darvg