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.

Sign up for GitHub

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

Jump to bottom

Analyzed unsolvable packages #5171

Open
3 tasks
fridex opened this issue Apr 12, 2022 · 5 comments
Open
3 tasks

Analyzed unsolvable packages #5171

fridex opened this issue Apr 12, 2022 · 5 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/stack-guidance Categorizes an issue or PR as relevant to SIG Stack Guidance. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@fridex
Copy link
Contributor

fridex commented Apr 12, 2022

Is your feature request related to a problem? Please describe.

It looks like we never hit 0 with number of solved packages in our staging environment. Thoth's solver fails to solve some packages and the systems keeps retrying solving these packages. It would be great to check which packages are "unsolvable" in the stage environment and why thoth-solver failed to solve these packages.

Describe the solution you'd like

  • identify "unsolvable" packages in staging environment
  • check solver logs and derive reasoning why these packages failed to be solved by thoth-solver
  • if necessary, make changes in deployment (ex. adjusting resources) or make changes in the codebase so that these packages are marked as "solved" (either successfully or unsuccessfully) in Thoth's knowledge base
@fridex fridex added the kind/feature Categorizes issue or PR as related to a new feature. label Apr 12, 2022
@fridex
Copy link
Contributor Author

fridex commented Apr 12, 2022

/sig stack-guidance

@sesheta sesheta added the sig/stack-guidance Categorizes an issue or PR as relevant to SIG Stack Guidance. label Apr 12, 2022
@mayaCostantini
Copy link
Contributor

/priority important-soon
/triage accepted

@sesheta sesheta added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on. labels Apr 19, 2022
@sesheta
Copy link
Member

sesheta commented Jul 18, 2022

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@sesheta sesheta added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 18, 2022
@mayaCostantini
Copy link
Contributor

/remove-lifecycle stale
/lifecycle frozen

@sesheta sesheta added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jul 18, 2022
@VannTen
Copy link
Member

VannTen commented Oct 17, 2022

might be related to thoth-station/adviser#2203 ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/stack-guidance Categorizes an issue or PR as relevant to SIG Stack Guidance. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
Planning Board
Status: 🆕 New
Milestone
No milestone
Development

No branches or pull requests
4 participants
@fridex @VannTen @sesheta @mayaCostantini