I have noticed that in the last three days the mac extension images are not being built
On 8/31/2020 and 8/30/2020 the macOS build had a large number of core tests fail (237 and 177 respectively). This is probably why macOS extensions were not built.
@jcfr or @Sam_Horvath Do you know if a certain number of failing core tests causes extensions to not be built? Or just some specific failed tests results in extensions not being built?
So, if there are that many failing tests, it usually means that the test is failing to terminate correctly, and the tests are going to the 15 minute time-out. This delays the entire build process, so the extension step is not reached.
JC and I are working on some solutions to this issue (severely shortening test timeouts, re-ordering the dashboard process, etc)
Yesterday it was all fine
Yes, a lot were hitting that 15 minute timeout.
It was due to a missing library likely causing Slicer not to fully start
dyld: Library not loaded: /Volumes/D/P/S-0-build/CTK-build/CTK-build/bin/libCTKQtTesting.0.1.dylib
Referenced from: /Volumes/D/P/S-0-build/Slicer-build/bin/Slicer.app/Contents/MacOS/./Slicer
Reason: image not found
error: [/Volumes/D/P/S-0-build/Slicer-build/bin/Slicer.app/Contents/MacOS/./Slicer] exit abnormally - Report the problem.
This happened after there was a CTK update in Slicer. That update was on the 29th and then the corresponding builds on the night of the 29th (30th dashboard build date) and night of the 30th (31st dashboard build date) had the above issue. Once there was another commit to Slicer (a general Slicer update) on the 31st, then the corresponding build on the night of the 31st (Sept 1st dashboard build date) was successful.
Maybe something is wrong with processing a CTK update