# Cdash build test failing for Windows without error log

**URL:** <https://discourse.slicer.org/t/cdash-build-test-failing-for-windows-without-error-log/2378>\
**Category:** Development\
**Created:** [March 20, 2018, 2:23pm UTC](https://discourse.slicer.org/t/cdash-build-test-failing-for-windows-without-error-log/2378 "2018-03-20T14:23:28Z")\
**Posts on this page:** 17\
**Page:** 1

<div class="post-metadata">

**Author:** ![chribaue](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/chribaue/32/1373_2.png) [@chribaue](https://discourse.slicer.org/u/chribaue)\
**Post date:** [March 20, 2018, 2:23pm UTC](https://discourse.slicer.org/t/cdash-build-test-failing-for-windows-without-error-log/2378/1 "2018-03-20T14:23:28Z")

</div>

Hi,

one of the self tests I wrote for one of my extensions keeps failing on Cdash for the Windows build without giving me a reasonable error log:

[http://slicer.cdash.org/testDetails.php?test=8729220&build=1223692](http://slicer.cdash.org/testDetails.php?test=8729220&build=1223692)  
The test output is “vtkDebugLeaks has found no leaks.” and the test status is “Failed”

The same test passes on Mac and on my Linux machine.  
[http://slicer.cdash.org/testDetails.php?test=8742239&build=1223531](http://slicer.cdash.org/testDetails.php?test=8742239&build=1223531)

When I download Slicer nighly build for Windows, install the extension and run the test inside of Slicer, the self test also passes without any issues. Just on cdash it seems to have issue.

Any idea how to debug and fix this?

Thanks in advance.

---

<div class="post-metadata">

**Author:** ![adamrankin](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/adamrankin/32/155_2.png) [@adamrankin](https://discourse.slicer.org/u/adamrankin)\
**Post date:** [March 21, 2018, 5:28pm UTC](https://discourse.slicer.org/t/cdash-build-test-failing-for-windows-without-error-log/2378/2 "2018-03-21T17:28:04Z")

</div>

Hello all,

I was wondering what might cause an extension to not be built on the dashboard?

The SlicerVASST extension was built (and failed) on the mac build machine, but was not built for Windows.

Cheers,  
Adam

---

<div class="post-metadata">

**Author:** ![jcfr](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jcfr/32/17825_2.png) [@jcfr](https://discourse.slicer.org/u/jcfr)\
**Post date:** [March 21, 2018, 5:32pm UTC](https://discourse.slicer.org/t/cdash-build-test-failing-for-windows-without-error-log/2378/3 "2018-03-21T17:32:42Z")

</div>

@adamrankin @chribaue Thanks for the reports, we will follow up shortly with an update.

Cc: @Sam_Horvath

---

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [March 21, 2018, 7:23pm UTC](https://discourse.slicer.org/t/cdash-build-test-failing-for-windows-without-error-log/2378/4 "2018-03-21T19:23:22Z")

</div>

> [@adamrankin](#):
>
> I was wondering what might cause an extension to not be built on the dashboard?

Does it depend on another extension?  
There is a known issue on Windows there are any _test_ failures in any of the extensions that you depend on, your extension will not be attempted to be built, it will be just skipped.

---

<div class="post-metadata">

**Author:** ![jcfr](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jcfr/32/17825_2.png) [@jcfr](https://discourse.slicer.org/u/jcfr)\
**Post date:** [March 21, 2018, 7:46pm UTC](https://discourse.slicer.org/t/cdash-build-test-failing-for-windows-without-error-log/2378/5 "2018-03-21T19:46:58Z")

</div>

> [@lassoan](#):
>
> known issue on Windows there are any test failures in any of the extensions that you depend on

This shouldn’t be the case anymore, we are also testing for this:

[https://github.com/Slicer/Slicer/blob/c38d9754c55c7615e59e4a045774455dcd416015/Extensions/CMake/Testing/SlicerExtensionBuildSystemTest.py#L284-L290](https://github.com/Slicer/Slicer/blob/c38d9754c55c7615e59e4a045774455dcd416015/Extensions/CMake/Testing/SlicerExtensionBuildSystemTest.py#L284-L290)

---

<div class="post-metadata">

**Author:** ![cpinter](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/cpinter/32/7995_2.png) [@cpinter](https://discourse.slicer.org/u/cpinter)\
**Post date:** [March 21, 2018, 8:00pm UTC](https://discourse.slicer.org/t/cdash-build-test-failing-for-windows-without-error-log/2378/6 "2018-03-21T20:00:23Z")

</div>

> [@jcfr](#):
>
> This shouldn’t be the case anymore, we are also testing for this

Unfortunately it’s still a problem. It’s enough to take a look at the latest dashboard (see [this one](http://slicer.cdash.org/index.php?project=SlicerPreview&display=project&filtercombine=and&filtercombine=and&filtercombine=or&filtercombine=or&filtercombine=or&filtercombine=or&filtercombine=or&filtercombine=or&filtercount=4&showfilters=1&filtercombine=or&field1=label&compare1=63&value1=SlicerRT&field2=label&compare2=63&value2=GelDosimetry&field3=label&compare3=63&value3=FilmDosimetry&field4=label&compare4=63&value4=SegmentRegistration) with convenient filters). You can see that none of the dependent extensions build on Windows.

---

<div class="post-metadata">

**Author:** ![jcfr](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jcfr/32/17825_2.png) [@jcfr](https://discourse.slicer.org/u/jcfr)\
**Post date:** [March 21, 2018, 8:14pm UTC](https://discourse.slicer.org/t/cdash-build-test-failing-for-windows-without-error-log/2378/7 "2018-03-21T20:14:58Z")

</div>

Just to say that I think the assumption _it is failing because dependent extension tests fails_ is invalid. Few days ago, it look like they all got built as expected:

- [2018-03-18](http://slicer.cdash.org/index.php?project=SlicerPreview&date=2018-03-18&filtercount=4&showfilters=1&filtercombine=or&field1=label&compare1=63&value1=SlicerRT&field2=label&compare2=63&value2=GelDosimetry&field3=label&compare3=63&value3=FilmDosimetry&field4=label&compare4=63&value4=SegmentRegistration)
- [2018-03-17](http://slicer.cdash.org/index.php?project=SlicerPreview&date=2018-03-17&filtercount=4&showfilters=1&filtercombine=or&field1=label&compare1=63&value1=SlicerRT&field2=label&compare2=63&value2=GelDosimetry&field3=label&compare3=63&value3=FilmDosimetry&field4=label&compare4=63&value4=SegmentRegistration)

I think the problem is different. Most likely a regression introduced with the recent refactoring of dashboard script and associated driver scripts.

---

<div class="post-metadata">

**Author:** ![adamrankin](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/adamrankin/32/155_2.png) [@adamrankin](https://discourse.slicer.org/u/adamrankin)\
**Post date:** [March 21, 2018, 8:22pm UTC](https://discourse.slicer.org/t/cdash-build-test-failing-for-windows-without-error-log/2378/8 "2018-03-21T20:22:52Z")

</div>

Oh… Yup that’s it. I’ll start fixing tests!

Thanks!

---

<div class="post-metadata">

**Author:** ![chribaue](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/chribaue/32/1373_2.png) [@chribaue](https://discourse.slicer.org/u/chribaue)\
**Post date:** [March 21, 2018, 8:24pm UTC](https://discourse.slicer.org/t/cdash-build-test-failing-for-windows-without-error-log/2378/9 "2018-03-21T20:24:56Z")

</div>

My extension also depends on another extension. cdash builds it for Windows. Just that the test fails without any output telling me why.

---

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [March 21, 2018, 9:46pm UTC](https://discourse.slicer.org/t/cdash-build-test-failing-for-windows-without-error-log/2378/10 "2018-03-21T21:46:08Z")

</div>

> [@jcfr](#):
>
> Just to say that I think the assumption it is failing because dependent extension tests fails is invalid.

Sounds promising! We have been struggling with the issue of dependent extensions not building and the only factor we could identify was failing tests, but maybe it was just coincidence.

---

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [March 21, 2018, 9:49pm UTC](https://discourse.slicer.org/t/cdash-build-test-failing-for-windows-without-error-log/2378/11 "2018-03-21T21:49:12Z")

</div>

> [@chribaue](#):
>
> Just that the test fails without any output telling me why

That may indicate that the application crashes during shutdown. Also note that on Windows, the application may be built without console support. In that case, console output does not appear on the dashboard.

---

<div class="post-metadata">

**Author:** ![chribaue](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/chribaue/32/1373_2.png) [@chribaue](https://discourse.slicer.org/u/chribaue)\
**Post date:** [March 22, 2018, 1:04pm UTC](https://discourse.slicer.org/t/cdash-build-test-failing-for-windows-without-error-log/2378/12 "2018-03-22T13:04:49Z")

</div>

Hi Andras,

Thank you for the feedback.

According to: [http://slicer.cdash.org/testSummary.php?project=11&name=py\_PETLiverUptakeMeasurementQR&date=2018-03-20](http://slicer.cdash.org/testSummary.php?project=11&name=py_PETLiverUptakeMeasurementQR&date=2018-03-20)  
the test for the Windows nightly only takes 15 seconds before it fails.  
The Mac version runs for 255 seconds until the end.

What is the quickest way to figure out what’s going on?

---

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [March 22, 2018, 8:15pm UTC](https://discourse.slicer.org/t/cdash-build-test-failing-for-windows-without-error-log/2378/13 "2018-03-22T20:15:12Z")

</div>

I’ve checked what’s happening on perklab-factory.

The problem with PETLiverUptakeMeasurement extension test on Windows is that DEPENDENCIES\_ADDITIONAL\_MODULE\_PATHS is set incorrectly. On Windows, binaries are within Release, Debug, RelWithDebInfo, or MinSizeRel subfolder. You can find a working example [here](https://github.com/Slicer/Slicer/blob/master/Modules/Loadable/Segmentations/Testing/Python/CMakeLists.txt#L11-L29).

I would also recommend to use DICOMUtils.LoadDICOMFilesToDatabase for downloading, importing, and loading DICOM data set. It is more robust and faster than what the module does. See usage example [here](https://github.com/Slicer/Slicer/blob/e6878b0065778a56d2e7f182f4c9abba20f4ca88/Applications/SlicerApp/Testing/Python/SubjectHierarchyGenericSelfTest.py#L164-L184).

---

<div class="post-metadata">

**Author:** ![chribaue](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/chribaue/32/1373_2.png) [@chribaue](https://discourse.slicer.org/u/chribaue)\
**Post date:** [March 22, 2018, 8:20pm UTC](https://discourse.slicer.org/t/cdash-build-test-failing-for-windows-without-error-log/2378/14 "2018-03-22T20:20:32Z")

</div>

That’s helpful! Thank you Andras!

I’ll start working on it.

---

<div class="post-metadata">

**Author:** ![adamrankin](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/adamrankin/32/155_2.png) [@adamrankin](https://discourse.slicer.org/u/adamrankin)\
**Post date:** [March 23, 2018, 3:10pm UTC](https://discourse.slicer.org/t/cdash-build-test-failing-for-windows-without-error-log/2378/15 "2018-03-23T15:10:02Z")

</div>

Does the factory.perklab experience the same glitches as overload.kitware?

If so, I will setup my own build configuration and debug from there.

Thanks @jcfr @lassoan for the knowledge

---

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [March 23, 2018, 10:37pm UTC](https://discourse.slicer.org/t/cdash-build-test-failing-for-windows-without-error-log/2378/16 "2018-03-23T22:37:30Z")

</div>

Building all extensions is really simple, so I would recommend to set it up on a computer so that you can debug extension build failures.

> [@adamrankin](#):
>
> Does the factory.perklab experience the same glitches as overload.kitware?

If the same error occurs on factory.perklab and overload.kitware then most likely it is not a glitch. Is there any particular issue that you are investigating?

---

<div class="post-metadata">

**Author:** ![adamrankin](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/adamrankin/32/155_2.png) [@adamrankin](https://discourse.slicer.org/u/adamrankin)\
**Post date:** [March 24, 2018, 12:02am UTC](https://discourse.slicer.org/t/cdash-build-test-failing-for-windows-without-error-log/2378/17 "2018-03-24T00:02:24Z")

</div>

Yes, the SlicerVASST extension is still not being built on windows.

I am setting up a build.