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

MFEM: add new version v4.7 #44010

Open
wants to merge 21 commits into
base: develop
Choose a base branch
from
Open

MFEM: add new version v4.7 #44010

wants to merge 21 commits into from

Conversation

v-dobrev
Copy link
Member

@v-dobrev v-dobrev commented May 5, 2024

TODO:

* Fix the build when the cuda variant is disabled and cuda is
  present on the system.
* In the 'libs' property, search for the libraries in the whole
  prefix, not just in 'lib' -- newer versions use 'lib64' at least
  in some cases.
* Propagate the 'make_jobs' setting to the build system -- it
  requires a special flag in the make options.
@spackbot-app spackbot-app bot added the patch label May 7, 2024
path_from_modules(...) to the rpaths when it returns None. The presense
of None in the rpaths was causing an issue.
… was

causing the PETSc configuration to fail.
…nmp'

to the SuiteSparse build system. Add backward compatibility support for
new SuiteSparse versions which moved the SuiteSparse headers inside a
subdirectory 'suitesparse' -- to allow existing packages to work with these
new versions, all headers from the 'suitesparse' subdirectory are linked in
the parent directory, '<prefix>/include'. Added new version: v7.7.0.
during testing through Spack. Added various tweaks and fixes in the
package and updated the testing script 'test_builds.sh'.
@spackbot-app spackbot-app bot added build-environment conflicts core PR affects Spack core functionality dependencies labels May 16, 2024
@v-dobrev
Copy link
Member Author

@spackbot fix style

Copy link

spackbot-app bot commented May 17, 2024

Let me see if I can fix that for you!

Copy link

spackbot-app bot commented May 17, 2024

I was able to run spack style --fix for you!

spack style --fix
==> Running style checks on spack
  selected: isort, black, flake8, mypy
==> Modified files
  lib/spack/spack/build_environment.py
  var/spack/repos/builtin/packages/hiop/package.py
  var/spack/repos/builtin/packages/metis/package.py
  var/spack/repos/builtin/packages/mfem/package.py
  var/spack/repos/builtin/packages/petsc/package.py
  var/spack/repos/builtin/packages/suite-sparse/package.py
  var/spack/repos/builtin/packages/zlib-ng/package.py
==> Running isort checks
Fixing /tmp/tmp0qna4rvk/spack/var/spack/repos/builtin/packages/suite-sparse/package.py
  isort checks were clean
==> Running black checks
reformatted var/spack/repos/builtin/packages/metis/package.py
reformatted var/spack/repos/builtin/packages/suite-sparse/package.py
reformatted var/spack/repos/builtin/packages/zlib-ng/package.py
reformatted var/spack/repos/builtin/packages/mfem/package.py
All done! ✨ 🍰 ✨
4 files reformatted, 3 files left unchanged.
  black checks were clean
==> Running flake8 checks
  flake8 checks were clean
==> Running mypy checks
lib/spack/spack/version/version_types.py:145: error: Argument 2 to "StandardVersion" has incompatible type "*Tuple[Tuple[Any, ...], Tuple[Any, ...]]"; expected "Tuple[Tuple[Any, ...], Tuple[Any, ...]]"  [arg-type]
lib/spack/spack/version/version_types.py:452: error: Argument 2 to "StandardVersion" has incompatible type "*Tuple[Tuple[Any, ...], Tuple[Any, ...]]"; expected "Tuple[Tuple[Any, ...], Tuple[Any, ...]]"  [arg-type]
lib/spack/spack/version/version_types.py:481: error: Argument 2 to "StandardVersion" has incompatible type "*Tuple[Tuple[Any, ...], Tuple[Any, ...]]"; expected "Tuple[Tuple[Any, ...], Tuple[Any, ...]]"  [arg-type]
Found 3 errors in 1 file (checked 625 source files)
  mypy found errors
Keep in mind that I cannot fix your flake8 or mypy errors, so if you have any you'll need to fix them and update the pull request. If I was able to push to your branch, if you make further changes you will need to pull from your updated branch before pushing again.

I've updated the branch with style fixes.

@alalazo alalazo self-assigned this May 17, 2024
@v-dobrev
Copy link
Member Author

@spackbot fix style

Copy link

spackbot-app bot commented May 24, 2024

Let me see if I can fix that for you!

Copy link

spackbot-app bot commented May 24, 2024

I was able to run spack style --fix for you!

spack style --fix
==> Running style checks on spack
  selected: isort, black, flake8, mypy
==> Modified files
  lib/spack/spack/build_environment.py
  var/spack/repos/builtin/packages/hiop/package.py
  var/spack/repos/builtin/packages/hypre/package.py
  var/spack/repos/builtin/packages/metis/package.py
  var/spack/repos/builtin/packages/mfem/package.py
  var/spack/repos/builtin/packages/petsc/package.py
  var/spack/repos/builtin/packages/suite-sparse/package.py
  var/spack/repos/builtin/packages/zlib-ng/package.py
==> Running isort checks
  isort checks were clean
==> Running black checks
reformatted var/spack/repos/builtin/packages/mfem/package.py
All done! ✨ 🍰 ✨
1 file reformatted, 7 files left unchanged.
  black checks were clean
==> Running flake8 checks
  flake8 checks were clean
==> Running mypy checks
lib/spack/spack/version/version_types.py:145: error: Argument 2 to "StandardVersion" has incompatible type "*Tuple[Tuple[Any, ...], Tuple[Any, ...]]"; expected "Tuple[Tuple[Any, ...], Tuple[Any, ...]]"  [arg-type]
lib/spack/spack/version/version_types.py:452: error: Argument 2 to "StandardVersion" has incompatible type "*Tuple[Tuple[Any, ...], Tuple[Any, ...]]"; expected "Tuple[Tuple[Any, ...], Tuple[Any, ...]]"  [arg-type]
lib/spack/spack/version/version_types.py:481: error: Argument 2 to "StandardVersion" has incompatible type "*Tuple[Tuple[Any, ...], Tuple[Any, ...]]"; expected "Tuple[Tuple[Any, ...], Tuple[Any, ...]]"  [arg-type]
Found 3 errors in 1 file (checked 625 source files)
  mypy found errors
Keep in mind that I cannot fix your flake8 or mypy errors, so if you have any you'll need to fix them and update the pull request. If I was able to push to your branch, if you make further changes you will need to pull from your updated branch before pushing again.

I've updated the branch with style fixes.

'ld_flags_from_dirs' as methods of class 'Mfem' so that they
can be reused by sub-classes.
@v-dobrev
Copy link
Member Author

@spackbot fix style

Copy link

spackbot-app bot commented May 30, 2024

Let me see if I can fix that for you!

Copy link

spackbot-app bot commented May 30, 2024

I was able to run spack style --fix for you!

spack style --fix
==> Running style checks on spack
  selected: isort, black, flake8, mypy
==> Modified files
  lib/spack/spack/build_environment.py
  var/spack/repos/builtin/packages/hiop/package.py
  var/spack/repos/builtin/packages/hypre/package.py
  var/spack/repos/builtin/packages/metis/package.py
  var/spack/repos/builtin/packages/mfem/package.py
  var/spack/repos/builtin/packages/petsc/package.py
  var/spack/repos/builtin/packages/suite-sparse/package.py
  var/spack/repos/builtin/packages/zlib-ng/package.py
==> Running isort checks
  isort checks were clean
==> Running black checks
reformatted var/spack/repos/builtin/packages/mfem/package.py
All done! ✨ 🍰 ✨
1 file reformatted, 7 files left unchanged.
  black checks were clean
==> Running flake8 checks
  flake8 checks were clean
==> Running mypy checks
lib/spack/spack/version/version_types.py:145: error: Argument 2 to "StandardVersion" has incompatible type "*Tuple[Tuple[Any, ...], Tuple[Any, ...]]"; expected "Tuple[Tuple[Any, ...], Tuple[Any, ...]]"  [arg-type]
lib/spack/spack/version/version_types.py:452: error: Argument 2 to "StandardVersion" has incompatible type "*Tuple[Tuple[Any, ...], Tuple[Any, ...]]"; expected "Tuple[Tuple[Any, ...], Tuple[Any, ...]]"  [arg-type]
lib/spack/spack/version/version_types.py:481: error: Argument 2 to "StandardVersion" has incompatible type "*Tuple[Tuple[Any, ...], Tuple[Any, ...]]"; expected "Tuple[Tuple[Any, ...], Tuple[Any, ...]]"  [arg-type]
Found 3 errors in 1 file (checked 625 source files)
  mypy found errors
Keep in mind that I cannot fix your flake8 or mypy errors, so if you have any you'll need to fix them and update the pull request. If I was able to push to your branch, if you make further changes you will need to pull from your updated branch before pushing again.

I've updated the branch with style fixes.

Copy link
Contributor

@kennyweiss kennyweiss left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @v-dobrev!

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

Successfully merging this pull request may close these issues.

None yet

3 participants