On Mon, 2007-09-10 at 15:22 -0400, Jeff Burke wrote: > Subrata, > In my opinion it would be much better for this list to be on a wiki. So > we have one master list. That everyone can update. Also so we don't
Thatś correct. But everybody will not have access to the wiki. So, if you can mail me your findings and link, i can update the wiki immediately. Meanwhile i have not yet heard (from anybody on the mailing list) any other cases other than this attachment. May i assume that whatever other testcases you are executing in LTP are correct ?? and does not need to be addressed for failures and False positives ?? > loose items in the when people are replying. We could add links to the > wiki with examples of the failures. It would be nice to list the other > things as well. For example the Arch the false positive occurs on "All", > "i686", x86_64. also well as distro "All", "RHEL5", "SLES", "Ubuntu" > > I guess I would like to also better define the definition of a false > positive vs broken test case. For example the f00f test currently fails > on systems that have the NX bit enable. If the NX bit is enabled it > doesn't return SIGILL it returns SIGSEGV. Sure, please go ahead in defining what is what. We will also have this on our ltp wiki (http://ltp.sourceforge.net/wiki/) *** It would be great if some patch is forthcoming from anybody who foresees any problem in any testcase(s) *** > > Thanks, > Jeff > > Subrata Modak wrote: > > Hi, > > > > We have been hearing some couple of fuming faces for LTPś Broken Test > > cases, commonly known as false positives. Yes there are hundreds of such > > Test cases which has not been updated for quite some time. So, the > > functionality they test may have undergone changes during that period. > > Hence, we need to revisit/rework the way they report PASS or FAIL. > > Following is attached an initial set of Test cases, which according to > > [EMAIL PROTECTED] reports false positives. Our aim is to make this as > > comprehensive as we can and then swiftly act upon these erring test > > cases before they loose their value. I would request you to add your > > entries to this list (as well as the reasons/observations/conditions for > > which they report false positives). We would work out to include fixes > > for them. > > > > --Regards-- > > Subrata > > > > > > > > > > ------------------------------------------------------------------------ > > > > **************************************************************************************************************************** > > * Test-Case Type * > > Broken-Issue(s) * > > **************************************************************************************************************************** > > | fcntl17 | > > attempt to signal child failed > > | > > ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > | fsync | > > took too long > > | > > ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > | gettimeofday | > > is going backwards > > | > > ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > | gf18 | > > > > | > > ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > | mlockall | > > > > | > > ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > | msg |call failed - > > erro=28 (note: after you get error 28 or 'device out of space, you'll get > > tons | > > | |and tons of > > msg* error msgs that are safe to ignore. I think this tends to happen only > > | > > | | when swap is > > less than 2*ram, and perhaps only on RHEL) > > | > > ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > | nanosleep |remaining time > > doesn't match foo > > | > > ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > | pselect |sleep time was > > incorrect > > | > > ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > | syslog |ailed to log > > msgs of all levels > > | > > ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > | capset02 |BROK > > Unexpected signal 15 received(matrix issue 1234 - if you see this, please > > mark as | > > | | PASS, but > > attach the issue to help establish trends) > > | > > ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > | getsid02 | > > > > | > > ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > | ioperm | > > > > | > > ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > | setpgid |expect EACCES > > got 1 (21134 mention, ltp SF bug 1114033) > > | > > ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > | shmctl01 |FAIL : # of > > attaches is incorrect > > | > > ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > | shmget02 |FAIL: call > > succeeded unexpectedly > > | > > ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > | socket | > > > > | > > ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > | syslogd |no such > > command (21068 - diff failure than the historical) > > | > > ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > | vmsplice01 |1 FAIL : > > vmsplice() Failed, errno=38 > > | > > ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > > > > > _______________________________________________ > > Ltp-list mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/ltp-list > ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Ltp-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ltp-list
