Changeset 361fda6 in rtems-testing


Ignore:
Timestamp:
Jul 23, 2009, 1:59:13 PM (10 years ago)
Author:
Joel Sherrill <joel.sherrill@…>
Branches:
4.11, 8895273c193787f84c4585a10f6d6aceb3b25dc4
Children:
23e1f18
Parents:
fa6ae97
Message:

2009-07-23 Joel Sherrill <joel.sherrill@…>

  • Explanations.txt: Remove cancellation cases and cleanup killinfo.c explations.
Location:
rtems-coverage
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • rtems-coverage/ChangeLog

    rfa6ae97 r361fda6  
     12009-07-23      Joel Sherrill <joel.sherrill@OARcorp.com>
     2
     3        * Explanations.txt: Remove cancellation cases and cleanup killinfo.c
     4        explations.
     5
    162009-07-21      Joel Sherrill <joel.sherrill@OARcorp.com>
    27
  • rtems-coverage/Explanations.txt

    rfa6ae97 r361fda6  
    1 
    2 cancelrun.c:44
    3 Simple Test Case
    4 This is simply an untested normal use of pthread cancellation handlers.
    5 +++
    6 
    7 setcancelstate.c:50
    8 Simple Test Case
    9 A very simple test case where a NULL pointer to the oldstate is passed in.
    10 +++
    11 
    12 setcancelstate.c:65
    13 Simple Test Case
    14 The other is a branch from line 50 for !oldstate.
    15 +++
    16 
    17 setcanceltype.c:50
    18 Simple Test Case
    19 This is a case of passing in a bad cancelation type.
    20 +++
    21 
    22 setcanceltype.c:64
    23 Simple Test Case
    24 The other is a branch from line 50 for bad type.
    25 +++
    261
    272keycreate.c:80
     
    3510+++
    3611
    37 keyrundestructors.c:62
    38 Simple Test Case
    39 Restructure the code into 3 separate tests with continues and see which
    40 cases are really not hit. Then trigger the cases.
    41 +++
    42 
    4312keyrundestructors.c:64
    4413Simple Test Case
    45 Probably Iterating over a NULL value.
     14This is where a key is configured without a destructor.
     15+++
     16
     17keyrundestructors.c:68
     18Simple Test Case
     19This is where a key is configured and created that this thread is not using.
    4620+++
    4721
     
    9973pthread.c:97
    10074Simple Test Case
    101 This is a case of the sporadic scheduling replinish period being less
     75This is a case of the sporadic scheduling replenish period being less
    10276than one clock tick in length.
    10377+++
     
    218192+++
    219193
    220 iterateoverthreads.c:42
     194iterateoverthreads.c:43
    221195Simple Test Case
    222196Need to call iterate over threads in a test where there is an API configured
    223 which does not have threads.  Should be easy to add to sp54.
     197which does not have threads.  We may be able to add this to sp54.
    224198+++
    225199
     
    260234threadqprocesstimeout.c:46
    261235Interrupt Synchronization
    262 This is processing a timeout on a thread (that is NOT the thread executing)
    263 that times out while another thread is in the process of blocking on
    264 a thread queue.
     236This is a case there we are timing out a thread on the same thread
     237queue that the currently executing thread is in the process of blocking on.
    265238+++
    266239
     
    287260+++
    288261
    289 killinfo.c:152
    290 Simple Test Case
    291 Yet another path through here.
    292 +++
    293 
    294 killinfo.c:212
    295 Simple Test Case
    296 Multiple threads interested but find high priority one first.
    297 +++
    298 
    299 killinfo.c:247
    300 Simple Test Case
    301 Yet another path through here.
    302 +++
    303 
    304 killinfo.c:339
     262killinfo.c:145
     263Simple Test Case
     264Probably a loop termination since the last line is 130.  I suspect
     265this may involve have to iterate the list with multiple entries on it.
     266Even worse, this appears to be ignoring the two to N chain.  We may
     267want to consider revisiting the POSIX specificiation to see if a
     268FIFO is acceptable.  Otherwise, this code is going to have to
     269get more complicated.  Maybe the logic in the loop needs to move
     270to a subroutine.
     271+++
     272
     273killinfo.c:203
     274Simple Test Case
     275A higher priority thread is interested so we need to take the branch
     276to continue.  This is only a single instruction.
     277+++
     278
     279killinfo.c:234
     280Simple Test Case
     281Multiple threads interested but find high priority one first.  This is
     282a long section with multiple cases.  It will take multiple tests to do
     283this.
     284+++
     285
     286killinfo.c:328
    305287Simple Test Case
    306288This is an error case where we can't allocate another signinfo structure.
Note: See TracChangeset for help on using the changeset viewer.