Skip to content

Telcon: 2022 04 13

Jump to bottom Edit New page
Peter Scheibel edited this page Apr 13, 2022 · 27 revisions

Attendees

  • Peter Scheibel (host)
  • Massimiliano Culpo
  • Richarda Butler
  • Mark Krentel
  • Tammy Dahlgren
  • Todd Gamblin
  • Brian Van Essen
  • Phil Regier
  • Greg Becker

Agenda items

  • (Todd) 0.18 is coming out in 4 weeks

    • --reuse will be default
    • Plans for a public buildcache

  • (Brian) Spack intermittent download failures

    • (Todd) is this a matter of urllib vs. curl?
    • (Mark) noticed that things fail with savannah.nongnu URLs when using urllib, but not with curl
    • (Todd) you can set this with url_fetch_method: curl in config.yaml
      • If this works, then Spack should probably be updated to check if we can find certs for urllib
    • This can also be a matter of site policy (e.g. if they interfere with some URLs)

  • (Brian) #28367: issue with building PyTorch on Power machines

    • This is with some newer versions of PyTorch
    • So the Spack PyTorch package could constrain not to build with those newer version
    • Or: the patch is suboptimal (could be better), but it could still be applied for the Spack package
      • (Peter) We spoke about a possible warning directive in a prior meeting: would that be useful here?

  • (Brian) When working off the head of develop, there can be "too much change" in terms of what gets installed

    • (Todd) How much does --reuse help?
      • (Brian) Definitely some
    • --reuse will be default in 0.18

  • (Todd) public build cache

    • How will compiler compatibility affect reuse from the build cache?
      • If you build with GCC 9.5, Spack should probably allow using dependency binary caches built with GCC 9.4

  • (Brian) limitations to configuration yaml files from the commmand line

    • (Brian) Sometimes in scripts I append a yaml file
      • Is there a way to merge this into a config?
        • (Greg) spack config add can be used to merge one config file into another

  • Continue from https://github.com/spack/spack/wiki/Telcon%3A-2022-03-30: vendored CUDA dependencies

    • OpenMPI etc. will continue to be bundled with CUDA
      • If the implementation is distinct we can model the package to provide mpi (i.e. we don't have to make openmpi virtual)

  • Continue from https://github.com/spack/spack/wiki/Telcon%3A-2022-04-06: not in spec syntax

    • (Peter) When does conflicts not address this?
      • If we only want to define certain variants/dependencies conditionally, such that they don't appear on the Spec at all
      • If we only want only (x or y) (although we also don't have or)
    • (New: April 11) https://github.com/spack/spack/pull/29943#pullrequestreview-938727865 suggests a mechanism for handling this

Possible Agenda items

Add a custom footer
Clone this wiki locally