Changeset a42395a in rtems-testing


Ignore:
Timestamp:
Jul 7, 2009, 5:27:32 PM (10 years ago)
Author:
Joel Sherrill <joel.sherrill@…>
Branches:
4.11, 8895273c193787f84c4585a10f6d6aceb3b25dc4
Children:
c198584
Parents:
7e7a513
Message:

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

  • Explanations.txt: Restructured code to eliminate these cases.
Location:
rtems-coverage
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • rtems-coverage/ChangeLog

    r7e7a513 ra42395a  
     12009-07-07      Joel Sherrill <joel.sherrill@OARcorp.com>
     2
     3        * Explanations.txt: Restructured code to eliminate these cases.
     4
    152009-07-07      Joel Sherrill <joel.sherrill@OARcorp.com>
    26
  • rtems-coverage/Explanations.txt

    r7e7a513 ra42395a  
    132132+++
    133133
    134 mutexsetprioceiling.c:59
    135 Probably Simple Test Case
    136 This appears to be missing not passing in a bad id.
    137 +++
    138 
    139134mutextimedlock.c:59
    140135Simple Test Case (or Restructure)
     
    223218+++
    224219
     220coremutexsurrender.c:188
     221Simple Test Case
     222There must not be a test of a priority ceiling mutex getting released
     223which results in a thread being unblocked and the UNBLOCKED thread's
     224priority being elevated.
     225+++
     226
    225227corespinlockwait.c:69
    226228Simple Test Case
     
    233235Attempt to release a locked spinlock from a thread that is not the one
    234236which locked it.
    235 +++
    236 
    237 coremutexsurrender.c:88
    238 Simple Test Case or Code Restructuring
    239 This is a switch which has two cases marked as not able to be hit. This
    240 documentation needs to be verified and if true, restructured to represent
    241 this.  The cases that are not executed need to be turned into a
    242 conditionalized debug assertion.
    243 +++
    244 
    245 coremutexsurrender.c:178
    246 Simple Test Case
    247 I have trouble believing there is no simple priority ceiling mutex test
    248 which locks raises priority and then releases and lowers priority but this
    249 case sure looks like that.  Or it is a case where the thread's priority
    250 is equal to the ceiling and the branch is taken.  Hard to read SPARC assembly.
    251 I am leaning to the equal case.
    252237+++
    253238
Note: See TracChangeset for help on using the changeset viewer.