Deployed 74558a4 with MkDocs version: 1.6.0

adding_software/debugging_failed_builds/index.html

@@ -2075,7 +2075,7 @@ <h3 id="building-for-the-generic-optimization-target">Building for the <code>gen
 <div class="highlight"><pre><span></span><code><a id="__codelineno-11-1" name="__codelineno-11-1" href="#__codelineno-11-1"></a>export EESSI_CPU_FAMILY=$(uname -m) &amp;&amp; export EESSI_SOFTWARE_SUBDIR_OVERRIDE=${EESSI_CPU_FAMILY}/generic
 </code></pre></div></p>
 <h2 id="building-software-with-the-eessi-install-softwaresh-script">Building software with the <code>EESSI-install-software.sh</code> script<a class="headerlink" href="#building-software-with-the-eessi-install-softwaresh-script" title="Permanent link">&para;</a></h2>
-<p>The Automatic build and deploy <a href="../../bot/">bot</a> installs software by executing the <code>EESSI-install-software.sh</code> script. The advantage is that running this script is the closest you can get to replicating the bot's behaviour - and thus the failure. The downside is that if a PR adds a lot of software, it may take quite a long time to run - even if you might already know what the problematic software package is. In that case, you might be better off following the steps under (Building software from an easystack file)[#building-software-from-an-easystack-file] or (Building an individual package)[#building-an-individual-package].</p>
+<p>The Automatic build and deploy <a href="../../bot/">bot</a> installs software by executing the <code>EESSI-install-software.sh</code> script. The advantage is that running this script is the closest you can get to replicating the bot's behaviour - and thus the failure. The downside is that if a PR adds a lot of software, it may take quite a long time to run - even if you might already know what the problematic software package is. In that case, you might be better off following the steps under <a href="#building-software-from-an-easystack-file">Building software from an easystack file</a> or <a href="#building-an-individual-package">Building an individual package</a>.</p>
 <p>Note that you could also combine approaches: first build everything using the <code>EESSI-install-software.sh</code> script, until you reproduce the failure. Then, start making modifications (e.g. changes to the EasyConfig, patches, etc) and trying to rebuild that package individually to test your changes.</p>
 <p>To build software using the <code>EESSI-install-software.sh</code> script, you'll first need to get the diff file for the PR. This is used by the <code>EESSI-install-software.sh</code> script to see what is changed in this PR - and thus what needs to be build for this PR. To download the diff for PR 360, we would e.g. do
 <div class="highlight"><pre><span></span><code><a id="__codelineno-12-1" name="__codelineno-12-1" href="#__codelineno-12-1"></a>wget https://github.com/EESSI/software-layer/pull/360.diff
@@ -2200,7 +2200,7 @@ <h3 id="the-writeable-overlay">The writeable overlay<a class="headerlink" href="
     <span class="md-icon" title="Last update">
       <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M21 13.1c-.1 0-.3.1-.4.2l-1 1 2.1 2.1 1-1c.2-.2.2-.6 0-.8l-1.3-1.3c-.1-.1-.2-.2-.4-.2m-1.9 1.8-6.1 6V23h2.1l6.1-6.1-2.1-2M12.5 7v5.2l4 2.4-1 1L11 13V7h1.5M11 21.9c-5.1-.5-9-4.8-9-9.9C2 6.5 6.5 2 12 2c5.3 0 9.6 4.1 10 9.3-.3-.1-.6-.2-1-.2s-.7.1-1 .2C19.6 7.2 16.2 4 12 4c-4.4 0-8 3.6-8 8 0 4.1 3.1 7.5 7.1 7.9l-.1.2v1.8Z"/></svg>
     </span>
-    <span class="git-revision-date-localized-plugin git-revision-date-localized-plugin-date">March 27, 2024</span>
+    <span class="git-revision-date-localized-plugin git-revision-date-localized-plugin-date">June 4, 2024</span>
   </span>