Strong APA scheduler testing

[Richi Dubey]

Hi,

Sorry for the delay. My university tests were going on.

So, I reran the test only for smptestsuites, and I have attached the log.

The test says that smpfatal09 gives timeout, where when I ran the test with
qemu, I get the following output:

-----------------------------------------------------------------------------------
~/quick-start/rtems/5/bin$ ./qemu-system-arm -net none -nographic -M
realview-pbx-a9 -m 256M -kernel
~/quick-start/build/b3-realview/arm-rtems5/c/realview_pbx_a9_qemu/testsuites/smptests/smpfatal09.exe
-smp 4

*** BEGIN OF TEST SMPFATAL 9 ***
*** TEST VERSION: 6.0.0.cba933cb2260afc79c2a94d7c26bce1b58a7dbfd-modified
*** TEST STATE: EXPECTED_PASS
*** TEST BUILD: RTEMS_NETWORKING RTEMS_POSIX_API RTEMS_SMP
*** TEST TOOLS: 7.5.0 20191114 (RTEMS 5, RSB 5 (0b7e87143b76), Newlib
fbaa096)

*** END OF TEST SMPFATAL 9 ***


*** FATAL ***
fatal source: 0 (INTERNAL_ERROR_CORE)
fatal code: 40 (INTERNAL_ERROR_NO_MEMORY_FOR_PER_CPU_DATA)
RTEMS version: 6.0.0.cba933cb2260afc79c2a94d7c26bce1b58a7dbfd-modified
RTEMS tools: 7.5.0 20191114 (RTEMS 5, RSB 5 (0b7e87143b76), Newlib fbaa096)
executing thread is NULL


*** BEGIN OF TEST SMPFATAL 9 ***
*** TEST VERSION: 6.0.0.cba933cb2260afc79c2a94d7c26bce1b58a7dbfd-modified
*** TEST STATE: EXPECTED_PASS
*** TEST BUILD: RTEMS_NETWORKING RTEMS_POSIX_API RTEMS_SMP
*** TEST TOOLS: 7.5.0 20191114 (RTEMS 5, RSB 5 (0b7e87143b76), Newlib
fbaa096)

*** END OF TEST SMPFATAL 9 ***


*** FATAL ***

and so on ...

-----------------------------------------------

Also, I ran the qemu with gdb and I get the same result. Why does
rtems-test feel it is timeout? Is it because of the 200 s limit?

Please let me know.



On Sat, Sep 12, 2020 at 7:47 PM Richi Dubey <richidubey at gmail.com> wrote:

> Understood. I'm on it. I'll try to debug the scheduler related tests first
> i.e SMP tests if there are errors in them.
>
> On Fri, Sep 11, 2020 at 3:30 AM Gedare Bloom <gedare at rtems.org> wrote:
>
>> Start at the end and work your way back.
>>
>> The clean version reports:
>> Passed:        636
>> Failed:          1
>> User Input:      6
>> Expected Fail:   1
>> Indeterminate:   0
>> Benchmark:       3
>> Timeout:         3
>> Invalid:         5
>> Wrong Version:   1
>> Wrong Build:     0
>> Wrong Tools:     0
>> ------------------
>> Total:         656
>>
>>
>> Your version reports:
>> Passed:        600
>> Failed:         22
>> User Input:      6
>> Expected Fail:   1
>> Indeterminate:   0
>> Benchmark:       3
>> Timeout:        16
>> Invalid:         6
>> Wrong Version:   0
>> Wrong Build:     0
>> Wrong Tools:     0
>> ------------------
>> Total:         654
>>
>> You'll want to poke at those failures first and triage them. Fixing
>> one may cascade to other tests, so rerun the testsuite after you try a
>> fix.
>>
>> On Thu, Sep 10, 2020 at 12:59 PM Richi Dubey <richidubey at gmail.com>
>> wrote:
>> >
>> > Hi,
>> >
>> > Please find attached the log of rtems-test with the "clean" version
>> (Commit: 61ccb9c05d (HEAD, tag: 5.1, origin/5) bsp/xilinx-zynq: Flush
>> TX-Buffer before initializing uar) vs my Strong APA changes (with name
>> log_leon3_sis_strong_apa).
>> >
>> > I haven't looked at the log in detail yet, but please let me know if
>> there's anything odd that sparks interest.
>> >
>> > Thanks,
>> > Richi.
>> > _______________________________________________
>> > devel mailing list
>> > devel at rtems.org
>> > http://lists.rtems.org/mailman/listinfo/devel
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20200916/eb0da048/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: log_leon3_sis_strong_apa_new
Type: application/octet-stream
Size: 17169 bytes
Desc: not available
URL: <http://lists.rtems.org/pipermail/devel/attachments/20200916/eb0da048/attachment-0001.obj>