BEGIN:VCALENDAR
VERSION:2.0
PRODID:Linklings LLC
BEGIN:VTIMEZONE
TZID:America/Denver
X-LIC-LOCATION:America/Denver
BEGIN:DAYLIGHT
TZOFFSETFROM:-0700
TZOFFSETTO:-0600
TZNAME:MDT
DTSTART:19700308T020000
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0600
TZOFFSETTO:-0700
TZNAME:MST
DTSTART:19701101T020000
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTAMP:20200129T163600Z
LOCATION:605
DTSTART;TZID=America/Denver:20191118T090500
DTEND;TZID=America/Denver:20191118T093200
UID:submissions.supercomputing.org_SC19_sess116_ws_hust103@linklings.com
SUMMARY:Buildtest: A Software Testing Framework with Module Operations for
  HPC systems
DESCRIPTION:Workshop\n\nBuildtest: A Software Testing Framework with Modul
 e Operations for HPC systems\n\nSiddiqui\n\nHPC support teams are often ta
 sked with installing scientific software for their user community and the 
 complexity of managing a large software stack gets very challenging. Softw
 are installation brings forth many challenges that requires a team of doma
 in expertise and countless hours troubleshooting to build an optimal softw
 are state that is tuned to the architecture. In the past decade, two softw
 are build tools (Easybuild, Spack) have emerged that are widely accepted i
 n HPC community to accelerate building a complete software stack for HPC s
 ystems.  The support team are constantly involved in fulfilling software r
 equest for end-users which leads to an ever-growing software ecosystem. On
 ce a software is installed, the support team hands it off to the user with
 out any testing because scientific software requires domain expertise in o
 rder to test software. Some software packages are shipped with a test suit
 e that can be run at post build while many software have no mechanism for 
 testing. This poses a knowledge gap between HPC support team and end-users
  on the type of testing to do. Some HPC centers may have developed in-hous
 e test scripts that are suitable for testing their software, but these tes
 ts are not portable due to hardcoded paths and are often site dependent. I
 n addition, there is no collaboration between HPC sites in building a test
  repository that will benefit the community. This paper presents buildtest
 , a framework to automate  testing for a software stack along with several
  module operations that would be of interest to HPC support teams.\n\nTag:
  Workshop Reg Pass, Best Practices, Build Systems, Datacenter, HPC Center 
 Planning and Operations, Parallel Application Frameworks, System Testing, 
 Tools\n\nRegistration Category: Workshop Reg Pass, Best Practices, Build S
 ystems, Datacenter, HPC Center Planning and Operations, Parallel Applicati
 on Frameworks, System Testing, Tools
URL:https://sc19.supercomputing.org/presentation/?id=ws_hust103&sess=sess1
 16
END:VEVENT
END:VCALENDAR