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

[TASK] Include Windows testing for ipopt, cbc #334

Open
5 of 10 tasks
PaulTalbot-INL opened this issue Jan 24, 2024 · 0 comments
Open
5 of 10 tasks

[TASK] Include Windows testing for ipopt, cbc #334

PaulTalbot-INL opened this issue Jan 24, 2024 · 0 comments
Assignees
Labels
priority-critical Task that is time sensitive and critical to project work task Feature requests

Comments

@PaulTalbot-INL
Copy link
Collaborator


Issue Description

With its setup as of this writing, the Windows test is skipping tests using ipopt and cbc as solvers due to either (1) the solvers not being on the machine, or (2) inability to correctly recognize if the solver is on the machine. See for example from #333 :
image

We should try to do one or more of the following:

  1. Find a way to install ipopt and cbc via normal installation processes.
  2. Assure ipopt and cbc are on the regression testing machines and point users to how to obtain these solvers for themselves.
  3. Determine how to include openly available solvers as part of one-step installation processes.

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 task?
  • 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 release branch? If yes, is there any issue tagged with release (create if needed)?
  • 5. If the issue is being closed without a pull request, has an explanation of why it is being closed been provided?
@PaulTalbot-INL PaulTalbot-INL added task Feature requests priority-critical Task that is time sensitive and critical to project work labels Jan 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority-critical Task that is time sensitive and critical to project work task Feature requests
Projects
None yet
Development

No branches or pull requests

2 participants