Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TUI "closeness" evaluation #221

Open
msuozzo opened this issue Dec 12, 2024 · 0 comments
Open

TUI "closeness" evaluation #221

msuozzo opened this issue Dec 12, 2024 · 0 comments

Comments

@msuozzo
Copy link
Member

msuozzo commented Dec 12, 2024

It would be nice to display an evaluation of how close a failed rebuild is to success from the TUI summary view. The two main cases to support would be build failures and comparison failures. Build failures could use a coarse metric of how many steps were observed to run (tricky with nested commands like npx. might want to split these out and use set -eux) possibly with some log length metric. Comparison failures could be evaluated using ContentSummary for now and could be augmented with richer diffs.

The UI could be a two-segment progress bar (with a fancier structure than below), the first being build success and the second being comparison completeness:

npm foo 1.0.0      [o___|____]
npm bar 1.0.0      [oooo|o___]

Assuming this to be a monotonic indicator of success would have issues: With this approach, you could imagine a local maxima of a build that succeeds but is of a substantially lower complexity than is necessary. Still, it could be a good, quick, indicator of progress, especially if we disaggregate results by verdict (or have many verdicts for a single artifact/package).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant