Skip to content

Conversation

@williamjallen
Copy link
Collaborator

CDash currently maintains two separate types of build errors: "build errors", which are scraped from the log, and "build failures" which are collected by launchers. Needing (almost) duplicate logic to handle these two cases is a major pain point throughout the codebase. This commit begins the process of merging errors and failures into a single table by migrating the precontext, text, and postcontext columns of the builderror table to a stdoutput column which contains precontext+text+postcontext, and a stderror column which contains just the error text.

CDash currently maintains two separate types of build errors: "build errors", which are scraped from the log, and "build failures" which are collected by launchers.  Needing (almost) duplicate logic to handle these two cases is a major pain point throughout the codebase.  This commit begins the process of merging errors and failures into a single table by migrating the precontext, text, and postcontext columns of the builderror table to a stdoutput column which contains precontext+text+postcontext, and a stderror column which contains just the error text.
@williamjallen williamjallen force-pushed the builderror-context-to-stdout branch from 308b59d to 84db783 Compare January 21, 2026 19:10
@williamjallen
Copy link
Collaborator Author

Let's hold off on merging this to let @josephsnyder take a look since it's such a significant change.

Copy link
Member

@josephsnyder josephsnyder left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM also. I can't find any immediately obvious issues

@josephsnyder josephsnyder added this pull request to the merge queue Jan 26, 2026
github-merge-queue bot pushed a commit that referenced this pull request Jan 26, 2026
CDash currently maintains two separate types of build errors: "build
errors", which are scraped from the log, and "build failures" which are
collected by launchers. Needing (almost) duplicate logic to handle these
two cases is a major pain point throughout the codebase. This commit
begins the process of merging errors and failures into a single table by
migrating the precontext, text, and postcontext columns of the
builderror table to a stdoutput column which contains
precontext+text+postcontext, and a stderror column which contains just
the error text.
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Jan 26, 2026
@josephsnyder josephsnyder added this pull request to the merge queue Jan 26, 2026
Merged via the queue into Kitware:master with commit 276298a Jan 26, 2026
7 checks passed
@williamjallen williamjallen deleted the builderror-context-to-stdout branch January 26, 2026 15:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants