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

Enable assertions during CI when release builds are used #1098

Closed
lifflander opened this issue Sep 29, 2020 · 1 comment · Fixed by #1107 or #1109
Closed

Enable assertions during CI when release builds are used #1098

lifflander opened this issue Sep 29, 2020 · 1 comment · Fixed by #1107 or #1109

Comments

@lifflander
Copy link
Collaborator

lifflander commented Sep 29, 2020

Right now, if you build with cmake in release mode, assertions vtAssert*() are disabled. Since the workflows all build in release to reduce memory usage, we don't see if assertions are breaking. I believe the configuration parameter vt_check_enabled(production) is used to switch between assertion failures breaking or not in release mode.

Add a cmake option to control this so we can have assertions in release builds in the workflows.

@lifflander lifflander changed the title Enable assertions during CI Enable assertions during CI when release builds are used Sep 29, 2020
JacobDomagala added a commit that referenced this issue Oct 12, 2020
JacobDomagala added a commit that referenced this issue Oct 12, 2020
…flows.ini files so it's properly added during workflow generation
@JacobDomagala
Copy link
Contributor

Reopened after comment #1107 (comment)

bradybray pushed a commit that referenced this issue Oct 15, 2020
bradybray pushed a commit that referenced this issue Oct 15, 2020
…flows.ini files so it's properly added during workflow generation
cz4rs pushed a commit that referenced this issue Jan 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment