Skip to content
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

FFCx logger leaking information with setuptools>65.5.1 #553

Closed
jorgensd opened this issue Feb 1, 2023 · 4 comments · Fixed by #554
Closed

FFCx logger leaking information with setuptools>65.5.1 #553

jorgensd opened this issue Feb 1, 2023 · 4 comments · Fixed by #554

Comments

@jorgensd
Copy link
Sponsor Member

jorgensd commented Feb 1, 2023

With upgraded setuptools and run

from mpi4py import MPI
from dolfinx import mesh, fem
domain = mesh.create_unit_square(MPI.COMM_WORLD, 8, 8, mesh.CellType.quadrilateral)
V = fem.FunctionSpace(domain, ("Lagrange", 1))

we get output from

-> r = ffcx.codegeneration.jit.compile_elements([ufl_object], options=p_ffcx, **p_jit)
INFO:root:running build_ext
INFO:root:building 'libffcx_elements_e4fe433d26b02ded2cb20b3aae866c45eff14100' extension
INFO:root:x86_64-linux-gnu-gcc -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security -g -fwrapv -O2 -fPIC -I/usr/local/lib/python3.10/dist-packages/ffcx/codegeneration -I/usr/include/python3.10 -c libffcx_elements_e4fe433d26b02ded2cb20b3aae866c45eff14100.c -o ./libffcx_elements_e4fe433d26b02ded2cb20b3aae866c45eff14100.o -O2
INFO:root:x86_64-linux-gnu-gcc -shared -Wl,-O1 -Wl,-Bsymbolic-functions -Wl,-Bsymbolic-functions -g -fwrapv -O2 ./libffcx_elements_e4fe433d26b02ded2cb20b3aae866c45eff14100.o -L/usr/lib/x86_64-linux-gnu -o ./libffcx_elements_e4fe433d26b02ded2cb20b3aae866c45eff14100.cpython-310-x86_64-linux-gnu.so

This happens every time we call FFCx, causing massive output

@jorgensd
Copy link
Sponsor Member Author

jorgensd commented Feb 1, 2023

Seems to come from cffi, i.e. ffibuilder.compile

@jorgensd
Copy link
Sponsor Member Author

jorgensd commented Feb 1, 2023

We should probably set: https:/FEniCS/ffcx/blob/main/ffcx/codegeneration/jit.py#L279 verbose=False

@jorgensd
Copy link
Sponsor Member Author

jorgensd commented Feb 1, 2023

@michalhabera @garth-wells @chrisrichardson are there any specific reason we have had on verbose mode for cffi by default?

@garth-wells
Copy link
Member

The issue isn't verbose=True, but where the output is being directed to. It's helpful for the JIT log file to have the verbose output.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants