<html>
    <head>
      <base href="https://bugs.dpdk.org/">
    </head>
    <body><table border="1" cellspacing="0" cellpadding="8" class="bz_new_table">
        <tr>
          <th>Bug ID</th>
          <td><a class="bz_bug_link 
          bz_status_UNCONFIRMED "
   title="UNCONFIRMED - Make limited use of "per testsuite" conf files."
   href="https://bugs.dpdk.org/show_bug.cgi?id=1375">1375</a>
          </td>
        </tr>

        <tr>
          <th>Summary</th>
          <td>Make limited use of "per testsuite" conf files.
          </td>
        </tr>

        <tr>
          <th>Product</th>
          <td>DPDK
          </td>
        </tr>

        <tr>
          <th>Version</th>
          <td>unspecified
          </td>
        </tr>

        <tr>
          <th>Hardware</th>
          <td>All
          </td>
        </tr>

        <tr>
          <th>OS</th>
          <td>All
          </td>
        </tr>

        <tr>
          <th>Status</th>
          <td>UNCONFIRMED
          </td>
        </tr>

        <tr>
          <th>Severity</th>
          <td>normal
          </td>
        </tr>

        <tr>
          <th>Priority</th>
          <td>Normal
          </td>
        </tr>

        <tr>
          <th>Component</th>
          <td>dts
          </td>
        </tr>

        <tr>
          <th>Assignee</th>
          <td>dev@dpdk.org
          </td>
        </tr>

        <tr>
          <th>Reporter</th>
          <td>probb@iol.unh.edu
          </td>
        </tr>

        <tr>
          <th>CC</th>
          <td>juraj.linkes@pantheon.tech, probb@iol.unh.edu
          </td>
        </tr>

        <tr>
          <th>Target Milestone</th>
          <td>---
          </td>
        </tr></table>
      <p>
        <div class="bz_comment_block">
          <pre class="bz_comment_text">There will be examples of testsuite which require some divserse input on a per
testsuite or environment basis (setting expected baselines for a testsuite in
perf testing is one example). So, we are going to be doing this at some point
anyways, and I think it is okay to do so now with functional tests too if it
can help make testsuites more concise.

I don't want this suggestion to be conflated with our previous discussion about
building a YAML schema and intepreter for taking testsuite parameters and also
python functions and mapping that to a python testsuite. I think it's clear
based on our 1/24 meeting that we are not going in that direction. However, we
probably do need per-testsuite conf files for some (but not all) suites. I
think how we best leverage this can be a discussion point for next week's DTS
meeting.
          </pre>
        </div>
      </p>


      <hr>
      <span>You are receiving this mail because:</span>

      <ul>
          <li>You are the assignee for the bug.</li>
      </ul>
      <div itemscope itemtype="http://schema.org/EmailMessage">
        <div itemprop="action" itemscope itemtype="http://schema.org/ViewAction">
          
          <link itemprop="url" href="https://bugs.dpdk.org/show_bug.cgi?id=1375">
          <meta itemprop="name" content="View bug">
        </div>
        <meta itemprop="description" content="Bugzilla bug update notification">
      </div>
    </body>
</html>