Telcon: 2023 11 29

Wednesday November 29th, 9am PT (UTC -8:00)

Attendees

• Peter Scheibel (host)
• Todd Gamblin
• Chris Green
• Prentice Bisbal
• Dom Heinzeller
• Mark Krentel
• Massimiliano Culpo
• Srinath Vadlamani
• Tammy Dahlgren
• Yang Liu
• Davide DelVento
• Richard Lawrence

Agenda

Pre-planned general topics:

• Coordinating nightly builds with other users

  • Can we provide a dashboard for users to upload to?
  • e.g. if they do a nightly build
  • From meeting:
    • (High level): we want to generate docs for
      • given a spack.yaml Environment file, how do we generate cdash output for build results (and upload it)
    • Side Notes
      • Users have other hardware, they want to verify that spack packages build on their system
        • For this the users can run nightly builds off of spack develop
        • And then they can upload results
      • A couple mechanisms:
        • Example: spack install --tests using a Spack environment
          • This Generates cdash output
        • See: spack install --help-cdash
        • Use spack ci to generate the pipeline
      • There is a cdash site, we can upload to it
        • https://cdash.spack.io/index.php?project=Spack%20Testing
        • e.g. https://cdash.spack.io/index.php?project=Spack+Testing&date=2023-11-29
        • Assuming someone has the credentials, what commands need to be run?
          • https://spack.readthedocs.io/en/latest/pipelines.html
        • We need to coordinate with KitWare folks on how to get the appropriate credentials
        • Specify cdash endpoint: https://github.com/spack/spack/blob/develop/share/spack/gitlab/cloud_pipelines/configs/cdash.yaml
      • Slack channel: https://app.slack.com/client/T5URKQG73/C02N33GM28H

• (delayed) Spack PR reviewer onboarding process:

  • Currently, maintainers are invited to get triage permissions on PRs
  • Do we have other mechanisms for adding reviewers?
  • What about for merge permissions?

Ad-hoc discussion items

• Chris: https://github.com/spack/spack/pull/40018
  • Peter: still have this in my queue
• Chris: mypy change
  • Version in CI is pinned
  • Version in bootstrapping is not
  • Fixed in: https://github.com/spack/spack/pull/41245
  • Chris: fixed this independently in https://github.com/FNALssi/spack/pull/238
    • This fixes the mypy errors
• Richard: if we can provide cycles for running CI jobs, how do we integrate that with Spack?
  • Todd: will talk on future telcon about this