From: Simon Tournier <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludovic.courtes@inria.fr>, 65219@debbugs.gnu.org
Cc: reza <reza@housseini.me>
Subject: bug#65219: OpenFOAM is not reproducible
Date: Wed, 23 Aug 2023 18:39:07 +0200 [thread overview]
Message-ID: <86zg2hzpas.fsf@gmail.com> (raw)
In-Reply-To: <87r0oagh53.fsf@inria.fr>
Hi,
On Fri, 11 Aug 2023 at 09:41, Ludovic Courtès <ludovic.courtes@inria.fr> wrote:
> /share/OpenFOAM/build/linux64GccDPInt32Opt/applications/solvers/heatTransfer/chtMultiRegionFoam/chtMultiRegionTwoPhaseEulerFoam/chtMultiRegionTwoPhaseEulerFoam.C.dep
> /share/OpenFOAM/build/linux64GccDPInt32Opt/applications/solvers/multiphase/reactingMultiphaseEulerFoam/reactingMultiphaseEulerFoam.C.dep
> /share/OpenFOAM/build/linux64GccDPInt32Opt/applications/solvers/multiphase/reactingTwoPhaseEulerFoam/reactingTwoPhaseEulerFoam.C.dep
> /share/OpenFOAM/build/linux64GccDPInt32Opt/src/functionObjects/phaseSystems/sizeDistribution/sizeDistribution.C.dep
> /share/OpenFOAM/build/linux64GccDPInt32Opt/src/phaseSystemModels/reactingEuler/twoPhaseCompressibleTurbulenceModels/kineticTheoryModels/kineticTheoryModel/kineticTheoryModel.C.dep
> /share/OpenFOAM/build/linux64GccDPInt32Opt/src/phaseSystemModels/reactingEuler/twoPhaseCompressibleTurbulenceModels/phasePressureModel/phasePressureModel.C.dep
> /share/OpenFOAM/build/linux64GccDPInt32Opt/src/phaseSystemModels/reactingEuler/twoPhaseCompressibleTurbulenceModels/twoPhaseCompressibleTurbulenceModels.C.dep
> /share/OpenFOAM/build/linux64GccDPInt32Opt/src/phaseSystemModels/reactingEuler/twoPhaseSystem/diameterModels/IATE/IATE.C.dep
> /share/OpenFOAM/build/linux64GccDPInt32Opt/src/phaseSystemModels/reactingEuler/twoPhaseSystem/diameterModels/IATE/IATEsources/phaseChange/phaseChange.C.dep
> /share/OpenFOAM/build/linux64GccDPInt32Opt/src/phaseSystemModels/reactingEuler/twoPhaseSystem/twoPhaseSystem.C.dep
> /share/OpenFOAM/build/linux64GccDPInt32Opt/src/phaseSystemModels/reactingEuler/twoPhaseSystem/twoPhaseSystems.C.dep
Are these files required at run-time? I mean, why are they retain? And
I was guessing they should be removed, no?
> /share/OpenFOAM/test/IO/fileHandler/log.blockMesh
> /share/OpenFOAM/test/IO/fileHandler/log.decomposePar
> /share/OpenFOAM/test/IO/fileHandler/log.decomposePar.collated
> /share/OpenFOAM/test/IO/fileHandler/log.decomposePar.uncollated
> /share/OpenFOAM/test/IO/fileHandler/log.foamFormatConvert
> /share/OpenFOAM/test/IO/fileHandler/log.foamFormatConvert.uncollated
> /share/OpenFOAM/test/IO/fileHandler/log.particleFoam
> /share/OpenFOAM/test/IO/fileHandler/log.particleFoam.collated
> /share/OpenFOAM/test/IO/fileHandler/log.particleFoam.multiCollated
> /share/OpenFOAM/test/IO/fileHandler/log.particleFoam.uncollated
> /share/OpenFOAM/test/IO/fileHandler/log.particleFoam.uncollated_from_multiCollated
> /share/OpenFOAM/test/IO/fileHandler/log.reconstructPar
> /share/OpenFOAM/test/IO/fileHandler/log.reconstructPar.collated
> /share/OpenFOAM/test/IO/fileHandler/log.reconstructPar.multiCollated
> /share/OpenFOAM/test/IO/fileHandler/machineA/fileHandler/log.particleFoam.distributed_multiCollated
> /share/OpenFOAM/test/fvMeshTools/cavity/0.005/polyMesh/faces
> /share/OpenFOAM/test/fvMeshTools/cavity/0.005/polyMesh/neighbour
> /share/OpenFOAM/test/fvMeshTools/cavity/0.005/polyMesh/owner
> /share/OpenFOAM/test/fvMeshTools/cavity/0.005/polyMesh/points
> /share/OpenFOAM/test/fvMeshTools/cavity/0.01/polyMesh/faces
> /share/OpenFOAM/test/fvMeshTools/cavity/0.01/polyMesh/neighbour
> /share/OpenFOAM/test/fvMeshTools/cavity/0.01/polyMesh/owner
> /share/OpenFOAM/test/fvMeshTools/cavity/0.01/polyMesh/points
> /share/OpenFOAM/test/fvMeshTools/cavity/0.015/polyMesh/faces
> […]
> /share/OpenFOAM/test/multiphase/multiphaseEulerFoam/thermal/waterEvaporation/log.multiphaseEulerFoam.e.steam_h.water
> /share/OpenFOAM/test/multiphase/multiphaseEulerFoam/thermal/waterEvaporation/log.multiphaseEulerFoam.h.steam_e.water
> /share/OpenFOAM/test/multiphase/multiphaseEulerFoam/thermal/waterEvaporation/log.multiphaseEulerFoam.h.steam_h.water
> /share/OpenFOAM/test/multiphase/multiphaseEulerFoam/thermal/waterEvaporation/postProcessing.eps
> /share/OpenFOAM/test/postProcessing/channel/log.blockMesh
> /share/OpenFOAM/test/postProcessing/channel/log.topoSet
> /share/OpenFOAM/test/testLoopReport
Similar question, no? Why log files and testing files are part of the
output?
Cheers,
simon
next prev parent reply other threads:[~2023-08-23 17:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 7:41 bug#65219: OpenFOAM is not reproducible Ludovic Courtès
2023-08-23 16:39 ` Simon Tournier [this message]
[not found] ` <4523575a-dc70-4ec8-7c07-2d949b185bb8@housseini.me>
2023-08-24 10:29 ` reza via Bug reports for GNU Guix
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86zg2hzpas.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=65219@debbugs.gnu.org \
--cc=ludovic.courtes@inria.fr \
--cc=reza@housseini.me \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).