From 67f72c42771afcbe72950b8abe6090ddc65591fd Mon Sep 17 00:00:00 2001 From: Quincey Koziol Date: Wed, 20 Nov 2002 09:49:11 -0500 Subject: [svn-r6120] Purpose: Update information Description: Add more information about tests performed and why they succeed/fail. --- doc/html/TechNotes/TestReview/H5Dget_offset.html | 85 ++++++++++++++++++++++-- 1 file changed, 80 insertions(+), 5 deletions(-) diff --git a/doc/html/TechNotes/TestReview/H5Dget_offset.html b/doc/html/TechNotes/TestReview/H5Dget_offset.html index 6c53a3d..afc445a 100644 --- a/doc/html/TechNotes/TestReview/H5Dget_offset.html +++ b/doc/html/TechNotes/TestReview/H5Dget_offset.html @@ -25,7 +25,10 @@ OL.upperroman { list-style-type: upper-roman } Test case -Test file +Test source file + + +Test method Expected test results @@ -41,9 +44,27 @@ OL.upperroman { list-style-type: upper-roman } dsets.c + +
    +
  1. Create chunked dataset +
  2. Query dataset offset +
+ + FAIL + +

Because dataset is stored in chunks that are indexed by a B-tree, there is +no single piece of data to query the offset of. +

+

It may be possible in the future to +enhance this function by querying the offset of a particular chunk (or chunks), +but that has limited use because chunks could be compressed, etc. with an I/O +filter. +

+ + @@ -53,9 +74,28 @@ OL.upperroman { list-style-type: upper-roman } dsets.c + +
    +
  1. Create chunked dataset +
  2. Query dataset offset +
+ + FAIL + +

Because dataset is stored in the object header of the dataset, there is +no separate piece of data to query the offset of. +

+

It may be possible in the future to get the offset of the data in the object +header, but this is problematic due to the fact that the messages in the object +header can get relocated in the file when changes (like adding attributes, etc.) +are made to the dataset, invalidating the address given to the user. +filter. +

+ + @@ -65,11 +105,21 @@ OL.upperroman { list-style-type: upper-roman } dsets.c -

Succeed in getting the proper address and be able to verify + +

    +
  1. Create file with 0 sized user-block (the default) +
  2. Create contigous dataset +
  3. Query dataset offset +
+ + + +

Succeed in getting the proper address and be able to verify that the data at that address in the file is what was written out.

When data storage allocation is "late" (the default), querying the offset -should fail.

+should fail if performed before data is written to the dataset. +

Needs additional test to verify that the data written out is located at the @@ -85,11 +135,21 @@ correct offset in the file. dsets.c -

Succeed in getting the proper address and be able to verify + +

    +
  1. Create file with non-0 sized user-block +
  2. Create contigous dataset +
  3. Query dataset offset +
+ + + +

Succeed in getting the proper address and be able to verify that the data at that address in the file is what was written out.

When data storage allocation is "late" (the default), querying the offset -should fail.

+should fail if performed before data is written to the dataset. +

Needs test for this case. @@ -104,12 +164,27 @@ should fail.

external.c + +
    +
  1. Create contigous dataset with external storage +
  2. Query dataset offset +
+ + FAIL + +

In theory, it's easy to return the offset of the data in the external file, +but this wasn't done because it would be too easy for users to assume that the +offset returned was in the HDF5 file instead of the external file. +

+ + +
  • Parallel Review:

    The H5Dget_offset() function is not tested in parallel. Currently, there -- cgit v0.12