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

RrR on Cluster #683

Closed
10 tasks done
PaulTalbot-INL opened this issue Jun 12, 2018 · 1 comment · Fixed by #684
Closed
10 tasks done

RrR on Cluster #683

PaulTalbot-INL opened this issue Jun 12, 2018 · 1 comment · Fixed by #684

Comments

@PaulTalbot-INL
Copy link
Collaborator

PaulTalbot-INL commented Jun 12, 2018


Issue Description

It appears Raven-running-Raven does not work as intended on the cluster; this likely has to do with libraries and environments.

Also, there's a big path difference between how it works locally and on the cluster; it appears the working directory is always raven/framework instead of the requested working directory.


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
Copy link
Collaborator

alfoa commented Jul 20, 2018

Issue closure checklist passed...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants