-
Notifications
You must be signed in to change notification settings - Fork 9
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
1484: fix memory footprint tests #1676
Conversation
ecd604f
to
40e4ef1
Compare
This comment was marked as outdated.
This comment was marked as outdated.
81ec62e
to
7ab383b
Compare
3c4bb4c
to
d04e3fc
Compare
Codecov Report
@@ Coverage Diff @@
## develop #1676 +/- ##
===========================================
- Coverage 83.79% 83.70% -0.10%
===========================================
Files 772 772
Lines 26868 26772 -96
===========================================
- Hits 22514 22409 -105
- Misses 4354 4363 +9
|
ebe33cb
to
827bbf9
Compare
a0f5b9a adds seemingly reasonable test verifying that Note: I was able to reproduce this locally with clang 13, so definitely not a compiler issue. |
ca13bd7
to
1153f9d
Compare
In the end, this PR is addressing 2 issues:
Other changes are a small cleanup, updating workflow definitions and removing tests performing footprinting of single components (these did not add much value, since the coverage is provided by testing |
Disable unity build in gcc-6 workflow and update all workflows.
This reverts commit 5f91b78.
Remove separate tests for each component. Footprinting is performed for all (live) components in `test_live_components` and `test_live_components_at_shutdown`.
a848af8
to
22dfbb8
Compare
fixes #1484