Feature Request
How can we make CDash better?
Submissions can fail to display for a number of reasons, including parse failures, validation failures, or infrastructure issues. Additionally, submissions can appear to have failed if the queue is backlogged and results take longer than usual to appear. CDash currently displays the number of submissions by hour on the /monitor page, but there is no tracking of actual submissions.
I propose tracking each submission file individually, in a new submissions(id, projectid, buildid, created_at, status, details) table. Doing so allows us to add a new /submissions page, which would replace the /monitor page, as well as a new /projects/<id>/submissions page. These new pages would allow users to understand where their submissions are in the queue, and see any errors associated with failed submissions.
Feature Request
How can we make CDash better?
Submissions can fail to display for a number of reasons, including parse failures, validation failures, or infrastructure issues. Additionally, submissions can appear to have failed if the queue is backlogged and results take longer than usual to appear. CDash currently displays the number of submissions by hour on the
/monitorpage, but there is no tracking of actual submissions.I propose tracking each submission file individually, in a new
submissions(id, projectid, buildid, created_at, status, details)table. Doing so allows us to add a new/submissionspage, which would replace the/monitorpage, as well as a new/projects/<id>/submissionspage. These new pages would allow users to understand where their submissions are in the queue, and see any errors associated with failed submissions.