Open fridex opened 3 years ago
@fridex: This issue is currently awaiting triage.
One of the @thoth-station/devs will take care of the issue, and will accept the issue by applying the
triage/accepted
label and provide further guidance.
The triage/accepted
label can be added by org members by writing /triage accepted
in a comment.
Briefly checking the releases (checked grpcio-tools and spacy)- the issue behind timeout might be a need to compile these packages as they do not provide pre-built wheel binaries for Python 3.8. Given the hardware resources and CPU time allocated, the build in solver workflow never succeeds and thus the workflow task timeouts.
xref https://github.com/AICoE/aicoe-ci/issues/130 for tunable build resource allocations
xref AICoE/aicoe-ci#130 for tunable build resource allocations
This one is related to solver jobs we run to aggregate dependency information for resolver. Resources are part of the corresponding solver Argo workflow task in this case:
Briefly checking the releases (checked grpcio-tools and spacy)- the issue behind timeout might be a need to compile these packages as they do not provide pre-built wheel binaries for Python 3.8. Given the hardware resources and CPU time allocated, the build in solver workflow never succeeds and thus the workflow task timeouts.
Shall we create a re-build pipeline that will do the compilation and publish to our own PI?
/priority important-soon /area solver
Briefly checking the releases (checked grpcio-tools and spacy)- the issue behind timeout might be a need to compile these packages as they do not provide pre-built wheel binaries for Python 3.8. Given the hardware resources and CPU time allocated, the build in solver workflow never succeeds and thus the workflow task timeouts.
Shall we create a re-build pipeline that will do the compilation and publish to our own PI?
Good idea for the future - we could do it for the selected set of packages that Thoth users use.
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen
.
Mark the issue as fresh with /remove-lifecycle rotten
.
/close
@sesheta: Closing this issue.
/remove-lifecycle rotten /lifecycle frozen /reopen
@goern: Reopened this issue.
cc: @harshad16
/triage accepted
Briefly checking the releases (checked grpcio-tools and spacy)- the issue behind timeout might be a need to compile these packages as they do not provide pre-built wheel binaries for Python 3.8. Given the hardware resources and CPU time allocated, the build in solver workflow never succeeds and thus the workflow task timeouts.
Shall we create a re-build pipeline that will do the compilation and publish to our own PI?
Good idea for the future - we could do it for the selected set of packages that Thoth users use.
@goern @harshad16 is that something we still want to implement?
+1 @mayaCostantini could you extract this out into an issue on its own and add it to https://github.com/orgs/open-services-group/projects/21
Describe the bug
See stage environment - the metric for unsolved packages keeps on ~130 package releases for some time. Checking the namespace, some packages fail to be solved using the solver-rhel-8-py38 in the given time and this solving never succeeds.
Packages that might be affected:
Note not all the packages might be causing troubles as I saw package-releases job run in parallel that inserted some new releases.
To Reproduce Steps to reproduce the behavior:
Expected behavior
Package releases should be successfully solved.
Additional context
I tried to locally resolve
grpcio-tools===1.1.3
using thoth-solver, it looks like it works. Solver jobs reported exceeded time to solve the job.Acceptence criteria