Skip to content

Reduce critical error rate#4048

Draft
finestructure wants to merge 1 commit intomainfrom
reduce-critical-error-rate
Draft

Reduce critical error rate#4048
finestructure wants to merge 1 commit intomainfrom
reduce-critical-error-rate

Conversation

@finestructure
Copy link
Copy Markdown
Member

@finestructure finestructure commented May 1, 2026

We have a couple of packages which trigger analysis errors beyond our control. They trigger the following warning whenever they are being analysed:

[ CRITICAL ] updatePackages: unusually high error rate: 1/5 = 20.0% [component: analyze]

The reason this warning exists is to make sure we don't end up with most of the analysis queue blocked by packages that can't be analysed.

Raising the limit slightly will allow for single packages failing without triggering a critical warning.

At the same time, we should see if we can let packages with known errors, or rather errors we know that aren't ours, pass analysis, so they don't come around early. What's happening right now is that they are analysed quite frequently, because they're not marked done and put to the end of the queue until next regular analysis.

To do:

  • check if/how we can complete analysis on known problematic packages

@cla-bot cla-bot Bot added the cla-signed label May 1, 2026
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.

2 participants