diff options
author | Joel Sherrill <joel.sherrill@OARcorp.com> | 2011-07-25 18:38:30 +0000 |
---|---|---|
committer | Joel Sherrill <joel.sherrill@OARcorp.com> | 2011-07-25 18:38:30 +0000 |
commit | 2cedd4b4f0c61d6238dd0bd6cb82c362ac367500 (patch) | |
tree | ed66348668b149b02ee0d073955c141869c0ae11 /rtems-coverage | |
parent | 5f060dca53d9ebcf17a017ce7489000e0f28edca (diff) |
2011-07-25 Joel Sherrill <joel.sherrilL@OARcorp.com>
* Explanations.txt: Minor updates.
* VERSIONS-COVERAGE: Testing 4.9.6.
* do_coverage: Default to saving tarballs.
Diffstat (limited to 'rtems-coverage')
-rw-r--r-- | rtems-coverage/ChangeLog | 6 | ||||
-rw-r--r-- | rtems-coverage/Explanations.txt | 169 | ||||
-rw-r--r-- | rtems-coverage/VERSIONS-COVERAGE | 2 | ||||
-rwxr-xr-x | rtems-coverage/do_coverage | 2 |
4 files changed, 30 insertions, 149 deletions
diff --git a/rtems-coverage/ChangeLog b/rtems-coverage/ChangeLog index 27ab63f..887486a 100644 --- a/rtems-coverage/ChangeLog +++ b/rtems-coverage/ChangeLog @@ -1,3 +1,9 @@ +2011-07-25 Joel Sherrill <joel.sherrilL@OARcorp.com> + + * Explanations.txt: Minor updates. + * VERSIONS-COVERAGE: Testing 4.9.6. + * do_coverage: Default to saving tarballs. + 2011-03-15 Joel Sherrill <joel.sherrilL@OARcorp.com> * VERSIONS-COVERAGE: Switch to CVS head. diff --git a/rtems-coverage/Explanations.txt b/rtems-coverage/Explanations.txt index c66f3f2..f988b51 100644 --- a/rtems-coverage/Explanations.txt +++ b/rtems-coverage/Explanations.txt @@ -1,160 +1,35 @@ -privateenv.c:43 -Unreachable -free_user_env is never called when (env == &rtems_global_user_env). -This check is done by the caller (rtems_libio_share_private_env) in a different manner as below: -"if (rtems_current_user_env->task_id==current_task_id) {" -This makes sure that free_user_env is not called venv == &rtems_global_user_env -+++ - -imfs_fifo.c:61 -Unreachable -This is an error return path which only returns an error when -pipe_release() returns an error but pipe_release() can't return -an error. Maybe pipe_release() should be changed to void. -+++ - -imfs_getchild.c:51 -Unreachable -This code cannot be reached. The routine IMFS_find_match_in_dir is -called only if the token type is IMFS_NAME. If ".." is present in the -path, the token type returned by IMFS_get_token would be -IMFS_DIR_UP. With such a setup, IMFS_find_match_in_dir cannot be -called with the name as ".." -+++ - -imfs_fsunmount.c:86 -Ask Chris Johns -I think he wrote this code and can probably identify the test case. -+++ - -imfs_fsunmount.c:93 -Ask Chris Johns -I think he wrote this code and can probably identify the test case. -+++ - -imfs_mount.c:44 -Unreachable? -We need to ask Chris Johns about this. I believe this is a -case where the error checking has been done by the system -call layer. I analyzed the "file handlers" callbacks for -guarantees on parameters. This indicates the same analysis -needs to happen for "file system handlers." -Bharath: Yes, it is checked in mount.c -+++ - -imfs_debug.c:54 -Simple Test Case -Need to do an IMFS_dump on an IMFS filesystem which has a very large -file in it. I think this is a simple addition to one of the existing -IMFS tests which creates a large file. -+++ - -imfs_debug.c:88 -Simple Test Case -We need to do an IMFS_dump on an IMFS filesystem which has a bad node type -in it. This may require peeking behind the curtain and changing a -value. -Bharath: But usually, this code is unreachable since we cannot create -a node which is not of type that is checked for. -+++ - -imfs_rename.c:40 -Discuss -I think this is either a simple test or unreachable code. We need -to discuss this to figure out which. -Bharath: I am not sure how to have a node's parent == NULL. -+++ - -imfs_unlink.c:51 -Discuss -I think this is either a simple test or unreachable code. We need -to discuss this to figure out which. -+++ - -imfs_unmount.c:45 -Discuss -I think this is either a simple test or unreachable code. We need -to discuss this to figure out which. -+++ - -imfs_unmount.c:52 -Discuss -I think this is either a simple test or unreachable code. We need -to discuss this to figure out which. -+++ - -newlibc_exit.c:89 -Simple Test Case -libc_wrapup() is never called when the system state is down. -+++ - -readv.c:106 -Simple Test Case -The count needs to be -1 in one of the requests. Also add a test for -0 value at the same time since it appears that is a missing branch -condition. -+++ - -getpwent.c:127 -Discuss -I think this is detecting whether or not the read can be fulfilled -from the buffer. But I am not sure. -+++ - -getpwent.c:112 +schedulerpriorityyield.c:47 Simple Test Case +Branch Never Taken +New test where there is more than one thread at a priority with the +executing thread being non-preemptive. Create a higher priority thread +and then yield. -This is actually the error case at line 103 (*nleft < 2). I think this -will be hit by having a password entry which does not have enough -characters left in the user's return buffer while something is -being copied into it. + init task at priority 2, non-preemptive + create task at priority 2 + create task at priority 1 + yield +++ -writev.c:104 +schedulerpriorityyield.c:51 Simple Test Case -This is a case of needing 0 values in the write iov entries. -+++ +Branch Always Taken +New test where only one thread at a priority (non-preemptive), create a +thread at higher priority, then yield. -writev.c:113 -Simple Test Case -This is a case of needing negative values in the write iov entries. + init task at priority 2, non-preemptive + create task at priority 1 + yield +++ -vprintk.c:125 +schedulerpriorityyield.c:52 Simple Test Case -0x6f is a 'o'. It looks like we do not have a printk test which uses %o. +Not Executed +Same test case as schedulerpriorityyield.c:51 +++ -imfs_load_tar.c:112 +coremsg.c:86 Simple Test Case -Need to make sure one of the tar tests is configured with the IMFS -and the other is configured with fifoIMFS. -+++ - -imfs_load_tar.c:151 -Simple Test Case -We apparently only have a relative symbolic link. We need to include -one which has an absolute path. This will be a broken symlink on the -host but resolve fine on the target. -+++ - -imfs_load_tar.c:169 -Medium Test Case -The eval for make must fail. We will have to ask Jennifer how to -make this call fail. -+++ - -rtems_mkdir.c:102 -Email Sebastian -Sebastian needs to write a test case for this. -+++ - -rtems_mkdir.c:110 -Email Sebastian -Sebastian needs to write a test case for this. -+++ - -rtems_mkdir.c:124 -Email Sebastian -Sebastian needs to write a test case for this. +We need to request enough messages of a certain size that the math +overflows to less than a single message. +++ diff --git a/rtems-coverage/VERSIONS-COVERAGE b/rtems-coverage/VERSIONS-COVERAGE index 2b4c590..02ac03b 100644 --- a/rtems-coverage/VERSIONS-COVERAGE +++ b/rtems-coverage/VERSIONS-COVERAGE @@ -1,7 +1,7 @@ # USE FULL PATHS!!! BASEDIR=${HOME}/test-gcc -RTEMS_VERSION=4.11 +RTEMS_VERSION=4.9.6 case ${RTEMS_VERSION} in 4.5) RTEMSDIR=${BASEDIR}/rtems-45 TARDIR=${BASEDIR}/tarballs/4.5 diff --git a/rtems-coverage/do_coverage b/rtems-coverage/do_coverage index 94873e3..61c9393 100755 --- a/rtems-coverage/do_coverage +++ b/rtems-coverage/do_coverage @@ -93,7 +93,7 @@ do_link_tests="yes" do_run_tests="no" do_reports="no" do_publish="no" -do_save_tarballs="no" +do_save_tarballs="yes" do_core="yes" do_developmental="yes" outputDir="" |