Merged
Conversation
* Add mising QE releases. * Update QE dependencies and conflicts. * QE 6.3 install method requires a patch to work properly. * include QE git develop branch * QE HDF5 needs Fortran support. HDF5 versions prior to 1.8.16 leads to QE runtime errors. * Number of MKL related conflicts for QE. * Flake8 fixes for QE for hdf5 lines. * Pass in all compilers properly to QE configure * Fixed external BLAS/LAPACK linkage in QE. * Library search was problematic in QE. * Add section headings to QE package. * External FFTW compatible libraries properly detected in QE. * Flake8 fixes for QE * QE configure defaults to False for ELPA, thus Spack package should as well. * QE depends on FFTW3 provider instead of FFTW explictly. * Primary QE repo is gitlab.com, not github.com. Github mirror lags behind gitlab site. * Support both 6.3-backports branch and develop branch in QE. * QE patch needed for proper MKL detection. MKL_ROOT is detected and preferred, still falls back to finding first MKL installation in /opt/intel. * Use FFTW-API provider versioned interface for specify QE FFT dependency. * QE FFTW conflicts no longer need thanks to FFTW-API provider versioned interface. * Flake8 3.6.0 fix in support of spack#9853 * Fix QE conflict with ilp64 variant in support of spack#9853 * Remove custom url_for_version for QE package and use builtin url instead. In support of spack#9853 * Use FFTW builtin flags for QE instead of custom Python code. In support of spack#9853 * Fix typo in QE package comments. In support of spack#9853 * Future proof QE package patches in anticipation of QE >= 6.3.1. In support of spack#9853
…ck#9988) * Adding new versions of py-rope.
- Since early Spack versions, the SpecParser has (weirdly) been responsible for initializing Spec fields. - This refactors initialization to take place in Spec.__init__, as it probably should have originally. - This makes the code easier to read, the parser easier to understand, and removes the use of __new__ in the parser to initialize the Spec. - This also makes it possible to make a completely empty Spec with `Spec()` -- this is an abstract Spec that will match anything.
- simplify logic in multimethod - remove the requirement of multimethod invocations to walk up the stack.
- all multimethod tests are now run for both `multimethod` and `multimethod-inheritor` - do this with a parameterized fixture (pkg_name) that runs the same tests on both
Add tests MRO for inherited multimethods with multiple inheritance Add tests for inherited and overridden multimethods
* Spades: Add version 3.13.0 In version 3.13.0 the CmakeLists.txt dir is at a different location than in other versions. Versions up to 3.12.0 are located in "src" whereas 3.13.0 is a level deeper at "assemblers/src". * Remove git and add new version hash
Fix the install of the single header amalgate in catch2. The public API for catch < 2.3.0 was "#include <catch.hpp>". For 2.3.0+ it is "#include <catch2/catch.hpp>"
* updated release and checksums, also tightened depends_on() * remove blank line at end of file * removing new version 0.5
* usearch: Make binary executable * usearch: remove join_path
* add the tfel package * fix the tfel package * fix the tfel package * fix the tfel package * Taking Adam J. Steward' remarks into account * fixes trailing white spaces * Update description * Update dependencies following @adamjstewart adices * Style fixes * Style fixes * Add java optional support * add the maintainers attribute (following @alalazo advice), disable interface not selected (following @adamjstewart advice) * flake8 fixes * Fix Cast3M and python-bindings support. Python detection is made compatible with cmake'FindPythonLibs module (at least how it is used in TFEL) * Style fixes * Style fixes * Fix test on python version * Follow @adamjstewart advices: code is much cleaner and readable * Small fix * Small fix * Add comment * Small fix in cmake option * try again (trying to overcome Travis CI unstable build process) * Add support for the MFrontGenericInterfaceSupport project (MGIS) * Style fixes * Package documentation update * Package documentation update * Fix a typo thanks to Andreas Baumbach review * Follow Adam J. Stewart advices * Fix type
* added new versions, and tightened up depends_on() specs
* added type=('build', 'run') to r dependency
* updated versions for r-data-table
* added type=('build', 'run') to r dependency
* updated versions for r-cowplot
* depends_on: added type=('build', 'run') to r, and added r-scales
* updated versions for r-ape
* added type=('build', 'run') to r dependency
* Initial compiler support * added arm.py * Changed licence to Arm suggested header * Changed licence to the same as clang.py Main author of file is Nick Forrington <[email protected]> Minor changes by Srinath Vadlamani <[email protected]> * compilers: add arm compiler detection to Spack - added arm.py with support for detecting `armclang` and `armflang` Co-authored-by: Srinath Vadlamani <[email protected]> * Changed to using get get_compiler_version * linking to general cc for arm compiler * For arm compiler add CFLAGS to use compiler-rt rtlib. * Escape for special characters in rexep * Cleaned up for Flake8 to pass. * libcompiler-rt should be part of the LDFLAGS not CFLAGS * fixed m4 when using clang to used LDFLAGS. Fixed comments for arm.py to display compiler --version output with # NOAQ for flakes pass. * added arm compilers * proper linked names
Fixes spack#10284 spack#10152 replaced shutil.move with llnl's copy and copy_tree for resources. This did not copy permissions so led to later failures if an executable was copied (e.g. a configure script). This uses install/install_tree instead, which preserve permissions.
Add the development version of OpenMPI from the git repo in `master`.
gartung
force-pushed
the
fnal-develop-merge
branch
2 times, most recently
from
ce47953 to
0a28661
Compare
gartung
force-pushed
the
fnal-develop-merge
branch
from
0a28661 to
5d3979d
Compare
Member
|
@gartung Let me know when you think this is ready for merge. |
Member
Author
|
Its is ready |
marcmengel
added a commit
that referenced
this pull request
Feb 4, 2022
Replace dashes with underscores in product and dependency names so the can be evaluated by bash
greenc-FNAL
pushed a commit
that referenced
this pull request
Aug 4, 2022
* Created package and added description * Add py-markdown-include * Created package * Finished creating package * Added py-md-environ * Added build dependencies * Added other deps * Add python-markdown-math (#4) * Created package and started to add info * Removed unneeded global/install options * Figured out version spec for markdown-math * Removed type=build from unnecessary dependencies * Removed unneeded install/global options, added version spec to dependency * Added wscullin as interim maintainer for packages * Fixed style issues * Took care of trailing whitespace * Removed comment line before imports * Changed file charset to match other packages * Update var/spack/repos/builtin/packages/py-ford/package.py Co-authored-by: Adam J. Stewart <[email protected]> * Update var/spack/repos/builtin/packages/py-ford/package.py Co-authored-by: Adam J. Stewart <[email protected]> * Removed test dependency after review feedback * Added new 6.1.12 version to py-ford Co-authored-by: Seth R. Johnson <[email protected]> Co-authored-by: Adam J. Stewart <[email protected]>
marcmengel
pushed a commit
that referenced
this pull request
Apr 21, 2023
1. support version 3.1.3, which now depends on sundials@6 2. support version 3.1.2:, which broke the two patch files and therefore the two patch files have been replaced by more flexible filter_file() commands inside a patch() function. 3. rename the variant for python extension from using the package name "+pyuqtk" to the more standard "+python" 4. add maintainers @omsai and the upstream developer @bjdebus who offered to help with the spack packaging. 5. swig should only be a build-time dependency. swig is only necessary until @:3.1.0 6. confirmed python dependencies are correct by inspecting imports, subset python dependencies type to build, run, and confirmed all 31 build-time tests pass including the 9 python tests: ```console $ spack env create uqtk-dev $ spack add [email protected] $ spack install --test root && cat $(spack location -i uqtk)/.spack/install-time-test-log.txt ==> Testing package uqtk-3.1.3-nok6fut ==> [2023-04-19-14:56:25.005361] Running build-time tests ==> [2023-04-19-14:56:25.005536] RUN-TESTS: build-time tests [check] ==> [2023-04-19-14:56:25.009543] '/home/omsai/src/spack/opt/spack/linux-pureos10-skylake/gcc-10.2.1/gmake-4.4.1-b6g4apmfvxz3bn4eabh37dehcrg65fj7/bin/make' '-j4' '-n' 'test' ==> [2023-04-19-14:56:25.014903] '/home/omsai/src/spack/opt/spack/linux-pureos10-skylake/gcc-10.2.1/gmake-4.4.1-b6g4apmfvxz3bn4eabh37dehcrg65fj7/bin/make' '-j4' 'test' Running tests... /home/omsai/src/spack/opt/spack/linux-pureos10-skylake/gcc-10.2.1/cmake-3.26.3-zjmsfz23j5l4ytniz26uzvxonlu5qebr/bin/ctest --force-new-ctest-process Test project /tmp/omsai/spack-stage/spack-stage-uqtk-3.1.3-nok6fut47h42cnaau7wkoohgqy5f2qqa/spack-build-nok6fut Start 1: ArrayReadAndWrite Start 2: ArrayDelColumn Start 3: Array1DMiscTest Start 4: Array2DMiscTest 1/31 Test #1: ArrayReadAndWrite ................ Passed 0.01 sec Start 5: ArraySortTest 2/31 Test #2: ArrayDelColumn ................... Passed 0.01 sec Start 6: MultiIndexTest 3/31 Test #3: Array1DMiscTest .................. Passed 0.01 sec Start 7: CorrTest 4/31 Test #4: Array2DMiscTest .................. Passed 0.01 sec Start 8: QuadLUTest 5/31 Test #5: ArraySortTest .................... Passed 0.02 sec Start 9: MCMC2dTest 6/31 Test #6: MultiIndexTest ................... Passed 0.01 sec Start 10: MCMCRandomTest 7/31 Test #8: QuadLUTest ....................... Passed 0.02 sec Start 11: MCMCNestedTest 8/31 Test #10: MCMCRandomTest ................... Passed 0.02 sec Start 12: Deriv1dTest 9/31 Test #12: Deriv1dTest ...................... Passed 0.01 sec Start 13: SecondDeriv1dTest 10/31 Test #13: SecondDeriv1dTest ................ Passed 0.01 sec Start 14: GradHessianTest 11/31 Test #11: MCMCNestedTest ................... Passed 0.03 sec Start 15: GradientPCETest 12/31 Test #14: GradHessianTest .................. Passed 0.01 sec Start 16: PCE1dTest 13/31 Test #15: GradientPCETest .................. Passed 0.01 sec Start 17: PCEImplTest 14/31 Test #16: PCE1dTest ........................ Passed 0.01 sec Start 18: PCELogTest 15/31 Test #18: PCELogTest ....................... Passed 0.01 sec Start 19: Hessian2dTest 16/31 Test #19: Hessian2dTest .................... Passed 0.01 sec Start 20: BCS1dTest 17/31 Test #20: BCS1dTest ........................ Passed 0.01 sec Start 21: BCS2dTest 18/31 Test #21: BCS2dTest ........................ Passed 0.01 sec Start 22: LowRankRegrTest 19/31 Test #22: LowRankRegrTest .................. Passed 0.01 sec Start 23: PyModTest 20/31 Test #17: PCEImplTest ...................... Passed 0.07 sec Start 24: PyArrayTest 21/31 Test #23: PyModTest ........................ Passed 0.08 sec Start 25: PyArrayTest2 22/31 Test #25: PyArrayTest2 ..................... Passed 0.30 sec Start 26: PyQuadTest 23/31 Test #24: PyArrayTest ...................... Passed 1.44 sec Start 27: PyBCSTest1D 24/31 Test #26: PyQuadTest ....................... Passed 1.68 sec Start 28: PyBCSTest2D 25/31 Test #27: PyBCSTest1D ...................... Passed 1.66 sec Start 29: PyBADPTest 26/31 Test #7: CorrTest ......................... Passed 3.43 sec Start 30: PyRegressionTest 27/31 Test #28: PyBCSTest2D ...................... Passed 1.50 sec Start 31: PyGalerkinTest 28/31 Test #9: MCMC2dTest ....................... Passed 3.90 sec 29/31 Test #29: PyBADPTest ....................... Passed 1.66 sec 30/31 Test #30: PyRegressionTest ................. Passed 1.72 sec 31/31 Test #31: PyGalerkinTest ................... Passed 1.63 sec 100% tests passed, 0 tests failed out of 31 Total Test time (real) = 5.35 sec ==> [2023-04-19-14:56:30.382797] '/home/omsai/src/spack/opt/spack/linux-pureos10-skylake/gcc-10.2.1/gmake-4.4.1-b6g4apmfvxz3bn4eabh37dehcrg65fj7/bin/make' '-j4' '-n' 'check' ==> [2023-04-19-14:56:30.385983] Target 'check' not found in Makefile ```
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
20 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.