-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MFC seems to rebuild all targets on run
even if they're already been built via build
#288
Comments
It would be interesting if you could find a way to reliably reproduce this issue. Here are a few ideas for what could be going wrong:
|
@henryleberre logging into Bridges2 then issuing: [C]br013: bryngel-startup-proj/MFC $ . ./mfc.sh load -c b -m c
[I]br013: bryngel-startup-proj/MFC $ ./mfc.sh build -t pre_process simulation -j 8
[...builds...]
[I]br013: bryngel-startup-proj/MFC $ ./mfc.sh run ./examples/1D_sodshocktube/case.py -t pre_process -n 1
mfc: OK > (venv) Entered the Python virtual environment.
.=++*: -+*+=. [email protected] [Linux]
:+ -*- == =* . -----------------------------------------
:*+ == ++ .+- --jobs 1
:*##-.....:*+ .#%+++=--+=:::. --mpi
-=-++-======#=--**+++==+*++=::-:. --no-gpu
.:++=----------====+*= ==..:%..... --no-debug
.:-=++++===--==+=-+= +. := --targets pre_process
+#=::::::::=%=. -+: =+ *:
-----------------------------------------------------------
.*=-=*=.. :=+*+: -...-- $ ./mfc.sh [build, run, test, clean, count, packer]
--help
Run
Acquiring /ocean/projects/phy210041p/bryngel/MFC/examples/1D_sodshocktube/case.py...
Configuration:
Input
/ocean/projects/phy210041p/bryngel/MFC/examples/1D_sodshocktube/case.py
Job Name (-#) MFC
Engine (-e) interactive
Nodes (-N) 1
Tasks (/node) (-n) 1
MPI Binary (-b) srun
Generating input files for pre_process...
Generating pre_process.inp.
INFO: Forwarded 32/50 parameters.
Generating syscheck/include/case.fpp.
INFO: Custom case.fpp file is up to date.
$ cmake --build
/ocean/projects/phy210041p/bryngel/MFC/build/no-debug_no-gpu_mpi/syscheck --target
syscheck -j 1 --config Release
[100%] Built target syscheck
$ cmake --install
/ocean/projects/phy210041p/bryngel/MFC/build/no-debug_no-gpu_mpi/syscheck
-- Install configuration: "Release"
-- Installing: /jet/home/bryngel/bryngel-startup-proj/MFC/build/install/no-debug_no-gpu_mpi/bin/syscheck
Generating pre_process/include/case.fpp.
INFO: Custom case.fpp file is up to date.
$ cmake --build
/ocean/projects/phy210041p/bryngel/MFC/build/no-debug_no-gpu_mpi/pre_process --target
pre_process -j 1 --config Release
-- GLOB mismatch!
-- Enabled IPO / LTO
-- Configuring done
-- Generating done
-- Build files have been written to: /jet/home/bryngel/bryngel-startup-proj/MFC/build/no-debug_no-gpu_mpi/pre_process
[ 2%] Preprocessing (Fypp) m_variables_conversion.fpp
[ 5%] Preprocessing (Fypp) m_check_patches.fpp
[ 8%] Preprocessing (Fypp) m_constants.fpp
[ 11%] Preprocessing (Fypp) m_data_output.fpp
[...] |
Thanks, I'll take a look! |
@henryleberre --case-optimization seems to be hit or miss lately too... My fork is up to date with master, and I keep getting an unsupported value of weno_order error when using case optimization. When I look at the case.fpp file, it's empty. I'm also seeing the rebuild on every run behavior that @sbryngelson is seeing. |
@wilfonba, I can look into it. Are you looking at the case.fpp in the build folder or src/? It transitioned to the former recently. Since we don’t test for case-optimization right now, it’s possible that someone (including myself) might have broken it. |
Hmm, it appears to have been updated in the build directory. Maybe I'm missing something else then. |
MFC rebuilds all targets on
./mfc.sh run
even if they've already been built via./mfc.sh build
. Seems to be triggered via aGLOB MISMATCH
though I haven't investigated why this occurs. Even occurs if one immediately runs after a build. One option is to avoidbuild
altogether though this is obviously not a very attractive idea.It even partially rebuilds some dependencies like FFTW/HDF5.
Example snippet:
The text was updated successfully, but these errors were encountered: