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.

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

Allow macOS Debug pipeline to fail -> checking for memory alloc #117

Merged
merged 7 commits into from
Nov 16, 2022

Conversation

fabinsch
Copy link
Collaborator

  • currently we check for runtime memory allocations in this one specific pipeline
  • we still observe a few during the dense solve, but we don't want to PRs to be marked as failed, it's a way to keep track of mem allocs but no critical failure

- currently we check for runtime memory allocations in this one specific pipeline
- we still observe a few during the dense solve, but we dont want to PRs to be marked as failed, it's a way to keep track of mem allocs but no critical failure
jcarpent
jcarpent previously approved these changes Nov 16, 2022
- due to our include structure we have to specifically exclude this cfg otherwise we have two macOS Debug c++17
@fabinsch
Copy link
Collaborator Author

Hey @jcarpent, now it is fine. I needed to do some tests but now even though we have some tests failing due to mem allocation here we get a PR with green light.
I will do another commit to add back all the other pipelines which I deactivated to iterate faster. I think then we should merge but squeeze all commits into one.

@fabinsch fabinsch changed the title Draft: allow macOS Debug pipeline to fail -> checking for memory alloc Allow macOS Debug pipeline to fail -> checking for memory alloc Nov 16, 2022
@jcarpent jcarpent enabled auto-merge (squash) November 16, 2022 14:10
@jcarpent jcarpent merged commit b366929 into Simple-Robotics:devel Nov 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants