forked from idaholab/moose
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Feel like I'm getting into hacking territory
It turns out that there are some baked in assumptions of where the App is located relative to the testroot. There are some nasty hacks to locate it in a normal installation location, but this doesn't work if you install elsewhere (like we have to for the test). In order to get the TestHarness to behave, it's easiest to just link the executable to the fake test hierarchy. This part isn't a hack ;) Next Problem, the TestHarness currently checks for the working directory to exist in the Runnable phase, which occurs asyncronously to the scheduled launch of the test. This is a no go, since we are trying to copy the directory structure in the test so it won't exist for latter tests. So... I moved the working directory check to the place where we actually launch the test. This would be OK, but apparently there are other assumptions baked into the Job class. I had to start/stop the timer to avoid an index out of range. Now the tests are running properly. refs idaholab#19022
- Loading branch information
Showing
2 changed files
with
27 additions
and
8 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters