Skip to content

Conversation

@williamjallen
Copy link
Collaborator

CDash previously used the builderror table to store warnings and errors collected via log scraping, and a separate buildfailure table to store more detailed warning and error information collected via launchers. While convenient in some cases, having two tables which essentially store the same information requires near-duplicate code throughout the codebase and is very confusing for developers. This commit combines the two tables into a single builderrors table and creates builderror and buildfailure updateable views to remain backwards compatible with existing code. This commit also adds a new buildErrors GraphQL field, and deprecates the now-unnecessary basicErrors and basicWarnings fields.

CDash previously used the `builderror` table to store warnings and errors collected via log scraping, and a separate `buildfailure` table to store more detailed warning and error information collected via launchers.  While convenient in some cases, having two tables which essentially store the same information requires near-duplicate code throughout the codebase and is very confusing for developers.  This commit combines the two tables into a single `builderrors` table and creates `builderror` and `buildfailure` updateable views to remain backwards compatible with existing code.  This commit also adds a new `buildErrors` GraphQL field, and deprecates the now-unnecessary `basicErrors` and `basicWarnings` fields.
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.

1 participant