Re: [Fuego] LTP and POSIX test suite report

Hi Tim,

We analysed the previous test error report and sorted out some TCONF errors
but still some errors are coming.
We ran the latest ltp(20210524) test  on a raspberry pi board and we have
prepared the test error reports for both tests based on the output we got .

we have some observations:

   -  tests which failed as TCONF test error , shows status as "pass" in
   run.json log file.

               for an example :  fork14 which gives the  error as -  mmap()
fails too many times,so we are almost impossibleto get an vm_area_structsized
16TB.
                    but in run.json shows status as pass . like  below
               {
                    "name": "fork14",
                    "status": "PASS"
                }
          query is on what bases tests are considered as pass or fail in
the ltp?


   - Most of the TCONF failed tests are due to absence of required
   configurations in the kernel config file.Tests which failed as TCONF on
   raspberry pi runs successfully on x86 machine because required
   configurations are enabled in the config file.

           for example: fanotify test was failed due to
CONFIG_FANOTIFY_ACCESS_PERMISSIONS
not configured in the kernel but same test passed on the x86 machine
           because  * CONFIG_FANOTIFY_ACCESS_PERMISSIONS=y  *enabled in the
x86 config file.
            So can we add all those required configs to the raspberry pi
config file?


I have attached a test error report and also attached result output
documents(results.xlsx,run.json,consolelog.txt) generated during test
execution.
Let me know your thoughts on this.

Thanks and Regards
Pavan Arun Deshpande



On Thu, Jun 3, 2021 at 5:31 PM Balaji Kalidas <[email protected]>
wrote:

> Hi Tim,
>
>       We ran the latest ltp version(20210524) Functional LTP and POSIX
> tests on a raspberry pi board and we have prepared the test error reports
> for both tests based on the output we got .
>
> I have attached both(LTP and POSIX) test error reports and also attached
> result output  documents generated during test execution.
>
> Let me know your thoughts on the same.
>
> Thanks and regards
> BALAJI.K
>
>
> On Thu, Jun 3, 2021 at 5:22 AM <[email protected]> wrote:
>
>> OK - I did some more analysis and testing today.  I found a few different
>> bugs in the Functional.LTP test.  It works OK on some other boards in
>> my lab, but on my raspberry pi it had problems.  Specifically msgstress04
>> is taking quite a long time (but it does eventually complete).
>> But the overall test hangs before completing.
>>
>> I updated Functional.LTP to the latest version (20210524).  This has
>> been updated in the fuego-core master git repository. You should
>> be able to do a git pull of the new test. Can you please
>> try this test again, and let me know what results you get?
>>
>> Thanks,
>>  -- Tim
>>
>>
>> > -----Original Message-----
>> > From: Pavan Arun Deshpande <[email protected]>
>> >
>> > Hi Tim,
>> >
>> > fuego has LTP test version - 20180118.
>> > but the latest LTP repo has version - 20210524.
>> >
>> >
>> >
>> > We ran the LTP and POSIX tests on a raspberry pi board and we have
>> prepared the test error reports for both tests based on the output we
>> > got . Both the tests have the common errors(test failures).
>> >
>> >
>> > I have attached both(LTP and POSIX) test error reports and also
>> attached result output  documents generated during test execution.
>> >
>> > Let me know your thoughts on the same.
>> >
>> >
>> > Thanks and regards
>> > Pavan Arun Deshpande
>> >
>> >
>> >
>> > This message contains confidential information and is intended only for
>> the individual(s) named. If you are not the intended recipient, you
>> > are notified that disclosing, copying, distributing or taking any
>> action in reliance on the contents of this mail and attached file/s is
>> strictly
>> > prohibited. Please notify the sender immediately and delete this e-mail
>> from your system. E-mail transmission cannot be guaranteed to be
>> > secured or error-free as information could be intercepted, corrupted,
>> lost, destroyed, arrive late or incomplete, or contain viruses. The
>> > sender therefore does not accept liability for any errors or omissions
>> in the contents of this message, which arise as a result of e-mail
>> > transmission.
>>
>>

-- 






This
message contains confidential information and is intended only 
for the
individual(s) named. If you are not the intended
recipient, you are 
notified that disclosing, copying, distributing or taking any
action in 
reliance on the contents of this mail and attached file/s is strictly
prohibited. Please notify the
sender immediately and delete this e-mail 
from your system. E-mail transmission
cannot be guaranteed to be secured or 
error-free as information could be
intercepted, corrupted, lost, destroyed, 
arrive late or incomplete, or contain
viruses. The sender therefore does 
not accept liability for any errors or
omissions in the contents of this 
message, which arise as a result of e-mail
transmission.