<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div><div>On 12 May 2016, at 21:37, Frank Loeffler <<a href="mailto:knarf@cct.lsu.edu">knarf@cct.lsu.edu</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">On Thu, May 12, 2016 at 08:00:40PM +0200, Eloisa Bentivegna wrote:<br><blockquote type="cite">this is really due to the fact that this specific variable<br>(ct_multilevel-err) should not be tested for relative changes, as it's<br>difficult to define a natural tolerance, and sometimes even the smallest<br>differences in execution lead to very large relative changes. I have<br>just pushed a commit that makes sure that a failure is only triggered if<br>the absolute difference is above threshold.<br></blockquote><br>That is great, thanks.<br><br>On the other hand, the actual change that most likely triggered this<br>was a change in option lists on Jenkins, and there most likely the<br>-Ofast option. Before build #758 [1], the Jenkins VM used a special<br>jenkins option list, and starting with that build, it now uses the<br>generic Ubuntu option list.<br><br>Now, the tests should obviously also pass using that option list, but I<br>found it interesting to know why it started to fail when it did. Was the<br>change in option list intentional?<br></blockquote><div><br></div><div>Hi Frank,</div><div><br></div><div>No, this was not intentional. The change in question (<a href="https://bitbucket.org/ianhinder/cactusjenkins/commits/d7021a52bd83448db589b2346c43441682eecabb">https://bitbucket.org/ianhinder/cactusjenkins/commits/d7021a52bd83448db589b2346c43441682eecabb</a>) was not supposed to change the optionlist used for the main ET job, but now that I look at it, I see that it had exactly that effect. I think when I first made the change, I was working on a separate copy of the repository that wouldn't affect the main job, but when I committed it a few days later, I forgot that I needed to add an exclusion if it was in the main job. </div><div><br></div><div>I could add such an exclusion, but since it seems to work now and it is better to test the main ubuntu optionlist, I think I will just leave it as-is. Do you agree?</div><div><br></div><div>This will also have the effect of making the builds slower, as the standard ubuntu optionlist does not use ccache.</div><div><br></div></div><div apple-content-edited="true">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div>-- </div><div>Ian Hinder</div><div><a href="http://members.aei.mpg.de/ianhin">http://members.aei.mpg.de/ianhin</a></div></div></div></div></div>
</div>
<br></body></html>