Page MenuHomePhabricator

Figure out why CDash submissions to CDash 2.6 servers are not browsable
Open, NormalPublic

Description

I set up a CDash 2.6 instance at e071-jenkins/cdash and mitk-web/cdash. I created an MITK project and submitted successfully, however, I cannot browse into the details. For example all tests passed but when I click on the number there's an empty page saying 0 tests passed sucessfully. Same for warnings etc...

Event Timeline

kislinsk triaged this task as Normal priority.Jan 23 2019, 12:49 PM
kislinsk created this task.
kislinsk moved this task from Restricted Project Column to Restricted Project Column on the Restricted Project board.
kislinsk moved this task from Restricted Project Column to Restricted Project Column on the Restricted Project board.Feb 27 2019, 10:40 AM
kislinsk added a comment.EditedMay 7 2019, 3:23 PM

Things I found so far:

  • There is/was a missing slash in an XML tag of a file that specifies our subprojects and their dependencies
  • As soon as the MITK-Configure project is submitted, a CDash error is logged: This build already has a configure {"fn":"BuildConfigure::Insert", ...}
  • The actual issue seems to be that we do not submit a Done.xml file at the end of the build

Without the Done.xml submission, the submission won't get rid of the pending status and the details like errors, warnings, and modifications are not parsed and inserted into the database.

kislinsk renamed this task from Figure out why the MITK CDash submission to e071-jenkins/cdash is not browsable to Figure out why CDash submissions to CDash 2.6 servers are not browsable.May 9 2019, 8:58 AM
kislinsk added a project: MITK (2018-04-4).
kislinsk updated the task description. (Show Details)
kislinsk changed the visibility from "Restricted Project (Project)" to "Public (No Login Required)".
kislinsk changed the edit policy from "Restricted Project (Project)" to "Task Author".
kislinsk added a comment.EditedMay 10 2019, 11:01 AM

To get an overview of MITK subprojects:

  • Subprojects are defined in top-level CMakeLists.txt:445 (CTEST_PROJECT_SUBPROJECTS)
  • Subprojects are written into <BINARY_DIR>/CTestConfigSubProject.cmake
  • Additional subprojects can be appended to CTEST_PROJECT_ADDITIONAL_TARGETS
  • Subprojects are also written into <BINARY_DIR>/Project.xml
    • Basically same subprojects are written into Project.xml for superbuild and MITK build (superbuild-version adds SuperBuild as project dependency to subprojects)
    • Documentation subproject is hard-coded into Project.xml with all other subprojects as dependency
  • For each subproject defined in top-level CMakeLists.txt a custom target is created except for "Unlabeled"
  • Not sure if "Unlabeled" is really used in general as it can only be found a few times in the source tree but seemingly only in queries
  • mitk_create_module() has parameter SUBPROJECTS
    • If not set but MITK_DEFAULT_SUBPROJECTS variable is set, it is used instead
    • Else, "MITK-Modules" is set as subproject
    • Subprojects and "MITK" are added as labels to all sources
    • If the module is not header-only, the labels are also added to the target and the module target is added as dependency to the subproject targets
    • module subprojects can be queried after the function call via MODULE_SUBPROJECTS
  • mitk_create_plugin() also has parameter SUBPROJECTS
    • If not set but MITK_DEFAULT_SUBPROJECTS variable is set, it is used instead
    • Else, "MITK-Plugins" is set as subproject
    • Only the target is labeled, not the sources
    • Also, no "MITK" label as in modules
  • mitk_create_executable() basically uses mitk_create_module()
  • mitk_create_module_tests() basically uses mitk_create_executable()
    • Subproject and "MITK" labels are added to the tests
  • mitkAddCustomModuleTests() does the same
  • mitkFunctionAddTestLabel() appends a label to a test
    • Only used by DICOMTesting module for tests named DICOM_Load_${input} where the name is also added as label
kislinsk moved this task from Backlog to Postpone on the MITK (2018-04-4) board.Jul 31 2019, 1:29 PM
kislinsk removed kislinsk as the assignee of this task.Nov 4 2019, 10:22 AM
kislinsk moved this task from Postpone to Backlog on the MITK (2018-04-4) board.
kislinsk edited projects, added MITK; removed MITK (2018-04-4).Feb 11 2020, 4:42 PM
kislinsk claimed this task.Sat, Aug 1, 8:23 AM
kislinsk edited projects, added MITK (2020), CI; removed MITK.

Deleted branch bugfix/T25882-CDash-v2.6.

Deleted branch hotfix/T25882-CDash-v2.6.

kislinsk closed this task as Resolved.Sat, Aug 1, 4:58 PM
kislinsk reopened this task as Open.Sun, Aug 2, 7:31 AM

I still cannot browse submission results. :/

The This build already has a configure error in the CDash log file is triggered because we submit the Configure part twice: for the superbuild and for the MITK-build. However, it seems that this part is only allowed to be submitted once.