You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently track which test targets fail and keep a snippet of console output per target in the TRSS database.
For certain groups of tests like openjdk and jck we can summarize the list of testcase failures in the TAP file (and/or to console).
Currently, we have to inspect the console output to see if a particular target is failing with the same underlying set of test cases or not from run to run and across platforms.
We should consider pushing the summarized list of testcase failures to console (at the same time we are writing the list to the TAP file, see these related PRs in TKG). Then grabbing that console output and storing it in the TRSS database for querying and comparison between results in the GUI.
This may help us hone in on when root causes for certain failures are introduced.
The text was updated successfully, but these errors were encountered:
We currently track which test targets fail and keep a snippet of console output per target in the TRSS database.
For certain groups of tests like openjdk and jck we can summarize the list of testcase failures in the TAP file (and/or to console).
Currently, we have to inspect the console output to see if a particular target is failing with the same underlying set of test cases or not from run to run and across platforms.
We should consider pushing the summarized list of testcase failures to console (at the same time we are writing the list to the TAP file, see these related PRs in TKG). Then grabbing that console output and storing it in the TRSS database for querying and comparison between results in the GUI.
This may help us hone in on when root causes for certain failures are introduced.
The text was updated successfully, but these errors were encountered: