Changeset e686517 in rtems-testing


Ignore:
Timestamp:
Aug 2, 2010, 4:28:03 PM (9 years ago)
Author:
Joel Sherrill <joel.sherrill@…>
Branches:
4.11, 8895273c193787f84c4585a10f6d6aceb3b25dc4
Children:
5d8ffa7
Parents:
6b2e547
Message:

2010-08-02 Joel Sherrill <joel.sherrilL@…>

  • Explanations.txt: Update. Remove old ones and add a number of new entries.
Location:
rtems-coverage
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • rtems-coverage/ChangeLog

    r6b2e547 re686517  
     12010-08-02      Joel Sherrill <joel.sherrilL@OARcorp.com>
     2
     3        * Explanations.txt: Update. Remove old ones and add a number of new
     4        entries.
     5
    162010-07-14      Joel Sherrill <joel.sherrilL@OARcorp.com>
    27
  • rtems-coverage/Explanations.txt

    r6b2e547 re686517  
    1 bspcmdline_getparam.c:67
    2 Simple Test Case
    3 Need a test case to return NULL.
    4 +++
    5 
    6 bspcmdline_getparamrhs.c:36
    7 Simple Test Case
    8 Need a test case to return NULL.  This looks like a parameter of the form
    9 "LHS" with no "=" or "RHS".
    10 +++
    11 
    12 mknod.c:44
    13 Simple Test Case
    14 Call mknod with a mode of 0
    15 +++
    16 
    17 imfs_fifo.c:100
    18 Bharath Suri
    19 IMFS_fifo_ioctl should be hit when fifo tests are done if not
    20 check why.
    21 +++
    22 
    23 imfs_fifo.c:125
    24 Bharath Suri
    25 IMFS_fifo_lseek should be hit when fifo tests are done if not
    26 check why.
    27 +++
    28 
    29 imfs_fifo.c:69
    30 Bharath Suri
    31 IMFS_fifo_read should be hit when fifo tests are done if not
    32 check why.
    33 +++
    34 
    35 imfs_fifo.c:84
    36 Bharath Suri
    37 IMFS_fifo_write should be hit when fifo tests are done if not
    38 check why.
    39 +++
    40 
    41 fifo.c:553
    42 Bharath Suri
    43 pipe_ioctl should be hit when fifo tests are done if not check
    44 why.
    45 +++
    46 
    47 fifo.c:582
    48 Bharath Suri
    49 pipe_lseek should be hit when fifo tests are done if not check
    50 why.
    51 +++
    52 
    53 fifo.c:395
    54 Bharath Suri
    55 pipe_read should be hit when fifo tests are done if not check
    56 why.
    57 +++
    58 
    59 fifo.c:467
    60 Bharath Suri
    61 pipe_write should be hit when fifo tests are done if not check
    62 why.
    63 +++
    64 
    65 memfile.c:400
    66 Bharath Suri
    67 IMFS_memfile_remove_block should be hit when fifo tests are done
    68 if not check why.
    69 +++
    70 
    71 check.c:376
    72 Simple Test Case
    73 Stack_check_Dump_threads_usage should be hit in same test as new
    74 stack check test for report.
    75 +++
    76 
    77 check.c:356
    78 Simple Test Case
    79 Stack_check_find_high_water_mark should be hit in same test as
    80 new stack check test for report.
    81 +++
    82 
    83 check.c:470
    84 Simple Test Case
    85 rtems_stack_checker_report_usage_with_plugin should be hit in
    86 same test as new stack check test for report.
    87 +++
    88 
    89 privateenv.c:114
    90 Simple Test Case
    91 free_user_env and rtems_libio_share_private_env new test.
    92 +++
    93 
    94 privateenv.c:33
    95 Simple Test Case
    96 free_user_env and rtems_libio_share_private_env new test.
    97 +++
    98 
    99 check.c:215
    100 Simple Test Case
    101 Stack_check_report_blown_task Should be in stack check test check
    102 why not hit.
    103 +++
    104 
    105 assocnamebad.c:40
    106 Simple Test Case
    107 rtems_assoc_name_bad called from new; may want to add for
    108 associations.
    109 +++
    110 
    111 ioman.c:70
    112 Simple Test Case
    113 rtems_io_lookup_name added to existing io dev stub test ?sp19?
    114 +++
    115 
    116 error.c:201
    117 Simple Test Case
    118 rtems_panic, rtems_verror, rtems_error: New test for collection
    119 of rtems error reportin routines.
    120 +++
    121 
    122 error.c:109
    123 Simple Test Case
    124 rtems_panic, rtems_verror, rtems_error: New test for collection
    125 of rtems error reportin routines.
    126 +++
    127 
    128 error.c:182
    129 Simple Test Case
    130 rtems_panic, rtems_verror, rtems_error: New test for collection
    131 of rtems error reportin routines.
    132 +++
    133 
    134 getpwent.c:272
    135 Simple Test Case
    136 Simple
    137 +++
    138 
    139 getpwent.c:413
    140 Simple Test Case
    141 Simple
    142 +++
    143 
    144 getpwent.c:441
    145 Simple Test Case
    146 Simple
    147 +++
    148 
    149 fcntl.c:186
    150 Simple Test Case
    151 This is a function wrapper add a test case calling it where the
    152 wrapped function is called from
    153 +++
    154 
    155 getpid.c:43
    156 Simple Test Case
    157 This is a function wrapper add a test case calling it where the
    158 wrapped function is called from
    159 +++
    160 
    161 _gettod.c:84
    162 Simple Test Case
    163 This is a function wrapper add a test case calling it where the
    164 wrapped function is called from
    165 +++
    166 
    167 link.c:103
    168 Simple Test Case
    169 This is a function wrapper add a test case calling it where the
    170 wrapped function is called from
    171 +++
    172 
    173 _realloc_r.c:28
    174 Simple Test Case
    175 This is a function wrapper add a test case calling it where the
    176 wrapped function is called from
    177 +++
    178 
    179 stat.c:100
    180 Simple Test Case
    181 This is a function wrapper add a test case calling it where the
    182 wrapped function is called from
    183 +++
    184 
    185 unlink.c:115
    186 Simple Test Case
    187 This is a function wrapper add a test case calling it where the
    188 wrapped function is called from
    189 +++
    190 
    191 getpwent.c:406
    192 Simple Test Case
    193 This is a function wrapper add a test case calling it where the
    194 wrapped function is called from
    195 +++
    196 
    197 getpwent.c:263
    198 Simple Test Case
    199 This is a function wrapper add a test case calling it where the
    200 wrapped function is called from
    201 +++
    202 
    203 getpwent.c:254
    204 Simple Test Case
    205 This is a function wrapper add a test case calling it where the
    206 wrapped function is called from
    207 +++
    208 
    209 getpwent.c:247
    210 Simple Test Case
    211 This is a function wrapper add a test case calling it where the
    212 wrapped function is called from
    213 +++
    214 
    215 malloc_deferred.c:57
    216 Simple Test Case
    217 New test to Free memory from timer service routine. There is a
    218 send signal from TSR test that can be copied Consider adding test
    219 template for single operation from tsr. Talk to Joel before
    220 implementing.
    221 +++
    222 
     1privateenv.c:43
     2Simple Test Case
     3free_user_env is never called when (env == &rtems_global_user_env).  It is
     4possible that this path is impossible but that will require analysis of the
     5callers.  Since this is static, it is quite possible this is covered by
     6the callers.
     7+++
     8
     9imfs_chown.c:46
     10Simple Test Case
     11Not root and not owner.  Please try to cover all branch paths.
     12+++
     13
     14imfs_fchmod.c:42
     15Simple Test Case
     16Not root and not owner.  Please try to cover all branch paths.
     17+++
     18
     19imfs_fifo.c:61
     20Requires Discussion
     21This is an error return path which only returns an error when
     22pipe_release() returns an error but pipe_release() can't return
     23an error.  Maybe pipe_release() should be changed to void.
     24+++
     25
     26imfs_getchild.c:51
     27Simple Test Case
     28Appprently we never call this with ".." for the parent directory.
     29+++
     30
     31imfs_fsunmount.c:86
     32Ask Chris Johns
     33I think he wrote this code and can probably identify the test case.
     34+++
     35
     36imfs_fsunmount.c:93
     37Ask Chris Johns
     38I think he wrote this code and can probably identify the test case.
     39+++
     40
     41imfs_initsupp.c:55
     42Requires Discussion
     43I think this is an error case that cannot be reached.  The
     44bytes_per_block is set by confdefs.h and there are error checks
     45in that to prevent a bad value.
     46+++
     47
     48imfs_mount.c:44
     49Unreachable?
     50We need to ask Chris Johns about this. I believe this is a
     51case where the error checking has been done by the system
     52call layer.  I analyzed the "file handlers" callbacks for
     53guarantees on parameters.  This indicates the same analysis
     54needs to happen for "file system handlers."
     55+++
     56
     57imfs_debug.c:43
     58Simple Test Case
     59Need to do an IMFS_dump after loading a tarfile from memory.
     60I think this is a simple addition to tar01.
     61+++
     62
     63imfs_debug.c:54
     64Simple Test Case
     65Need to do an IMFS_dump on an IMFS filesystem which has a very large
     66file in it.  I think this is a simple addition to one of the existing
     67IMFS tests which creates a large file.
     68+++
     69
     70imfs_debug.c:88
     71Simple Test Case
     72We need to do an IMFS_dump on an IMFS filesystem which has a bad node type
     73in it.  This may require peeking behind the curtain and changing a value.
     74+++
     75
     76imfs_rename.c:40
     77Discuss
     78I think this is either a simple test or unreachable code.  We need
     79to discuss this to figure out which.
     80+++
     81
     82imfs_unlink.c:51
     83Discuss
     84I think this is either a simple test or unreachable code.  We need
     85to discuss this to figure out which.
     86+++
     87
     88imfs_unmount.c:45
     89Discuss
     90I think this is either a simple test or unreachable code.  We need
     91to discuss this to figure out which.
     92+++
     93
     94imfs_unmount.c:52
     95Discuss
     96I think this is either a simple test or unreachable code.  We need
     97to discuss this to figure out which.
     98+++
     99
     100dup2.c:51
     101Simple Test Case
     102This looks like we never get to the bottom to actually call fcntl()
     103which I take to mean that we do not have a test for a working call
     104to dup2().
     105
     106But we need to be careful because fcntl(F_DUPFD) which is called has
     107slightly different semantics.  I suspect that fcntl(F_DUPFD) is wrong.
     108See fcntl.c:55 for more details.
     109+++
     110
     111fcntl.c:55
     112Discuss
     113I question that this is correct.  We are calling this from dup2()
     114and the semantics are slightly different.  fcntl is
     115I suspect that by adding a shared routine and calling it from fcntl()
     116and and dup2() we can fix this.
     117+++
     118
     119fcntl.c:83
     120Simple Test Case
     121We need a test setting close on exec.
     122+++
     123
     124fcntl.c:143
     125Simple Test Case
     126None of the file system specific handlers have ever returned an error here.
     127+++
     128
     129newlibc_exit.c:89
     130Simple Test Case
     131libc_wrapup() is never called when the system state is down.
     132+++
     133
     134readv.c:106
     135Simple Test Case
     136The count needs to be -1 in one of the requests.  Also add a test for
     1370 value at the same time since it appears that is a missing branch
     138condition.
     139+++
     140
     141getpwent.c:127
     142Discuss
     143I think this is detecting whether or not the read can be fulfilled
     144from the buffer.  But I am not sure.
     145+++
     146
     147getpwent.c:141
     148Simple Test Case
     149I think this is a matter of putting in a VERY large number in
     150a numeric field.  This is detecting overflow.  I think a long
     151string of 9's will do most of this.
     152+++
     153
     154getpwent.c:142
     155Simple Test Case
     156
     157See getpwent.c:141
     158+++
     159
     160getpwent.c:112
     161Simple Test Case
     162
     163This is actually the error case at line 103 (*nleft < 2).  I think this
     164will be hit by having a password entry which does not have enough
     165characters left in the user's return buffer while something is
     166being copied into it.
     167+++
     168
     169writev.c:104
     170Simple Test Case
     171This is a case of needing 0 values in the write iov entries.
     172+++
     173
     174writev.c:113
     175Simple Test Case
     176This is a case of needing negative values in the write iov entries.
     177+++
     178
     179vprintk.c:125
     180Simple Test Case
     1810x6f is a 'o'.  It looks like we do not have a printk test which uses %o.
     182+++
     183
     184imfs_load_tar.c:112
     185Simple Test Case
     186Need to make sure one of the tar tests is configured with the IMFS
     187and the other is configured with fifoIMFS.
     188+++
     189
     190imfs_load_tar.c:151
     191Simple Test Case
     192We apparently only have a relative symbolic link.  We need to include
     193one which has an absolute path. This will be a broken symlink on the
     194host but resolve fine on the target.
     195+++
     196
     197imfs_load_tar.c:169
     198Medium Test Case
     199The eval for make must fail.  We will have to ask Jennifer how to
     200make this call fail.
     201+++
     202
     203rtems_mkdir.c:102
     204Email Sebastian
     205Sebastian needs to write a test case for this.
     206+++
     207
     208rtems_mkdir.c:110
     209Email Sebastian
     210Sebastian needs to write a test case for this.
     211+++
     212
     213rtems_mkdir.c:124
     214Email Sebastian
     215Sebastian needs to write a test case for this.
     216+++
Note: See TracChangeset for help on using the changeset viewer.