muratmaga
(Murat Maga)
January 11, 2022, 7:58pm
1
I can’t tell if that’s something on my end, but when I open the extension manager in today’s build (windows), there are no extensions listed. Searching them doesn’t find anything. There are no error messages in the log.
My regular stable works fine with the extension manager on the same computer (can install/uninstall new extensions).
Sam_Horvath
(Sam Horvath (Kitware))
January 11, 2022, 8:52pm
2
Looking into it. It appears that all of the extension builds did not show up on CDash, which is strange.
Sam_Horvath
(Sam Horvath (Kitware))
January 11, 2022, 8:58pm
4
Windows error for extensions, Linux one is the same
[OUTPUT]
* Extra verbosity turned on
[HANDLER_VERBOSE_OUTPUT]
Reading Script: D:/D/DashboardScripts/overload-vs2019-slicerextensions_preview_nightly.cmake
[HANDLER_OUTPUT]
-- Setting 'CTEST_TEST_TIMEOUT' variable with default value '900'
-- Setting 'CTEST_PARALLEL_LEVEL' variable with default value '8'
-- Setting 'CTEST_DROP_SITE' variable with default value 'slicer.cdash.org'
-- Setting 'run_ctest_submit' variable with default value 'TRUE'
-- Setting 'run_ctest_with_disable_clean' variable with default value 'FALSE'
-- Setting 'run_ctest_with_update' variable with default value 'TRUE'
-- Setting 'run_ctest_with_configure' variable with default value 'TRUE'
-- Setting 'run_ctest_with_build' variable with default value 'TRUE'
-- Setting 'run_ctest_with_notes' variable with default value 'TRUE'
-- Setting 'Slicer_UPLOAD_EXTENSIONS' variable with default value 'TRUE'
-- Setting 'run_extension_ctest_submit' variable with default value 'TRUE'
-- Setting 'run_extension_ctest_with_configure' variable with default value 'TRUE'
-- Setting 'run_extension_ctest_with_build' variable with default value 'TRUE'
-- Setting 'run_extension_ctest_with_test' variable with default value 'TRUE'
-- Setting 'run_extension_ctest_with_packages' variable with default value 'TRUE'
-- CTEST_GIT_COMMAND: C:/Users/svc-dashboard/AppData/Local/Programs/Git/cmd/git.exe
-- Removing binary directory [D:/D/P/S-0-E-b]
-- Removing binary directory [D:/D/P/S-0-E-b] - done
-- SCRIPT_MODE .......................: nightly
-- CTEST_BUILD_CONFIGURATION .........: Release
-- ADDITIONAL_CMAKECACHE_OPTION ......:
-- CTEST_CMAKE_GENERATOR .............: Visual Studio 16 2019
-- CTEST_BUILD_FLAGS .................: /maxcpucount:4
-- EXTENSIONS_TRACK_QUALIFIER ........: master
-- EXTENSIONS_BUILDSYSTEM_TESTING ....: FALSE
-- EXTENSIONS_INDEX_GIT_REPOSITORY ...: git://github.com/Slicer/ExtensionsIndex.git
-- EXTENSIONS_INDEX_GIT_TAG ..........: origin/master
-- Slicer_DIR ........................: D:/D/P/Slicer-0-build/Slicer-build
-- BITNESS ...........................: 64
-- OPERATING_SYSTEM ..................: Windows10
-- COMPILER ..........................: VS2019
-- QT_VERSION ........................: 5.15.2
-- BUILD_NAME_SUFFIX .................:
-- CTEST_BUILD_NAME ..................: Windows10-VS2019-64bits-Qt5.15.2-Release
-- HOSTNAME ..........................: overload
-- ORGANIZATION ......................: Kitware
-- CTEST_SITE ........................: overload.kitware
-- DASHBOARDS_DIR ....................: D:/D
-- EXTENSION_DASHBOARD_SUBDIR ........: P
-- EXTENSION_DIRECTORY_BASENAME ......: S
-- Slicer_DIRECTORY_IDENTIFIER .......: 0
-- CTEST_BINARY_DIRECTORY ............: D:/D/P/S-0-E-b
-- Slicer_SOURCE_DIR .................: D:/D/P/Slicer-0
-- EXTENSIONS_BUILDSYSTEM_SOURCE_DIRECTORY: D:/D/P/Slicer-0/Extensions/CMake
-- CTEST_SOURCE_DIRECTORY ............: D:/D/P/Slicer-0/Extensions/CMake
-- CTEST_CONFIGURATION_TYPE ..........: Release
-- CTEST_TEST_TIMEOUT ................: 900
-- CTEST_PARALLEL_LEVEL ..............: 8
-- CTEST_DROP_SITE ...................: slicer.cdash.org
-- run_ctest_submit ..................: TRUE
-- run_ctest_with_disable_clean ......: FALSE
-- run_ctest_with_update .............: TRUE
-- run_ctest_with_configure ..........: TRUE
-- run_ctest_with_build ..............: TRUE
-- run_ctest_with_notes ..............: TRUE
-- Slicer_UPLOAD_EXTENSIONS ..........: TRUE
-- run_extension_ctest_submit ........: TRUE
-- run_extension_ctest_with_configure : TRUE
-- run_extension_ctest_with_build ....: TRUE
-- run_extension_ctest_with_test .....: TRUE
-- run_extension_ctest_with_packages .: TRUE
-- CDASH_PROJECT_NAME ................: SlicerPreview
-- Slicer_EXTENSION_DESCRIPTION_DIR ..: D:/D/P/S-0-E-b/ExtensionsIndex
-- empty_binary_directory ............: TRUE
-- force_build .......................: TRUE
-- model .............................: Nightly
-- track .............................: Extensions-Nightly
-- CTEST_USE_LAUNCHERS ...............: 0
-- Setting ENV{ExternalData_OBJECT_STORES} to D:/D/.ExternalData
-- Slicer_REVISION:30527
-- Configuring D:/D/P/S-0-E-b/CTestConfig.cmake
[HANDLER_VERBOSE_OUTPUT]
SetCTestConfiguration:SourceDirectory:D:/D/P/Slicer-0/Extensions/CMake
SetCTestConfiguration:BuildDirectory:D:/D/P/S-0-E-b
[HANDLER_OUTPUT]
Run dashboard with model Nightly
Source directory: D:/D/P/Slicer-0/Extensions/CMake
Build directory: D:/D/P/S-0-E-b
Group: Extensions-Nightly
First perform the initial checkout: C:/cmake-3.17.2/bin/cmake.exe -P D:/D/DashboardScripts/overload-vs2019-slicerextensions_preview_nightly.cmake-origin-master-nightly-gitclone.cmake
Perform checkout in directory: D:/D/P/Slicer-0/Extensions
[ERROR_MESSAGE]
Initial checkout failed!
[HANDLER_VERBOSE_OUTPUT]
SetCTestConfiguration:BuildDirectory:D:/D/P/S-0-E-b
SetCTestConfiguration:SourceDirectory:D:/D/P/S-0-E-b/ExtensionsIndex
SetCTestConfiguration:SourceDirectory:D:/D/P/S-0-E-b/ExtensionsIndex
SetCTestConfigurationFromCMakeVariable:GITCommand:CTEST_GIT_COMMAND
SetCTestConfiguration:GITCommand:C:/Users/svc-dashboard/AppData/Local/Programs/Git/cmd/git.exe
SetCTestConfigurationFromCMakeVariable:GITUpdateCustom:CTEST_GIT_UPDATE_CUSTOM
SetCTestConfiguration:GITUpdateCustom:C:/cmake-3.17.2/bin/cmake.exe;-P;D:/D/DashboardScripts/overload-vs2019-slicerextensions_preview_nightly.cmake-origin-master-nightly-gitupdate.cmake
[HANDLER_OUTPUT]
Updating the repository: D:/D/P/S-0-E-b/ExtensionsIndex
[ERROR_MESSAGE]
Cannot find UpdateCommand configuration key.
[HANDLER_OUTPUT]
-- First time build - Initialize CMakeCache.txt
-- FILES_UPDATED ................: -1
-- force_build ..................: TRUE
-- Slicer_PREVIOUS_WC_REVISION ..:
-- Slicer_WC_REVISION ...........: 30527
[HANDLER_VERBOSE_OUTPUT]
SetCTestConfiguration:BuildDirectory:D:/D/P/S-0-E-b
SetCTestConfiguration:SourceDirectory:D:/D/P/Slicer-0/Extensions/CMake
SetCTestConfigurationFromCMakeVariable:DropSite:CTEST_DROP_SITE
SetCTestConfiguration:DropSite:slicer.cdash.org
[OUTPUT]
Add file: D:/D/DashboardScripts/overload-vs2019-slicerextensions_preview_nightly.cmake
[HANDLER_OUTPUT]
Submit files
Send to group: Extensions-Nightly
SubmitURL: http://slicer.cdash.org
Submission successful
[HANDLER_VERBOSE_OUTPUT]
SetCTestConfiguration:BuildDirectory:D:/D/P/S-0-E-b
SetCTestConfiguration:SourceDirectory:D:/D/P/Slicer-0/Extensions/CMake
SetCTestConfiguration:ConfigureCommand:"C:/cmake-3.17.2/bin/cmake.exe" "-GVisual Studio 16 2019" "-Ax64" "-Tv142" "D:/D/P/Slicer-0/Extensions/CMake"
[HANDLER_OUTPUT]
Configure project
[ERROR_MESSAGE]
Current Tag empty, this may mean NightlyStartTime / CTEST_NIGHTLY_START_TIME was not set correctly. Or maybe you forgot to call ctest_start() before calling ctest_configure().
Cannot open configure file
mikebind
(Mike Bindschadler)
January 11, 2022, 9:04pm
5
I see no extensions on today’s preview on Windows. I grabbed Slicer 4.13.0-2022-01-06 from @jamesobutler ’s message and confirm that I see extensions listed there. While it seems to be working OK, it does keep showing error messages like the following
Sam_Horvath
(Sam Horvath (Kitware))
January 11, 2022, 9:05pm
6
Yes, no extensions have been built for any platform see: CDash
This a “no more unauthenticated git” issue? Improving Git protocol security on GitHub - The GitHub Blog
January 11, 2022 Final brownout.
This is the full brownout period where we’ll temporarily stop accepting the deprecated key and signature types, ciphers, and MACs, and the unencrypted Git protocol. This will help clients discover any lingering use of older keys or old URLs.
Sam_Horvath
(Sam Horvath (Kitware))
January 11, 2022, 9:09pm
10
I will work on fixing this in the dashboard scripts so that the build can resume correctly tomorrow
1 Like
Sam_Horvath
(Sam Horvath (Kitware))
January 12, 2022, 2:33pm
12
Build looks good today, extensions should now be available for all platforms
3 Likes