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

keyword "interfacecheck" is ignored by "run_framework" #440

Closed
10 tasks done
wangcj05 opened this issue Nov 28, 2017 · 3 comments · Fixed by #660
Closed
10 tasks done

keyword "interfacecheck" is ignored by "run_framework" #440

wangcj05 opened this issue Nov 28, 2017 · 3 comments · Fixed by #660
Assignees
Labels
priority_normal task This tag should be used for any new capability, improvement or enanchment

Comments

@wangcj05
Copy link
Collaborator

wangcj05 commented Nov 28, 2017


Issue Description

What did you expect to see happen?

run_framework should work with keyword interfacecheck

What did you see instead?

interfacecheck is ignored.

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?
@wangcj05 wangcj05 added task This tag should be used for any new capability, improvement or enanchment priority_normal labels Nov 28, 2017
@wangcj05 wangcj05 assigned wangcj05 and aalfonsi and unassigned wangcj05 Nov 28, 2017
@alfoa
Copy link
Collaborator

alfoa commented May 21, 2018

@wangcj05 the closure checklist

@alfoa
Copy link
Collaborator

alfoa commented May 21, 2018

Closure checklist passed... No email is needed since the problem was effecting a "testing" feature that we currently not expose to the users

@wangcj05
Copy link
Collaborator Author

wangcj05 commented May 21, 2018 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority_normal task This tag should be used for any new capability, improvement or enanchment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants