test failures on sis

[Joel Sherrill]

On 12/16/2013 1:58 AM, Sebastian Huber wrote:
> On 2013-12-14 19:32, Joel Sherrill wrote:
>> Hi
>>
>> The failures on sis on the head indicate a few that need
>> some attention.
>>
>> WARNING - heapwalk did not appear to complete execution
>>
>>          create a loop in the free list
>> ../../../../../../../rtems/c/src/../../testsuites/libtests/heapwalk/init.c:
>> 55 retval == expectet_retval
> 
> In case RTEMS_DEBUG is enabled, then this is ok.

OK. I did have debug enabled. Maybe a message before that to
indicate an assert is expected and a forced failure in the
test below that point if debug is enabled?

>> WARNING - mrfs_fstime did not appear to complete execution
>>
>> Sleep a few seconds
>> ../../../../../../../rtems/c/src/../../testsuites/fstests/mrfs_fstime/../fstime/test.c:
>> 128 st.st_ctime == st.st_mtime
> 
> This is a TODO for the RFS.
> 
>>
>>
>> WARNING - sp2038 did not appear to complete execution
>>
>> I think this is expected.
> 
> Yes, this needs a 64-bit time_t.
> 
>>
>> WARNING - spintrcritical20 did not appear to complete execution
>>
>> *** TEST INTERRUPT CRITICAL SECTION 20 ***
>>
>> This looks like recent changes may have broken things or
>> the assertion is not really guaranteed all the time.
> 
> I think this is a problem with the test.  I see sporadic failures here.

I will put it on my every growing list to look at.

>> Support - rtems_timer_create - creating timer 1
>> ../../../../../../../rtems/c/src/../../testsuites/sptests/spintrcritical20/init.c:
>> 139 ctx->thread_queue_was_null
>>
>> WARNING - sppagesize did not appear to complete execution
>>
>> Known failure until tools adjusted.
>>
> 
> 



-- 
Joel Sherrill, Ph.D.             Director of Research & Development
joel.sherrill at OARcorp.com        On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
Support Available                (256) 722-9985