# 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:** 1\
**Showing post:** 4

<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?

---

_[View the full topic](https://discourse.slicer.org/t/interpreting-cdash-reporting-extension-is-packaged-despite-build-errors/856)._