When I download Slicer nighly build for Windows, install the extension and run the test inside of Slicer, the self test also passes without any issues. Just on cdash it seems to have issue.
Does it depend on another extension?
There is a known issue on Windows there are any test failures in any of the extensions that you depend on, your extension will not be attempted to be built, it will be just skipped.
Unfortunately it’s still a problem. It’s enough to take a look at the latest dashboard (see this one with convenient filters). You can see that none of the dependent extensions build on Windows.
Just to say that I think the assumption it is failing because dependent extension tests fails is invalid. Few days ago, it look like they all got built as expected:
Sounds promising! We have been struggling with the issue of dependent extensions not building and the only factor we could identify was failing tests, but maybe it was just coincidence.
That may indicate that the application crashes during shutdown. Also note that on Windows, the application may be built without console support. In that case, console output does not appear on the dashboard.
The problem with PETLiverUptakeMeasurement extension test on Windows is that DEPENDENCIES_ADDITIONAL_MODULE_PATHS is set incorrectly. On Windows, binaries are within Release, Debug, RelWithDebInfo, or MinSizeRel subfolder. You can find a working example here.
I would also recommend to use DICOMUtils.LoadDICOMFilesToDatabase for downloading, importing, and loading DICOM data set. It is more robust and faster than what the module does. See usage example here.
Building all extensions is really simple, so I would recommend to set it up on a computer so that you can debug extension build failures.
If the same error occurs on factory.perklab and overload.kitware then most likely it is not a glitch. Is there any particular issue that you are investigating?