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

[Fortran 90] COM.DATA.Invariant & COM.DATA.NotUsed do not detect violation #70

Closed
WaldoFR opened this issue Aug 2, 2017 · 0 comments
Closed

[Fortran 90] COM.DATA.Invariant & COM.DATA.NotUsed do not detect violation #70

WaldoFR opened this issue Aug 2, 2017 · 0 comments
Assignees
@WaldoFR
Labels
bug
Milestone
Version 3.0.0

Comments

@WaldoFR
Copy link

WaldoFR commented Aug 2, 2017

Theses two rules do not detect violations. The function call printError() that was ran at the end of the analysis was removed when changing data structures from Violation to CheckerResults #23.
@WaldoFR WaldoFR self-assigned this Aug 2, 2017
@WaldoFR WaldoFR added the bug label Aug 2, 2017
@WaldoFR WaldoFR added this to the Version 3.0 milestone Aug 2, 2017
WaldoFR pushed a commit to WaldoFR/i-CodeCNES that referenced this issue Aug 2, 2017
Fix cnescatlab#70 Call printError() function at the end of the analysis
8037835
@WaldoFR WaldoFR closed this as completed Aug 2, 2017
begarco pushed a commit to begarco/i-CodeCNES that referenced this issue Jan 25, 2020
Fix cnescatlab#70 Call printError() function at the end of the analysis
cc419fe
begarco pushed a commit that referenced this issue Feb 2, 2020
Fix #70 Call printError() function at the end of the analysis
8cfd3eb
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@WaldoFR WaldoFR

Labels
bug
Projects
None yet
Milestone
Version 3.0.0
Development

No branches or pull requests
1 participant
@WaldoFR