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

[DEFECT] ExternalRay test failing #2392

Open
8 of 13 tasks
PaulTalbot-INL opened this issue Oct 28, 2024 · 1 comment
Open
8 of 13 tasks

[DEFECT] ExternalRay test failing #2392

PaulTalbot-INL opened this issue Oct 28, 2024 · 1 comment

Comments

@PaulTalbot-INL
Copy link
Collaborator

PaulTalbot-INL commented Oct 28, 2024

Thank you for the defect report

Defect Description

In the regression testing for Mingw, the test tests\framework\InternalParallelTests\ExternalModelRay is consistently failing, and should be considered for CCB exception in PRs while we pursue solutions.

Steps to Reproduce

Run regression tests on main branch

Expected Behavior

Pass tests

Screenshots and Input Files

see https://civet.inl.gov/job/2509941/ for example

OS

Windows

OS Version

No response

Dependency Manager

CONDA

For Change Control Board: Issue Review

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

For Change Control Board: Issue Closure

  • If the issue is a defect, is the defect fixed?
  • If the issue is a defect, is the defect tested for in the regression test system? (If not explain why not.)
  • 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)?
  • 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)?
  • If the issue is being closed without a pull request, has an explanation of why it is being closed been provided?
@wangcj05
Copy link
Collaborator

The suggestion is good to me (CCB).

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

No branches or pull requests

2 participants