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

Log execution timeouts to Dashboard #31993

Open
rarkins opened this issue Oct 17, 2024 · 0 comments
Open

Log execution timeouts to Dashboard #31993

rarkins opened this issue Oct 17, 2024 · 0 comments
Labels
core:dashboard Related to Dependency Dashboard functionality priority-3-medium Default priority, "should be done" but isn't prioritised ahead of others type:feature Feature (new functionality)

Comments

@rarkins
Copy link
Collaborator

rarkins commented Oct 17, 2024

Describe the proposed change(s).

Related discussion: #31982

The Dependency Dashboard should indicate if a repo has been aborted due to an execution timeout, because such timeouts may be "permanent" instead of temporary. Generally we don't want to update the Dashboard for most temporary errors because they could result in wrong data, but I think in the case of an execution timeout causing the job to abort then it would be good to capture this.

BTW in some environments the entire job might be aborted if it goes too long, so this handles the case where Renovate knowingly cancels a child process package manager command and can gracefully exit in time to update.

@rarkins rarkins added type:feature Feature (new functionality) priority-3-medium Default priority, "should be done" but isn't prioritised ahead of others core:dashboard Related to Dependency Dashboard functionality labels Oct 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core:dashboard Related to Dependency Dashboard functionality priority-3-medium Default priority, "should be done" but isn't prioritised ahead of others type:feature Feature (new functionality)
Projects
None yet
Development

No branches or pull requests

1 participant