Closed Myoldmopar closed 1 year ago
@Myoldmopar sorry about that. I think it may work by checking if the file exists first before trying to copy.
But the safest thing is to just move the copy operation inside cmake via file(COPY) / configure_file(COPYONLY), so it's done once at cmake generation time. Edit: Depending on whether you run via ctest or via the exe directly, the current directory isn't the same though...
And yes, the C++ exception happens in SetupTestCase. The Test passes, the Suite fails.
Issue overview
There is an occasional unit test failure like this, where it is complaining it can't operate on
{build_folder}/tst/EnergyPlus/unit/in.epw
because it is in use. I think the problem comes down to some code around this line, where it is trying to setup the in.idf and in.epw for CLI testing. I guess if you run things in a bunch of threads, they can stomp on each other. Could we give each individual test its own IDF/EPW so there is no conflict?What's even weirder is that it's like the unit test....passes...but also doesn't? I feel like it is getting the exception raised, which signals the test failed, but because the file already exists from a different test, it goes ahead and passes. Here's the output from that link:
What do you think @jmarrec ?