Skip to content

Telcon: 2022 06 29

Jump to bottom Edit New page
Peter Scheibel edited this page Jun 29, 2022 · 17 revisions

Attendees

  • Peter Scheibel (host)
  • Massimiliano Culpo
  • Richarda Butler
  • Matt Belhorn (OLCF)
  • Greg Becker
  • Brian Van Essen
  • Todd Gamblin
  • Phil Sakievich

Agenda items

  • Brian: unify: false - why is that the default?
    • All created environments have unify: false explicitly added (with spack create)
    • As a side effect, if you
    • true would make more sense
    • Next Spack release will change away from unify: false
      • Unify-when-possible might be the safest default in the sense that it avoids concretization errors
      • But... it doesn't necessarily produce what users might expect (i.e. if they aren't aware, then they might get different installs of things)
  • The annoyances of ~ configuration came up
    • Also strategies for combining configurations for user experience
    • Phil: CI runs with the config they provide to users
    • Brian: externals are a pain that often influence config: can sites define a Cray-manifest analog (i.e. describing already-installed DAGs that are available)
      • Peter: at the moment creating a manifest file is time-consuming so IMO would be primarily useful for "slow-changing" packages
  • Best-effort co-concretization PR prevents concretizing specs on the command line
  • Massimiliano: 0.18 had a performance regression that will be fixed in 0.18.1 and also if you pull the latest develop branch
  • Brian: it would be nice if labs could share their individual Spack forks
    • Then if someone from one lab had a problem they could check if another lab had already addressed it
    • Phil: generally can make use of package inheritance to minimize differences
      • Peter: this works unless you need to remove constraints
        • There are efforts to address this

Possible Agenda items

Add a custom footer
Clone this wiki locally