RavenFramework tests using pip package or pre-built executable

[j-bryan]

---

Pull Request Description

What issue does this change request address? (Use "#" before the issue to link it, i.e., #42.)

2272

What are the significant changes in functionality due to this change request?

Adds the ability to run RavenFramework tests using either a pip-installed version of raven or a prebuilt executable of raven. Note that as currently implemented, the other types of raven tests (e.g. RavenPython) and the plugin tests will run using the development version of raven and its installed plugins, not the alternative installation.

---

For Change Control Board: Change Request Review

The following review must be completed by an authorized member of the Change Control Board.

• [x] 1. Review all computer code.
• [x] 2. If any changes occur to the input syntax, there must be an accompanying change to the user manual and xsd schema. If the input syntax change deprecates existing input files, a conversion script needs to be added (see Conversion Scripts).
• [x] 3. Make sure the Python code and commenting standards are respected (camelBack, etc.) - See on the wiki for details.
• [x] 4. Automated Tests should pass, including run_tests, pylint, manual building and xsd tests. If there are changes to Simulation.py or JobHandler.py the qsub tests must pass.
• [x] 5. If significant functionality is added, there must be tests added to check this. Tests should cover all possible options. Multiple short tests are preferred over one large test. If new development on the internal JobHandler parallel system is performed, a cluster test must be added setting, in XML block, the node <internalParallel> to True.
• [x] 6. If the change modifies or adds a requirement or a requirement based test case, the Change Control Board's Chair or designee also needs to approve the change. The requirements and the requirements test shall be in sync.
• [x] 7. The merge request must reference an issue. If the issue is closed, the issue close checklist shall be done.
• [x] 8. If an analytic test is changed/added is the the analytic documentation updated/added?
• [x] 9. If any test used as a basis for documentation examples (currently found in raven/tests/framework/user_guide and raven/docs/workshop) have been changed, the associated documentation must be reviewed and assured the text matches the example.

[moosebuild]

Job Test Ubuntu 18-2 Python 3 on 1a34487 : invalidated by @joshua-cogliati-inl

removed numexpr so retrying test

[j-bryan]

The recent commit (8c67f36) is a large rework of the capability with an emphasis on simplicity. The major changes are

• Renaming magic variable %RAVENFRAMEWORK% to %RAVENEXECUTABLE%, per the suggestion
• Handling interpretation of %RAVENEXECUTABLE% magic variable in ravenframework/Models/Code.py where the other magic variables are handled.
• Removal of the --use-pip and --use-binary command line options for Rook. Instead, a new command line option --tester-command can be used to specify the command to use to when running a certain tester. This removes RAVEN-specific instructions for Rook with the trade-off of a more difficult syntax for the developer running the tests. An example of using this option to set the RavenFramework tester command is ./run_tests --tester-command RavenFramework path/to/raven_framework. In conjunction with the existing --python-command and --command-prefix options, this gives users full control over what a Tester runs as a command.
• Removal of the skip_if_install_type logic in RAVEN "tests" files. This was messy and a workaround for the lone python-raven-runs-raven test. However, I have not yet implemented a fix for this! This test is expected to fail if the magic variable %RAVENEXECUTABLE% is used to specify how to run raven in the inner raven for that test.

[moosebuild]

Job Test mac on 6828a8e : invalidated by @joshua-cogliati-inl

failed in set python environment

[moosebuild]

Job Test qsubs sawtooth on 6206fd8 : invalidated by @j-bryan

Rerunning to get log files on failing qsubs test