-
Notifications
You must be signed in to change notification settings - Fork 2.2k
Telcon: 2016 12 15
Todd Gamblin edited this page Dec 15, 2016
·
8 revisions
- Todd Gamblin (LLNL)
- Greg Lee
- Spack
v0.10
release still scheduled for end of December
- See project page
- any questions?
- Concretizer needs some work; this is planned for
v1.0
:
- There isn't enough backtracking in the solver for conflicting variants (see #2590)
- We are going to be doing build dependencies slightly differently for
v1.0
(see #2548)- concretize build deps for the front-end platform / default compiler
- avoid building things like cmake with "weird" compilers when it's not needed
- make sure build deps are built entirely for the front-end on platforms that need it
-
Plan:
-
Get the last few bugs out the door for 0.10
-
Getting a CDash site set up with a reasonably comprehensive set of package builds so that we can see what works and what does not. Right now we are playing whack-a-mole with github issues and we need a dashboard so we can make the thing converge to green.
-
Get the concretizer fixes in for 1.0 in the Jan-Feb timeframe.
-
Testing status
- We're working on CDash setup concurrently with
v1.0
- Waiting for LLNL approval to set up CDash site for public use (sigh)
- Massimiliano has converted
nose
tests topytest
-
pytest
seems a lot nicer - fixtures seem much better than the mockup we were doing
-
- Lowercase package names (#2475)
- going to standardize on lowercase
- had to put in some fixes for Mac OS X to properly check out git repos with case changes (#)
- Check out Mario's command to automatically add external packages #2507 (WIP)
spack external add <package name> <path>
- Feedback would be great
-
compilers.yaml
now distinguishes compiler by OS and target.
-
ppc64le
Linux has same OS asx86_64
Linux, but different targets. - spack wasn't differentiating well on LLNL's shared filesystem.
- Anything else?
- See Pulse for list of latest merges.
- Matt Legendre adding package support for nonstandard include/lib/rpaths.