--- layout: default ---

{{page.title}}

Updated on {{page.date | date: "%d/%m/%Y"}} {% for cat in page.categories %} {% for catDat in site.data.categories %} {% if catDat.slug == cat %} {% assign catego = catDat %} {% endif %} {% endfor %} {% if catego %} {{ catego.name }}{% unless forloop.last %},{% else %}.{% endunless %} {% endif %} {% endfor %}🗒️ Edit on GitHub
<< Home
{{ content }}

This plot shows the top level splice outcomes, meaning across testers. For example, if a package or splice didn't concretize we will see it here.

Outcomes

  • combination-not-run: 0
  • {% for outcome in page.outcomes %}
  • {{ outcome[0] }}: {{ outcome[1]}}
  • {% endfor %}

Plot of Outcomes

Across an experiment, we have multiple testers. However, sometimes there is a failure unrelated to the tester. For example, a concretization fails, spack can't install the package, and then we can't be sure if the splice failed (or otherwise had a bad outcome) or if it's spack. This is a visualization of the outcomes above, colored by the values indicated.

{% if page.pdf %}Download PDF |{% endif %} {% if page.png %}Download PNG |{% endif %} {% if page.svg %}Download SVG{% endif %} {% if page.svg %}{% endif %} {% if page.results %}

Results

Since results (and outputs) can vary across testers, we provide an interactive table here for you to explore instead of trying to shove them into a visualization. The raw data is provided alongside each results directory, so you are free to grab it to generate a custom visualization to your liking.

Tester Package Splice Binary Library Prediction Message Return Code Command Outcome
{% endif %}
{% for tag in page.tags %} {% capture test %}{{tag | slice: 0}}{% endcapture %} {% capture testup %}{{tag | slice: 0 | upcase}}{% endcapture %}
{{tag}}
{% endfor %}
{% include search_form.html %}