Changeset 2cedd4b in rtems-testing


Ignore:
Timestamp:
Jul 25, 2011, 6:38:30 PM (8 years ago)
Author:
Joel Sherrill <joel.sherrill@…>
Branches:
4.11, 8895273c193787f84c4585a10f6d6aceb3b25dc4
Children:
8c4e654
Parents:
5f060dc
Message:

2011-07-25 Joel Sherrill <joel.sherrilL@…>

  • Explanations.txt: Minor updates.
  • VERSIONS-COVERAGE: Testing 4.9.6.
  • do_coverage: Default to saving tarballs.
Location:
rtems-coverage
Files:
4 edited

Legend:

Unmodified
Added
Removed
  • rtems-coverage/ChangeLog

    r5f060dc r2cedd4b  
     12011-07-25      Joel Sherrill <joel.sherrilL@OARcorp.com>
     2
     3        * Explanations.txt: Minor updates.
     4        * VERSIONS-COVERAGE: Testing 4.9.6.
     5        * do_coverage: Default to saving tarballs.
     6
    172011-03-15      Joel Sherrill <joel.sherrilL@OARcorp.com>
    28
  • rtems-coverage/Explanations.txt

    r5f060dc r2cedd4b  
    1 privateenv.c:43
    2 Unreachable
    3 free_user_env is never called when (env == &rtems_global_user_env).
    4 This check is done by the caller (rtems_libio_share_private_env) in a different manner as below:
    5 "if (rtems_current_user_env->task_id==current_task_id) {"
    6 This makes sure that free_user_env is not called venv == &rtems_global_user_env
     1schedulerpriorityyield.c:47
     2Simple Test Case
     3Branch Never Taken
     4New test where there is more than one thread at a priority with the
     5executing thread being non-preemptive.  Create a higher priority thread
     6and then yield.
     7
     8   init task at priority 2, non-preemptive
     9   create task at priority 2
     10   create task at priority 1
     11   yield
    712+++
    813
    9 imfs_fifo.c:61
    10 Unreachable
    11 This is an error return path which only returns an error when
    12 pipe_release() returns an error but pipe_release() can't return
    13 an error.  Maybe pipe_release() should be changed to void.
     14schedulerpriorityyield.c:51
     15Simple Test Case
     16Branch Always Taken
     17New test where only one thread at a priority (non-preemptive), create a
     18thread at higher priority, then yield.
     19
     20   init task at priority 2, non-preemptive
     21   create task at priority 1
     22   yield
    1423+++
    1524
    16 imfs_getchild.c:51
    17 Unreachable
    18 This code cannot be reached. The routine IMFS_find_match_in_dir is
    19 called only if the token type is IMFS_NAME. If ".." is present in the
    20 path, the token type returned by IMFS_get_token would be
    21 IMFS_DIR_UP. With such a setup, IMFS_find_match_in_dir cannot be
    22 called with the name as ".."
     25schedulerpriorityyield.c:52
     26Simple Test Case
     27Not Executed
     28Same test case as schedulerpriorityyield.c:51
    2329+++
    2430
    25 imfs_fsunmount.c:86
    26 Ask Chris Johns
    27 I think he wrote this code and can probably identify the test case.
     31coremsg.c:86
     32Simple Test Case
     33We need to request enough messages of a certain size that the math
     34overflows to less than a single message.
    2835+++
    29 
    30 imfs_fsunmount.c:93
    31 Ask Chris Johns
    32 I think he wrote this code and can probably identify the test case.
    33 +++
    34 
    35 imfs_mount.c:44
    36 Unreachable?
    37 We need to ask Chris Johns about this. I believe this is a
    38 case where the error checking has been done by the system
    39 call layer.  I analyzed the "file handlers" callbacks for
    40 guarantees on parameters.  This indicates the same analysis
    41 needs to happen for "file system handlers."
    42 Bharath: Yes, it is checked in mount.c
    43 +++
    44 
    45 imfs_debug.c:54
    46 Simple Test Case
    47 Need to do an IMFS_dump on an IMFS filesystem which has a very large
    48 file in it.  I think this is a simple addition to one of the existing
    49 IMFS tests which creates a large file.
    50 +++
    51 
    52 imfs_debug.c:88
    53 Simple Test Case
    54 We need to do an IMFS_dump on an IMFS filesystem which has a bad node type
    55 in it.  This may require peeking behind the curtain and changing a
    56 value.
    57 Bharath: But usually, this code is unreachable since we cannot create
    58 a node which is not of type that is checked for.
    59 +++
    60 
    61 imfs_rename.c:40
    62 Discuss
    63 I think this is either a simple test or unreachable code.  We need
    64 to discuss this to figure out which.
    65 Bharath: I am not sure how to have a node's parent == NULL.
    66 +++
    67 
    68 imfs_unlink.c:51
    69 Discuss
    70 I think this is either a simple test or unreachable code.  We need
    71 to discuss this to figure out which.
    72 +++
    73 
    74 imfs_unmount.c:45
    75 Discuss
    76 I think this is either a simple test or unreachable code.  We need
    77 to discuss this to figure out which.
    78 +++
    79 
    80 imfs_unmount.c:52
    81 Discuss
    82 I think this is either a simple test or unreachable code.  We need
    83 to discuss this to figure out which.
    84 +++
    85 
    86 newlibc_exit.c:89
    87 Simple Test Case
    88 libc_wrapup() is never called when the system state is down.
    89 +++
    90 
    91 readv.c:106
    92 Simple Test Case
    93 The count needs to be -1 in one of the requests.  Also add a test for
    94 0 value at the same time since it appears that is a missing branch
    95 condition.
    96 +++
    97 
    98 getpwent.c:127
    99 Discuss
    100 I think this is detecting whether or not the read can be fulfilled
    101 from the buffer.  But I am not sure.
    102 +++
    103 
    104 getpwent.c:112
    105 Simple Test Case
    106 
    107 This is actually the error case at line 103 (*nleft < 2).  I think this
    108 will be hit by having a password entry which does not have enough
    109 characters left in the user's return buffer while something is
    110 being copied into it.
    111 +++
    112 
    113 writev.c:104
    114 Simple Test Case
    115 This is a case of needing 0 values in the write iov entries.
    116 +++
    117 
    118 writev.c:113
    119 Simple Test Case
    120 This is a case of needing negative values in the write iov entries.
    121 +++
    122 
    123 vprintk.c:125
    124 Simple Test Case
    125 0x6f is a 'o'.  It looks like we do not have a printk test which uses %o.
    126 +++
    127 
    128 imfs_load_tar.c:112
    129 Simple Test Case
    130 Need to make sure one of the tar tests is configured with the IMFS
    131 and the other is configured with fifoIMFS.
    132 +++
    133 
    134 imfs_load_tar.c:151
    135 Simple Test Case
    136 We apparently only have a relative symbolic link.  We need to include
    137 one which has an absolute path. This will be a broken symlink on the
    138 host but resolve fine on the target.
    139 +++
    140 
    141 imfs_load_tar.c:169
    142 Medium Test Case
    143 The eval for make must fail.  We will have to ask Jennifer how to
    144 make this call fail.
    145 +++
    146 
    147 rtems_mkdir.c:102
    148 Email Sebastian
    149 Sebastian needs to write a test case for this.
    150 +++
    151 
    152 rtems_mkdir.c:110
    153 Email Sebastian
    154 Sebastian needs to write a test case for this.
    155 +++
    156 
    157 rtems_mkdir.c:124
    158 Email Sebastian
    159 Sebastian needs to write a test case for this.
    160 +++
  • rtems-coverage/VERSIONS-COVERAGE

    r5f060dc r2cedd4b  
    22BASEDIR=${HOME}/test-gcc
    33
    4 RTEMS_VERSION=4.11
     4RTEMS_VERSION=4.9.6
    55case ${RTEMS_VERSION} in
    66  4.5)  RTEMSDIR=${BASEDIR}/rtems-45
  • rtems-coverage/do_coverage

    r5f060dc r2cedd4b  
    9494do_reports="no"
    9595do_publish="no"
    96 do_save_tarballs="no"
     96do_save_tarballs="yes"
    9797do_core="yes"
    9898do_developmental="yes"
Note: See TracChangeset for help on using the changeset viewer.