# Multiple startup errors and no SimpleITK in May 1 nightly on mac

**URL:** <https://discourse.slicer.org/t/multiple-startup-errors-and-no-simpleitk-in-may-1-nightly-on-mac/231>\
**Category:** Support\
**Tags:** bug\
**Created:** [May 1, 2017, 1:44pm UTC](https://discourse.slicer.org/t/multiple-startup-errors-and-no-simpleitk-in-may-1-nightly-on-mac/231 "2017-05-01T13:44:44Z")\
**Posts on this page:** 11\
**Page:** 2

<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:** [May 2, 2017, 9:20pm UTC](https://discourse.slicer.org/t/multiple-startup-errors-and-no-simpleitk-in-may-1-nightly-on-mac/231/22 "2017-05-02T21:20:13Z")

</div>

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

It basically fix a regression introduced in [r25947](http://viewvc.slicer.org/viewvc.cgi/Slicer4?view=revision&revision=25947).

Thanks everyone for their help.

---

<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:** [May 3, 2017, 2:00pm UTC](https://discourse.slicer.org/t/multiple-startup-errors-and-no-simpleitk-in-may-1-nightly-on-mac/231/23 "2017-05-03T14:00:16Z")

</div>

I confirm the issue is fixed in today’s nightly. Thank you!

---

<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:** [May 3, 2017, 9:48pm UTC](https://discourse.slicer.org/t/multiple-startup-errors-and-no-simpleitk-in-may-1-nightly-on-mac/231/24 "2017-05-03T21:48:25Z")

</div>

We had a full-day Slicer training for about 20 new students, including several Mac users, so this fix has come just in time! (it was great that I could just tell them to install the latest version)

---

<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:** [May 3, 2017, 10:07pm UTC](https://discourse.slicer.org/t/multiple-startup-errors-and-no-simpleitk-in-may-1-nightly-on-mac/231/25 "2017-05-03T22:07:35Z")

</div>

Would be nice to post-mortem revise how things work on the factories, to see if this kind of issue can be caught automatically next time.

---

<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:** [May 3, 2017, 10:32pm UTC](https://discourse.slicer.org/t/multiple-startup-errors-and-no-simpleitk-in-may-1-nightly-on-mac/231/26 "2017-05-03T22:32:57Z")

</div>

> [@fedorov](#):
>
> caught automatically next time

Agreed. Our test are all executed on a build tree. Which make sense for “regular” development.

That said, it would be sensible to also execute the tests (e.g the self test) after the package has been generated.

One option would be to have appveyor, travis and circleci triggered after the packaging is completed. They would download the latest package … run few python test and push back the summary in a new entry on Cdash.

---

<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:** [May 3, 2017, 10:36pm UTC](https://discourse.slicer.org/t/multiple-startup-errors-and-no-simpleitk-in-may-1-nightly-on-mac/231/27 "2017-05-03T22:36:21Z")

</div>

I think the only solution would be to have more build machines, with different OS versions, submitting nightly build&test results.

If we provided easy-to-follow instructions/scripts to do this, who could set it up on his/her computer?  
(nightly Slicer core build&test takes 2-4 hours, extensions may take a few hours in addition)

---

<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:** [May 4, 2017, 1:57am UTC](https://discourse.slicer.org/t/multiple-startup-errors-and-no-simpleitk-in-may-1-nightly-on-mac/231/28 "2017-05-04T01:57:04Z")

</div>

> [@lassoan](#):
>
> only solution would be to have more build machines

In that case, the issue was specific to the generated installer and having other build machine wouldn’t have really to detect that problem.

That said, it is generally good to have build and testing on more system.

Otherwise, instructions are currently available here:

[https://www.slicer.org/wiki/Documentation/Nightly/Developers/Tutorials/DashboardSetup](https://www.slicer.org/wiki/Documentation/Nightly/Developers/Tutorials/DashboardSetup)

---

<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:** [May 4, 2017, 12:47pm UTC](https://discourse.slicer.org/t/multiple-startup-errors-and-no-simpleitk-in-may-1-nightly-on-mac/231/29 "2017-05-04T12:47:18Z")

</div>

> [@jcfr](#):
>
> One option would be to have appveyor, travis and circleci triggered after the packaging is completed. They would download the latest package … run few python test and push back the summary in a new entry on Cdash.

That would be an interesting experiment. Is there anything in ctest et al to support testing of packaged binaries, or this would need to be scripted from scratch?

---

<div class="post-metadata">

**Author:** ![pieper](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/pieper/32/8_2.png) [@pieper](https://discourse.slicer.org/u/pieper)\
**Post date:** [May 4, 2017, 11:47pm UTC](https://discourse.slicer.org/t/multiple-startup-errors-and-no-simpleitk-in-may-1-nightly-on-mac/231/30 "2017-05-04T23:47:21Z")

</div>

Typically Ron downloads the nightlies and lets us know if things don’t start, but since there are many things to test and he’s increasingly busy we should automate the process.

That’s why I suggest we name the script AutomatRon (get it?!? wink)

---

<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:** [May 5, 2017, 12:17am UTC](https://discourse.slicer.org/t/multiple-startup-errors-and-no-simpleitk-in-may-1-nightly-on-mac/231/31 "2017-05-05T00:17:14Z")

</div>

I still think “iRon” is better! 😄

---

<div class="post-metadata">

**Author:** ![pieper](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/pieper/32/8_2.png) [@pieper](https://discourse.slicer.org/u/pieper)\
**Post date:** [May 6, 2017, 6:09pm UTC](https://discourse.slicer.org/t/multiple-startup-errors-and-no-simpleitk-in-may-1-nightly-on-mac/231/32 "2017-05-06T18:09:17Z")

</div>

Whoever writes the script can name it!

[Previous page](https://discourse.slicer.org/t/multiple-startup-errors-and-no-simpleitk-in-may-1-nightly-on-mac/231.md?page=1)
