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] Regex for running tests does not deal correctly with backslashes #2437

Open
8 of 13 tasks
caleb-sitton-inl opened this issue Feb 1, 2025 · 0 comments
Open
8 of 13 tasks

Comments

@caleb-sitton-inl
Copy link
Collaborator

Thank you for the defect report

Defect Description

When attempting to run specific tests on a Windows machine by using regex with filepaths, behavior is not as expected. Single backslash path separators are lost in the processing of the input, preventing rook from finding tests whose names match the input.

Steps to Reproduce

On a windows machine, enter the following command:
./run_tests --re=framework\Basic

Expected Behavior

The rook system should find and run all tests whose names match the user-provided regex.

Screenshots and Input Files

No response

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?
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

1 participant