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

codecoverage is months old #761

Closed
10 tasks done
alfoa opened this issue Aug 26, 2018 · 1 comment · Fixed by #762
Closed
10 tasks done

codecoverage is months old #761

alfoa opened this issue Aug 26, 2018 · 1 comment · Fixed by #762
Assignees
Labels
defect devel issues in current devel master issue in current master priority_critical

Comments

@alfoa
Copy link
Collaborator

alfoa commented Aug 26, 2018


Issue Description

What did you expect to see happen?

The code coverage script to be functional.
The code coverage is months old since the check_coverage.sh is broken.
This is causing the master branch to be red since a while.

What did you see instead?

The code coverage script is currently broken

Do you have a suggested fix for the development team?
Please attach the input file(s) that generate this error. The simpler the input, the faster we can find the issue.

For Change Control Board: Issue Review

This review should occur before any development is performed as a response to this issue.

  • 1. Is it tagged with a type: defect or improvement?
  • 2. Is it tagged with a priority: critical, normal or minor?
  • 3. If it will impact requirements or requirements tests, is it tagged with requirements?
  • 4. If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users.
  • 5. Is a rationale provided? (Such as explaining why the improvement is needed or why current code is wrong.)

For Change Control Board: Issue Closure

This review should occur when the issue is imminently going to be closed.

  • 1. If the issue is a defect, is the defect fixed?
  • 2. If the issue is a defect, is the defect tested for in the regression test system? (If not explain why not.)
  • 3. If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)?
  • 4. If the issue is a defect, does it impact the latest stable branch? If yes, is there any issue tagged with stable (create if needed)?
  • 5. If the issue is being closed without a merge request, has an explanation of why it is being closed been provided?
@alfoa alfoa added priority_critical defect devel issues in current devel master issue in current master labels Aug 26, 2018
@alfoa alfoa self-assigned this Aug 26, 2018
@wangcj05
Copy link
Collaborator

This issue will not impact the users, it is only for the code coverage tests.
Checklist is good.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
defect devel issues in current devel master issue in current master priority_critical
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants