View Issue Details

IDProjectCategoryView StatusLast Update
0003873OpenFOAMBugpublic2022-08-10 10:47
Reportertniemi Assigned Towill  
Status resolvedResolutionfixed 
Product Versiondev 
Fixed in Versiondev 
Summary0003873: test/fvMeshTools/cavity fails in dev when reconstructing time step 0.01
DescriptionIt seems that the cavity fvMeshTools test is failing in recent dev builds, probably related to The first time step (0.005) gets reconstructed, but it fails with 0.01. Works, if directly issuing "reconstructPar -time 0.01"

I'm not sure if this is just a problem with the test or could this be a problem in some actual case, I just bumped into this because automatic build pipeline was failing.
Steps To ReproduceRun test/fvMeshTools/Allrun and check cavity/log.reconstrucPar

cannot find file "/u1/common/OpenFOAM/OpenFOAM-dev/test/fvMeshTools/cavity/0.01/polyMesh/cellProc"

    From function virtual Foam::autoPtr<Foam::ISstream> Foam::fileOperations::uncollatedFileOperation::readStream(Foam::regIOobject&, const Foam::fileName&, const Foam::word&, bool) const
    in file global/fileOperations/uncollatedFileOperation/uncollatedFileOperation.C at line 539.

FOAM exiting
TagsNo tags attached.



2022-08-10 07:14

reporter   ~0012708

Also postProcessing/channel test fails due to postProcess -> foamPostProcess change. Instead of
runApplication -s postProcess $(getApplication) -postProcess -latestTime

there should be something like
runApplication -s postProcess foamPostProcess -solver fluid -latestTime

Or alternatively define a getSolver-helper and then
runApplication -s postProcess foamPostProcess -solver $(getSolver) -latestTime


2022-08-10 09:28

manager   ~0012709

Last edited: 2022-08-10 09:38

I have updated the postProcess command: commit 19f984d58dd420ee621f4b8b5d202d8a59777f35
and added a get solver function and updated the tutorials and tests: commit bfa40570adaedfeafc07b670ed7b0624a5ab37a5


2022-08-10 10:47

manager   ~0012710

Thanks. It's because the serial mesh has changed **and** the processor mesh has changed, so reconstructPar doesn't know what to do. That workflow is highly unlikely to appear in an actual case.

Fixed in dev by

Issue History

Date Modified Username Field Change
2022-08-08 17:51 tniemi New Issue
2022-08-10 07:14 tniemi Note Added: 0012708
2022-08-10 09:28 henry Note Added: 0012709
2022-08-10 09:38 henry Note Edited: 0012709
2022-08-10 10:47 will Assigned To => will
2022-08-10 10:47 will Status new => resolved
2022-08-10 10:47 will Resolution open => fixed
2022-08-10 10:47 will Fixed in Version => dev
2022-08-10 10:47 will Note Added: 0012710