<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
On 01/05/2012 12:40 AM, Xie Ruohong wrote:
<blockquote
cite="mid:CAF+pHqf-9RjJhKp-3ewHieL53-X700LF6UniDT9wMWMjfHUZog@mail.gmail.com"
type="cite"><span>Hello,</span>
<div><br>
</div>
<div>We developed an operating system and hope to get LSB
certification. We have run LSB distribution checker and there
are some fails which we believe are due to the incorrect tests. </div>
<div><br>
</div>
<div>The four fails are list below:</div>
<div><br>
</div>
<div>
<div><b>/olver/time/timer/tests/timer_getoverrun_spec 1<span
style="white-space: pre-wrap;"> </span>failed<span
style="white-space: pre-wrap;"> </span></b></div>
<div>Message from the test:</div>
<div>failure 285</div>
<div>--------------------------------</div>
<div>Scenario time_timer_created_timers_scenario:</div>
<div>MEDIATOR_FAILED</div>
<div>Execution failed</div>
<div>Comment:</div>
<div>Test Purpose Comment: Check extra requirement</div>
<div>Open the journal:</div>
<div>/var/opt/lsb/test/manager/results/IA64-sp3k-2011-12-30-16h-28m-02s/results/olver.journal:23602</div>
<div><br>
</div>
<div><b>/olver/time/timer/tests/timer_getoverrun_spec 2<span
style="white-space: pre-wrap;"> </span>failed<span
style="white-space: pre-wrap;"> </span></b></div>
<div>Message from the test:</div>
<div>failure 286</div>
<div>--------------------------------</div>
<div>Scenario time_timer_timers_crash_scenario:</div>
<div>MEDIATOR_FAILED</div>
<div>Execution failed</div>
<div>Comment:</div>
<div>Test Purpose Comment: Check extra requirement</div>
<div>Open the journal:</div>
<div>/var/opt/lsb/test/manager/results/IA64-sp3k-2011-12-30-16h-28m-02s/results/olver.journal:23611</div>
<div><br>
</div>
<div><b>/olver/time/timer/tests/timer_gettime_spec 1<span
style="white-space: pre-wrap;"> </span>failed<span
style="white-space: pre-wrap;"> </span></b></div>
<div>Message from the test:</div>
<div>failure 287</div>
<div>--------------------------------</div>
<div>Scenario time_timer_timers_crash_scenario:</div>
<div>MEDIATOR_FAILED</div>
<div>Execution failed</div>
<div>Comment:</div>
<div>Test Purpose Comment: Check extra requirement</div>
<div>Open the journal:</div>
<div>/var/opt/lsb/test/manager/results/IA64-sp3k-2011-12-30-16h-28m-02s/results/olver.journal:23670</div>
<div><br>
</div>
<div><b>/olver/time/timer/tests/timer_delete_spec 1<span
style="white-space: pre-wrap;"> </span>failed<span
style="white-space: pre-wrap;"> </span></b></div>
<div>Message from the test:</div>
<div>failure 288</div>
<div>--------------------------------</div>
<div>Scenario time_timer_timers_crash_scenario:</div>
<div>MEDIATOR_FAILED</div>
<div>Execution failed</div>
<div>Comment:</div>
<div>Test Purpose Comment: Check extra requirement</div>
<div>Open the journal:</div>
<div>/var/opt/lsb/test/manager/results/IA64-sp3k-2011-12-30-16h-28m-02s/results/olver.journal:23788</div>
</div>
<div>
<div><br>
</div>
<div>The four fails have similar output. I check the test source
code and found they use incorrect timerid. In these tests, a
timer will be created by <i>timer_create()</i> and return <i>timerid</i>.
The program use <i>int</i> type to store <i>timerid</i>. But <i>timerid</i> is
64-bits while <i>int</i> is 32-bits on IA64 platform. So the<i>timerid</i> will
be truncated to an incorrect value. Then test program will use
the incorrect value and generate a segmentation fault.</div>
<div><br>
</div>
<div>How should we deal with these fails? </div>
<div><br>
</div>
</div>
</blockquote>
Please file a bug at lsbbugs.linuxfoundation.org. Looking at the
open bugs on olver-core I don't see anything that looks similar to
this. In the past we have run validation runs of the tests,
pre-release on all the architectures and I generally open bugs on
issues such as this that seem arch specific. At the moment I don't
have access to an IA64 machine to check.<br>
<br>
Opening a bug will be a starting point for any possible waiver and
an entry in the problem_db (when it comes back online).<br>
<br>
You can still submit your results for certification with the
failures if you're convinced it's a test issue and it will be
addressing during your results audit.<br>
<br>
-- <br>
<pre class="moz-signature" cols="72">Stew Benedict
</pre>
</body>
</html>