Telcon: 2018 02 22
scheibelp edited this page Feb 22, 2018
·
26 revisions
- Daniel Topa
- Mike Pozulp
- John Rood
- Patrick Gartung
- Ben Boeckel
- Greg Becker
- Improved log parsing (for error logs generated by failed package builds): https://github.com/spack/spack/pull/7093
- Improved command help: https://github.com/spack/spack/pull/7214
- Bug fix to allow ignoring conflicts for extension packages added to views: https://github.com/spack/spack/pull/7167
- Bug fix for flag handler support (python version issue): https://github.com/spack/spack/pull/6960
(whatever concerns anyone wants to bring up - bugs impacting usability, required features, unmerged PRs, etc.)
- Buildcache updates https://github.com/spack/spack/pull/7314
- Mark packages which can't be relocated (e.g. tcl) and don't create caches for them
- Daniel: power9 issues 7307/7309
- Daniel: LLVM issue for older versions of LLVM: https://github.com/spack/spack/issues/7248
- Python3 + boost is having an issue: https://github.com/spack/spack/issues/7170
- John: PR 7245
- Mike: PR 7313
- Failure to install llvm-lld
- lld is version-bound to llvm but Spack was building different versions
- llvm Spack package builds several components, so the PR removes the separate llvm-lld package
- John: how to deal with growth of Spack project
- Mike: if we are building a set of packages and want to ensure that the latest Spack can build those packages, can we set up a cron job to test building them (proposed by Gabriel Rockefeller, David Montoya)?
- Could this integrate with cdash (i.e. if the central site could trust specific users)
- Ben: cdash site only trusts specific machines for results cron jobs could send emails