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

fix: Assertion failure in propagation example #1180

Merged
merged 1 commit into from
Mar 2, 2022

Conversation

paulgessinger
Copy link
Member

This was for some reason using matrix access with two arguments to set elements of a vector (the diagonal of a matrix). Switched to use single component element access.

This was for some reason using matrix access with two arguments to set
elements of a vector (the diagonal of a matrix). Switched to use single
commponent element access.
@paulgessinger paulgessinger added this to the next milestone Mar 2, 2022
@paulgessinger paulgessinger changed the title fix: Assertion failure in proapgation example fix: Assertion failure in propagation example Mar 2, 2022
@stephenswat stephenswat added automerge Bug Something isn't working Component - Core Affects the Core module Impact - Minor Nuissance bug and/or affects only a single module labels Mar 2, 2022
@codecov
Copy link

codecov bot commented Mar 2, 2022

Codecov Report

Merging #1180 (ea1b7ca) into main (3ee4e2e) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##             main    #1180   +/-   ##
=======================================
  Coverage   47.83%   47.83%           
=======================================
  Files         360      360           
  Lines       18530    18530           
  Branches     8739     8739           
=======================================
  Hits         8863     8863           
  Misses       3631     3631           
  Partials     6036     6036           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3ee4e2e...ea1b7ca. Read the comment docs.

@kodiakhq kodiakhq bot merged commit 988e2ca into acts-project:main Mar 2, 2022
kodiakhq bot pushed a commit that referenced this pull request Mar 3, 2022
In the CI, we currently run the examples in Release only, which adds the `-DNDEBUG` flag and consequently disables `assert`. We can't run these in the CI with Debug, since that implies `-O0` and runs forever. 

This PR adds a new CMake option `ACTS_FORCE_ASSERTIONS` which defaults to `OFF`. If enabled, this will prepend a system include directory `cmake/assert_include` to all compilation units, which contains a wrapper around `cassert`, `Eigen/{Core,Dense,Geometry}` which enables `assert` (and `eigen_assert`) regardless of `NDEBUG`.

I verified that this would have triggered the assertion from #1180 for example.

The CI jobs are configured to run with `ACTS_FORCE_ASSERTIONS=ON`.
@paulgessinger paulgessinger modified the milestones: next, v18.0.0 Apr 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automerge Bug Something isn't working Component - Core Affects the Core module Impact - Minor Nuissance bug and/or affects only a single module
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants