# Numerous extensions fail with "packageupload" errors on the dashboard
**URL:** https://discourse.slicer.org/t/numerous-extensions-fail-with-packageupload-errors-on-the-dashboard/2281
**Category:** Development
**Tags:** package, dashboard
**Created:** [March 10, 2018, 2:50am UTC](https://discourse.slicer.org/t/numerous-extensions-fail-with-packageupload-errors-on-the-dashboard/2281 "2018-03-10T02:50:26Z")
**Posts on this page:** 9
**Page:** 1
### Author:  [@fedorov](https://discourse.slicer.org/u/fedorov)
#### Post date: [March 10, 2018, 2:50am UTC](https://discourse.slicer.org/t/numerous-extensions-fail-with-packageupload-errors-on-the-dashboard/2281/1 "2018-03-10T02:50:26Z")
There are many extensions, including SlicerDMRI, SlicerOpenIGTLink, SlicerRadiomics, LASegmenter, TOMAAT, MatlabBridge, that are failing with the error below starting from March 8. I am unable to reproduce this error locally. Anyone has an idea what is happening?
[http://slicer.cdash.org/index.php?project=SlicerPreview](http://slicer.cdash.org/index.php?project=SlicerPreview)
---
### Author:  [@fedorov](https://discourse.slicer.org/u/fedorov)
#### Post date: [March 10, 2018, 2:52am UTC](https://discourse.slicer.org/t/numerous-extensions-fail-with-packageupload-errors-on-the-dashboard/2281/2 "2018-03-10T02:52:21Z")
Coincidentally, there was a change to a relevant cmake script in the Slicer tree 2 days ago…
[https://github.com/Slicer/Slicer/commit/0d1f48832335074a1a91b5c3b71d7f0fc7993637#diff-8a153a54f093a6f42e991fbeea8a455e](https://github.com/Slicer/Slicer/commit/0d1f48832335074a1a91b5c3b71d7f0fc7993637#diff-8a153a54f093a6f42e991fbeea8a455e)
---
### Author:  [@fedorov](https://discourse.slicer.org/u/fedorov)
#### Post date: [March 10, 2018, 2:53am UTC](https://discourse.slicer.org/t/numerous-extensions-fail-with-packageupload-errors-on-the-dashboard/2281/3 "2018-03-10T02:53:57Z")
@jcfr any thoughts? Were those changes tested with a package upload process as done on the dashboard?
---
### Author:  [@jcfr](https://discourse.slicer.org/u/jcfr)
#### Post date: [March 10, 2018, 3:22am UTC](https://discourse.slicer.org/t/numerous-extensions-fail-with-packageupload-errors-on-the-dashboard/2281/4 "2018-03-10T03:22:32Z")
We will have a look shortly. Thanks for your patience.
---
### Author:  [@jcfr](https://discourse.slicer.org/u/jcfr)
#### Post date: [March 10, 2018, 3:32am UTC](https://discourse.slicer.org/t/numerous-extensions-fail-with-packageupload-errors-on-the-dashboard/2281/5 "2018-03-10T03:32:16Z")
> [@fedorov](#):
>
> Were those changes tested with a package upload process as done on the dashboard?
Almost, each one of these tests setup a mock server to validate that expected packages and queries are done.
```auto
$ ctest -R py_cmake_slicer_extensions_
Test project /home/jcfr/Projects/Slicer-Qt5-VTK9-Release/Slicer-build
Start 7: py_cmake_slicer_extensions_index_build_without_upload
1/4 Test #7: py_cmake_slicer_extensions_index_build_without_upload ............... Passed 35.81 sec
Start 8: py_cmake_slicer_extensions_index_build_with_upload
2/4 Test #8: py_cmake_slicer_extensions_index_build_with_upload .................. Passed 36.16 sec
Start 9: py_cmake_slicer_extensions_index_build_with_upload_using_ctest
3/4 Test #9: py_cmake_slicer_extensions_index_build_with_upload_using_ctest ...... Passed 35.86 sec
Start 10: py_cmake_slicer_extensions_index_build_without_upload_using_ctest
4/4 Test #10: py_cmake_slicer_extensions_index_build_without_upload_using_ctest ... Passed 35.65 sec
100% tests passed, 0 tests failed out of 4
Label Time Summary:
CMake = 143.47 sec*proc (4 tests)
Total Test time (real) = 143.51 sec
```
> there was a change to a relevant cmake script in the Slicer tree 2 days ago…
I think this is unrelated, the variable that was involved in the removed code are not used anywhere.
---
### Author:  [@jcfr](https://discourse.slicer.org/u/jcfr)
#### Post date: [March 10, 2018, 3:46am UTC](https://discourse.slicer.org/t/numerous-extensions-fail-with-packageupload-errors-on-the-dashboard/2281/6 "2018-03-10T03:46:47Z")
Problem has been addressed.
We locally modified code to disable the building of extension packages and forgot to revert the changes. This was motivated to test the upload of extension without having to wait for packages to be re-generated.
I will implement a solution avoiding such problem from happening again in the future.
---
### Author:  [@jcfr](https://discourse.slicer.org/u/jcfr)
#### Post date: [March 10, 2018, 12:17pm UTC](https://discourse.slicer.org/t/numerous-extensions-fail-with-packageupload-errors-on-the-dashboard/2281/7 "2018-03-10T12:17:07Z")
> [@jcfr](#):
>
> I will implement a solution avoiding such problem from happening again in the future.
This has also been implemented in [r27037](http://viewvc.slicer.org/viewvc.cgi/Slicer4?view=revision&revision=27037)
Note: Today, since the scripts were manually triggered later than usual, Slicer extension and application _preview_ (aka nightly) packages will be available for download later than expected.
---
### Author:  [@lassoan](https://discourse.slicer.org/u/lassoan)
#### Post date: [March 10, 2018, 1:56pm UTC](https://discourse.slicer.org/t/numerous-extensions-fail-with-packageupload-errors-on-the-dashboard/2281/8 "2018-03-10T13:56:00Z")
It would be great if we could switch to the new “Preview” term, but for that the update page would need to be updated. @jcfr Do you know what’s the status of that?
---
### Author:  [@jcfr](https://discourse.slicer.org/u/jcfr)
#### Post date: [March 10, 2018, 6:57pm UTC](https://discourse.slicer.org/t/numerous-extensions-fail-with-packageupload-errors-on-the-dashboard/2281/9 "2018-03-10T18:57:08Z")
> [@lassoan](#):
>
> that the update page would need to be updated.
If you talk about the download page, I think @mhalle will integrate the PR soon.
>
>
> See https://discourse.slicer.org/t/different-dashboard-for-master-and-stable-bui…lds/2091
`