[Insight-developers] HDF5 Testing Failures -- a solution! (?)

[Williams, Norman K]

I think I know what's going on and have pushed a patch:


The machines failing are testing concurrently, and the two HDF ImageIO
tests are using the same filenames, so if the two tests run at the same
time, they can step on each other's files!

In the history of times I've felt stupid, this is definitely top 5 for the
year.

I have pushed a patch: http://review.source.kitware.com/#change,1843

On 6/8/11 6:37 PM, "Bill Lorensen" <bill.lorensen at gmail.com> wrote:

>One or two days of passing tests on a platform is not enough. Prior to
>the upgrade of hdf5, the two hdf5 tests failed intermittently on some
>machines. After a few days, we can look back and see if this is still
>happening.
>
>Bikll
>
>On Wed, Jun 8, 2011 at 9:44 AM, Williams, Norman K
><norman-k-williams at uiowa.edu> wrote:
>> There are a lot of builds that fail, and they all (save one) have
>> something in common.  The test writes a file, but then cannot read it --
>> either it fails to open or it fails to read the first dataset.
>>
>>
>> I verified that the tests do in fact close the file they've created.
>>
>> I also notice that for many systems that fail, very similar systems
>> succeed.
>>
>> I can add a test that attempts to read a known-good image, and see if
>>that
>> fails as well.
>>
>> I've been loading up VMs in virtual boxes that are, where possible1 as
>> close as possible to the failing systems.  So far no failures.
>>
>> As I've said before, if someone can give me an account on any of the
>> machines with failures I'll gladly investigate.
>>
>> On 6/8/11 6:47 AM, "Brad King" <brad.king at kitware.com> wrote:
>>
>>>On 06/07/2011 10:51 AM, Brad King wrote:
>>>> On 06/04/2011 12:02 PM, Bill Lorensen wrote:
>>>>> Looks like an uninitialized variable somewhere? valgrind does not
>>>>> catch them all... Maybe you should run cppcheck on the HDF5
>>>>>thirdparty
>>>>> code.
>>>>
>>>> At Kent's request I've updated the HDF5 snapshot to version 1.8.7 from
>>>> upstream.  I manually built and tested it on Linux with GCC and
>>>>Windows
>>>> with MinGW and VS 9 tools.  We should all keep an eye out for new
>>>> warnings.
>>>>
>>>> The commit range of the changes is "e1f9e848..b76ce0bd".
>>>
>>>Well, there are quite a few places that the HDF5 tests now fail:
>>>
>>>http://www.cdash.org/CDash/testSummary.php?project=2&name=itkHDF5ImageIO
>>>Te
>>>st&date=2011-06-07
>>>http://www.cdash.org/CDash/testSummary.php?project=2&name=itkHDF5ImageIO
>>>St
>>>reamingReadWriteTest&date=2011-06-07
>>>
>>>However, they pass on all the Kitware machines and on all my own builds
>>>(except itkHDF5ImageIOTest on factory.kitware fails for an unrelated
>>> reason).
>>>
>>>Can anyone with a machine where it fails investigate, please?
>>>
>>>Thanks,
>>>-Brad
>>
>>
>>
>> ________________________________
>> Notice: This UI Health Care e-mail (including attachments) is covered
>>by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is
>>confidential and may be legally privileged.  If you are not the intended
>>recipient, you are hereby notified that any retention, dissemination,
>>distribution, or copying of this communication is strictly prohibited.
>>Please reply to the sender that you have received the message in error,
>>then delete it.  Thank you.
>> ________________________________
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Kitware offers ITK Training Courses, for more information visit:
>> http://kitware.com/products/protraining.html
>>
>> Please keep messages on-topic and check the ITK FAQ at:
>> http://www.itk.org/Wiki/ITK_FAQ
>>
>> Follow this link to subscribe/unsubscribe:
>> http://www.itk.org/mailman/listinfo/insight-developers
>>



________________________________
Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and may be legally privileged.  If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited.  Please reply to the sender that you have received the message in error, then delete it.  Thank you.
________________________________