# Interpreting CDash reporting: extension is packaged despite build errors?

**URL:** <https://discourse.slicer.org/t/interpreting-cdash-reporting-extension-is-packaged-despite-build-errors/856>\
**Category:** Development\
**Tags:** extensions-manager, package\
**Created:** [August 11, 2017, 2:03pm UTC](https://discourse.slicer.org/t/interpreting-cdash-reporting-extension-is-packaged-despite-build-errors/856 "2017-08-11T14:03:57Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![fedorov](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/fedorov/32/14_2.png) [@fedorov](https://discourse.slicer.org/u/fedorov)\
**Post date:** [August 11, 2017, 2:03pm UTC](https://discourse.slicer.org/t/interpreting-cdash-reporting-extension-is-packaged-despite-build-errors/856/1 "2017-08-11T14:03:57Z")

</div>

I checked the dashboard today, and I found that one of our extension had a (new) [build error](http://slicer.cdash.org/viewBuildError.php?buildid=1077712):

```auto
Error copying file "@rpath/libITKFactoryRegistration.dylib" to 
  "/.../DCMQI-build/dcmqi-build/_CPack_Packages/Darwin/TGZ/26228-macosx-amd64-DCMQI-
  git95356d4-2017-07-27/Slicer.app/Contents/lib/Slicer-4.7/libITKFactoryRegistration.dylib".

```

However, despite of this error, the extension package is available, and it seems to work in Slicer.

 ![image](https://us1.discourse-cdn.com/flex002/uploads/slicer/original/3X/c/8/c8c4e0df28dcd0a4e357d3333e4ff110e1b76517.png)

@jcfr could this potentially be related to the fixes discussed in [No nightly Mac binary since August 1 - #11 by jcfr](https://discourse.slicer.org/t/no-nightly-mac-binary-since-august-1/836/11)?

---

<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:** [August 12, 2017, 7:26pm UTC](https://discourse.slicer.org/t/interpreting-cdash-reporting-extension-is-packaged-despite-build-errors/856/2 "2017-08-12T19:26:01Z")

</div>

Look like a legitimate error associated with packaging. I will have a look.

To clarify, packaging is technically not part of the “build”, it happens afterward.

That said, we drive the packaging using ctest\_build and submit the additional results like they were a build output. That is packaging error are reported like “build” errors.

> <https://github.com/Slicer/Slicer/blob/05f67d75667f002b135e361f0f7e975ebcb7e77f/Extensions/CMake/SlicerBlockBuildPackageAndUploadExtension.cmake#L228-L238>

---

<div class="post-metadata">

**Author:** ![fedorov](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/fedorov/32/14_2.png) [@fedorov](https://discourse.slicer.org/u/fedorov)\
**Post date:** [August 12, 2017, 7:44pm UTC](https://discourse.slicer.org/t/interpreting-cdash-reporting-extension-is-packaged-despite-build-errors/856/3 "2017-08-12T19:44:15Z")

</div>

Thanks for looking into this @jcfr!

Note that there were no changes to the extension source code between the latest successful build/package (Aug 1, [http://slicer.cdash.org/buildSummary.php?buildid=1073259](http://slicer.cdash.org/buildSummary.php?buildid=1073259)) and the date when failure was first observed (Aug 9, [http://slicer.cdash.org/buildSummary.php?buildid=1076906](http://slicer.cdash.org/buildSummary.php?buildid=1076906)). In between there were no Mac builds of extensions at all. So it looks like the problem is on the Slicer side.

---

<div class="post-metadata">

**Author:** ![fedorov](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/fedorov/32/14_2.png) [@fedorov](https://discourse.slicer.org/u/fedorov)\
**Post date:** [August 15, 2017, 1:40pm UTC](https://discourse.slicer.org/t/interpreting-cdash-reporting-extension-is-packaged-despite-build-errors/856/4 "2017-08-15T13:40:39Z")

</div>

@jcfr the problem I mentioned above persists: [http://slicer.cdash.org/viewBuildError.php?buildid=1079987](http://slicer.cdash.org/viewBuildError.php?buildid=1079987)

I see the same problem for a large number of other C++ extensions. Is there a plan to address this regression in the Slicer core?

---

<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:** [August 21, 2017, 10:27pm UTC](https://discourse.slicer.org/t/interpreting-cdash-reporting-extension-is-packaged-despite-build-errors/856/5 "2017-08-21T22:27:36Z")

</div>

One of the MacOSX issue is now addressed by [r26296](http://viewvc.slicer.org/viewvc.cgi/Slicer4?view=revision&revision=26296), I will follow up on the dcmqi error tomorrow.

---

<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:** [August 24, 2017, 7:45am UTC](https://discourse.slicer.org/t/interpreting-cdash-reporting-extension-is-packaged-despite-build-errors/856/6 "2017-08-24T07:45:12Z")

</div>

macOS packaging issue will be addressed by

> <https://github.com/Slicer/Slicer/issues/780>
>
> This issue was created automatically from an original Mantis Issue. Further discussion may take place here.

---

<div class="post-metadata">

**Author:** ![fedorov](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/fedorov/32/14_2.png) [@fedorov](https://discourse.slicer.org/u/fedorov)\
**Post date:** [August 24, 2017, 2:35pm UTC](https://discourse.slicer.org/t/interpreting-cdash-reporting-extension-is-packaged-despite-build-errors/856/7 "2017-08-24T14:35:32Z")

</div>

Thank you @jcfr for tracking this down!

I am sure you will let us know if any updates will be needed for the extensions!

---

<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:** [August 24, 2017, 6:40pm UTC](https://discourse.slicer.org/t/interpreting-cdash-reporting-extension-is-packaged-despite-build-errors/856/8 "2017-08-24T18:40:58Z")

</div>

This should be fixed in [r26301](http://viewvc.slicer.org/viewvc.cgi/Slicer4?view=revision&revision=26301)

---

<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:** [August 25, 2017, 5:56pm UTC](https://discourse.slicer.org/t/interpreting-cdash-reporting-extension-is-packaged-despite-build-errors/856/9 "2017-08-25T17:56:46Z")

</div>

And here is a follow up commit addressing the remaining issues in Slicer. See [r26305](http://viewvc.slicer.org/viewvc.cgi/Slicer4?view=revision&revision=26305)

Corresponding changes in upstream projects are here:

- ITK: [http://review.source.kitware.com/#/c/22583/](http://review.source.kitware.com/#/c/22583/)
- CTK: [https://github.com/commontk/CTK/pull/745/commits/2b71958a424f7fff01b248aaebce0bcdb4dd25ed](https://github.com/commontk/CTK/pull/745/commits/2b71958a424f7fff01b248aaebce0bcdb4dd25ed)
- MINC: [https://github.com/BIC-MNI/libminc/pull/87](https://github.com/BIC-MNI/libminc/pull/87)