[lsb-discuss] Unresolved result in LSB test
Stew Benedict
stewbintn at gmail.com
Wed Feb 1 17:56:16 UTC 2012
On 02/01/2012 12:27 PM, Andrew Josey wrote:
> hi Stew, all
>
> I asked my engineers who maintain these tests, and the response is below, note that we refer to a variable SPEEDFACTOR that can impact the tests, I'm not sure how you set that within the LSB tests these days...
> regards
> Andrew
>
Thanks Andrew. SPEEDFACTOR looks to be set to 5 currently, I don't
believe this has changed in some time. I did push some changes that
would be in the core-test (formerly runtime-test) version mentioned that
attempt to set the SPEEDFACTOR for a couple of specific tests at
runtime, vs compile time. I limited the change to only the tests in
question, as we haven't seen any widespread issues with the given value
and I wasn't even really able to duplicate the issues with these tests,
but the changes didn't seem to cause any regressions in my testing.
Those tests were:
/tset/LSB.os/procprim/exec_L/T.exec{l,le,lp,v,ve,vp}_L 7 and
/tset/LSB.os/mfiles/msync_P/T.msync_P 1
https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=1614
https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=1618
--
Stew Benedict
More information about the lsb-discuss
mailing list