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

battle test obcpp memory usage #174

Open
Samir-Rashid opened this issue May 3, 2024 · 0 comments
Open

battle test obcpp memory usage #174

Samir-Rashid opened this issue May 3, 2024 · 0 comments
Labels
mission-critical MUST HAVE BEFORE COMPETITION

Comments

@Samir-Rashid
Copy link
Contributor

Test each state for 30 minutes to make sure things won't crash during the mission.

  • memory
    • valgrind for leaks, especially taking images and path planning
  • exceptions
    • Lucid calls can throw a bunch of random Exceptions at runtime. Need to wrap with try catch to make sure this doesn't take down the entire OBCPP.
  • edge cases
    • what if the state transitions don't behave like the "happy path". We could get unexpected inputs or the previous state might have some lingering things going on.
@Samir-Rashid Samir-Rashid added the mission-critical MUST HAVE BEFORE COMPETITION label May 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
mission-critical MUST HAVE BEFORE COMPETITION
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Samir-Rashid