<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Overcoming Challenges to Continuous Integration in HPC · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2303.17034/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/2303.17034/feed.xml" rel="self" type="application/rss+xml" /><item><title>Overcoming Challenges to Continuous Integration in HPC — mentioned by jfkfif</title><link>https://news.ycombinator.com/item?id=39685797</link><guid isPermaLink="false">urn:hackerpapers:mention:2303.17034:39685797</guid><pubDate>Tue, 12 Mar 2024 22:39:14 GMT</pubDate><description>&lt;p&gt;HPC, or scientific computing more generally, are slow when it comes to adopting modern software development practices. Most researchers used to only care about results above all, rather than reliability or reproducibility for other users. DOE initiatives [0] in the past couple years have done a lot to change this, though there are significant hurdles from a security and logistical standpoint [1]. For instance, to uncover issues in a PR, you might need to run the code at &amp;gt;64 nodes on a shared system. [0] https://ecp-ci.gitlab.io/docs/admin/jacamar/introduction.htm... [1]…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2303.17034/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.DC</category></item></channel></rss>
