<html>
<body>
<div style="font-family: Verdana, Arial, Helvetica, Sans-Serif;">
<table bgcolor="#f9f3c9" width="100%" cellpadding="8" style="border: 1px #c9c399 solid;">
<tr>
<td>
This is an automatically generated e-mail. To reply, visit:
<a href="https://reviewboard.asterisk.org/r/1796/">https://reviewboard.asterisk.org/r/1796/</a>
</td>
</tr>
</table>
<br />
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: 10px;">
<p style="margin-top: 0;">On March 20th, 2012, 9:59 a.m., <b>Russell Bryant</b> wrote:</p>
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: 10px;">
<pre style="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">How many cases are there where we *do* want a test to run on older versions, but not newer versions? That's the case where this change would be annoying. If there are very very few of them, I suppose it's not a big deal.</pre>
</blockquote>
<p>On March 20th, 2012, 10:02 a.m., <b>Paul Belanger</b> wrote:</p>
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: 10px;">
<pre style="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">At the moment, zero. We have been making sure all tests run on trunk, regardless if a test is considered old.</pre>
</blockquote>
<p>On March 20th, 2012, 10:22 a.m., <b>opticron</b> wrote:</p>
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: 10px;">
<pre style="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">So when we remove a deprecated feature from trunk for which there exists a test, do we remove that test?</pre>
</blockquote>
<p>On March 20th, 2012, 11:34 a.m., <b>Paul Belanger</b> wrote:</p>
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: 10px;">
<pre style="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">No sure, we haven't come across this situation yet. Something we have to consider, but don't think it will happen to often at the moment.</pre>
</blockquote>
<p>On March 20th, 2012, 2:52 p.m., <b>opticron</b> wrote:</p>
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: 10px;">
<pre style="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">Given that we're going to be dropping 1.4 and 1.6.2 in the near future, only being able to skip individual branches is maintainable for the near term. I see this more as an augment to the minversion/maxversion rather than a replacement since min/maxversion deal with open-ended ranges while this skip functionality deals with individual branches. I don't remember if min/maxversion also handles down to the tag level, but if it does that would also be an issue.</pre>
</blockquote>
<p>On March 22nd, 2012, 9:04 a.m., <b>Matt Jordan</b> wrote:</p>
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: 10px;">
<pre style="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">I agree with Kinsey. I don't think we should necessarily remove the minversion or maxversion checking that already exists, nor do I think we should remove the ability to simply skip a test for all branches. I'd prefer this functionality to exist along side that. That keeps the current capabilities of the test suite intact, but gives us the additional flexibility that is needed and that this patch does provide.</pre>
</blockquote>
<p>On March 22nd, 2012, 9:44 a.m., <b>Paul Belanger</b> wrote:</p>
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: 10px;">
<pre style="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">If we keep the minversion / maxversion flag, what is the actually version order including the digiumphones? I consider the digiumphones a parallel branch, and using something like minversion / maxversion does not work in that scenario. So, I'm having trouble seeing how we can use ranges with different version of asterisk (1.8/10/trunk s vs 1.8-digiumphones).</pre>
</blockquote>
<p>On March 22nd, 2012, 10 a.m., <b>opticron</b> wrote:</p>
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: 10px;">
<pre style="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">I would expect 1.8-digiumphones to be treated exactly like 1.8 as far as minversion/maxversion go. For the digiumphones branch tests, you'd then have minversion=1.8, skip 1.8, skip 10 so that the digiumphones branches of 1.8 and 10 will be run along with any future versions of asterisk that will (presumably) have this feature. This has the potential to be confusing for who are not familiar with the digiumphones branches, but those people are unlikely to be writing tests for the digiumphones branches specifically.</pre>
</blockquote>
<p>On March 22nd, 2012, 10:01 a.m., <b>rmudgett</b> wrote:</p>
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: 10px;">
<pre style="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">I suppose you could consider the 1.8-digiumphones as v1.9 since it backports several things from v10.</pre>
</blockquote>
</blockquote>
<pre style="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">It also has things that are specific to the branch and that are not in version 10, such as the AMI "ParkingLots" action. When testing those things, you'd need to test ONLY that version and, once they're merged to trunk, 11 and beyond. So you'd want to do something like have the minversion as 1.8-digiumphones and skip 10.</pre>
<br />
<p>- Mark</p>
<br />
<p>On March 6th, 2012, 11:02 a.m., Paul Belanger wrote:</p>
<table bgcolor="#fefadf" width="100%" cellspacing="0" cellpadding="8" style="background-image: url('https://reviewboard.asterisk.org/media/rb/images/review_request_box_top_bg.png'); background-position: left top; background-repeat: repeat-x; border: 1px black solid;">
<tr>
<td>
<div>Review request for Asterisk Developers.</div>
<div>By Paul Belanger.</div>
<p style="color: grey;"><i>Updated March 6, 2012, 11:02 a.m.</i></p>
<h1 style="color: #575012; font-size: 10pt; margin-top: 1.5em;">Description </h1>
<table width="100%" bgcolor="#ffffff" cellspacing="0" cellpadding="10" style="border: 1px solid #b8b5a0">
<tr>
<td>
<pre style="margin: 0; padding: 0; white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">I'm looking for some initial feedback on the following patch. Since we have the digiumphones branch now, we need to rework on the testsuite handles asterisk versions. Before we used minversion / maxversion (which worked across branches) however this does not work well if you have a parallel branch.
So, I've removed them in favour of 'skip'. Basically, the testsuite will run on every version of asterisk unless you have 'skip' defined, then depending on the flag (right now branch) it checks to run or skip the test.
We currently use the 'skip' flag, but only for a basic check. At the moment to skip broken tests, this new method would give us more control on the type of tests to skip. EG: Skip if OS is FreeBSD or skip if arch is i386.</pre>
</td>
</tr>
</table>
<h1 style="color: #575012; font-size: 10pt; margin-top: 1.5em;">Testing </h1>
<table width="100%" bgcolor="#ffffff" cellspacing="0" cellpadding="10" style="border: 1px solid #b8b5a0">
<tr>
<td>
<pre style="margin: 0; padding: 0; white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">Local dev box.
There is also more work needed to be done in updating the test-config.yaml files, however I want to get this patch reviewed before making all those changes.</pre>
</td>
</tr>
</table>
<h1 style="color: #575012; font-size: 10pt; margin-top: 1.5em;">Diffs</b> </h1>
<ul style="margin-left: 3em; padding-left: 0;">
<li>asterisk/trunk/lib/python/asterisk/TestConfig.py <span style="color: grey">(3083)</span></li>
<li>asterisk/trunk/lib/python/asterisk/version.py <span style="color: grey">(3083)</span></li>
<li>asterisk/trunk/runtests.py <span style="color: grey">(3083)</span></li>
<li>asterisk/trunk/tests/channels/SIP/message_auth/test-config.yaml <span style="color: grey">(3083)</span></li>
</ul>
<p><a href="https://reviewboard.asterisk.org/r/1796/diff/" style="margin-left: 3em;">View Diff</a></p>
</td>
</tr>
</table>
</div>
</body>
</html>