Poor information on tests errors
Metadata
Current evaluation
Abandoned. The report highlighted unclear test failure exceptions and proposed capturing output during execution or with the summary. No comments or follow-up actions occurred, and the issue was closed without resolution.
Suggested action: —
No scores available.
Issue body
When the integration and examples tests fail, the exception doesn't tell what was the problem.
We have the option to print everything to the stdout as it is executed or to collect the output and print it with the summary.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Abandoned. The report highlighted unclear test failure exceptions and proposed capturing output during execution or with the summary. No comments or follow-up actions occurred, and the issue was closed without resolution. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without discussion, likely abandoned. The author reported that failing integration and examples tests lack detailed error information and suggested printing execution output or collecting it for a summary. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1617149 There are test statements not run by the tests | snapcraft (launchpad) | closed | Closed without resolution. The report highlighted unexecuted test statements in coverage reports that risk code rot. No comments or fixes were provided. | |
| #1659816 runtests.sh static gives some errors | snapcraft (launchpad) | closed | Closed without resolution or comments, likely abandoned. The report listed static analysis and linting errors in runtests.sh but received no follow-up. |