# Multiple issues with extension builds

**URL:** <https://discourse.slicer.org/t/multiple-issues-with-extension-builds/6160>\
**Category:** Support\
**Tags:** build, extensions-manager, package, nightlybuild\
**Created:** [March 15, 2019, 5:43pm UTC](https://discourse.slicer.org/t/multiple-issues-with-extension-builds/6160 "2019-03-15T17:43:10Z")\
**Posts on this page:** 4\
**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:** [March 15, 2019, 5:43pm UTC](https://discourse.slicer.org/t/multiple-issues-with-extension-builds/6160/1 "2019-03-15T17:43:10Z")

</div>

There are several issues that are new (at least to me):

- at least some extensions are not listed 3 times (e.g. SlicerElastix is listed only once), which to me means they were not built on all platforms
- maybe I am mistaken, but I vaguely recall there used to be OS icons indicating the platform used to build specific artifact - those are gone now
- if inclusion of “clang” is supposed to indicate macOS, then there is only one line in the table that was built on mac (no idea what extension it packages, since it is called " [macOS-clang-8.0.0-64bits-QT5.10.0-Release](http://slicer.cdash.org/buildSummary.php?buildid=1537174)")
- can someone look at the issue below: [CDash](http://slicer.cdash.org/viewBuildError.php?buildid=1537220) - looks like a factory problem?

 ![image](https://us1.discourse-cdn.com/flex002/uploads/slicer/original/3X/6/2/62ad204a59f7b79172674b24546416bdb1eb4e45.png)

---

<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:** [March 15, 2019, 5:54pm UTC](https://discourse.slicer.org/t/multiple-issues-with-extension-builds/6160/2 "2019-03-15T17:54:29Z")

</div>

Related to this, maybe we should add an entry to FAQ for users updating Slicer installation with a new nightly.

When I do this, I usually over-write my previous nightly. But the problem with this approach is that at the time I do it, I don’t have an easy way to know whether I am “fortunate” to have extensions that I need available in the new nightly. It might be practical to make users aware of this issue, and recommend users to keep their old nightly until they confirm the extensions they need are available.

---

<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 19, 2019, 5:46pm UTC](https://discourse.slicer.org/t/multiple-issues-with-extension-builds/6160/3 "2019-03-19T17:46:26Z")

</div>

Today’s dashboard has a successful DCMQI and QuantitativeReporting build and packages:  
[http://slicer.cdash.org/index.php?project=SlicerPreview&filtercombine=or&filtercombine=or&filtercount=2&showfilters=1&filtercombine=or&field1=label&compare1=63&value1=DCMQI&field2=label&compare2=63&value2=QuantitativeReporting](http://slicer.cdash.org/index.php?project=SlicerPreview&filtercombine=or&filtercombine=or&filtercount=2&showfilters=1&filtercombine=or&field1=label&compare1=63&value1=DCMQI&field2=label&compare2=63&value2=QuantitativeReporting)

I do tend to see the error message sometimes that you posted though.

---

<div class="post-metadata">

**Author:** ![jamesobutler](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jamesobutler/32/7511_2.png) [@jamesobutler](https://discourse.slicer.org/u/jamesobutler)\
**Post date:** [March 19, 2019, 9:07pm UTC](https://discourse.slicer.org/t/multiple-issues-with-extension-builds/6160/4 "2019-03-19T21:07:24Z")

</div>

From another post about similar problems finalizing/uploading the extension:

> [@"Operation too slow. Less than 1 bytes/sec transferred the last 120 seconds"](https://discourse.slicer.org/t/operation-too-slow-less-than-1-bytes-sec-transferred-the-last-120-seconds/4819):
>
> I’ve seen this in several extension builds over the past two nights, causing build (or upload?) failure: Operation too slow. Less than 1 bytes/sec transferred the last 120 seconds

> [@"Operation too slow. Less than 1 bytes/sec transferred the last 120 seconds"](https://discourse.slicer.org/t/operation-too-slow-less-than-1-bytes-sec-transferred-the-last-120-seconds/4819/2):
>
> Thanks for the note. Waiting we finalize the transition to a new system to manage extension, I will ask our sysadmin to setup daily restart of the server at noon.