It appears that since a few weeks ago, koschei stops being able to resolve dependencies for packages in some circumstances, and never recovers. In this state, koschei does not schedule any new scratch builds for the affected packages, and does not report new issues about unresolved dependencies (because dependency resolution for the affected packages is apparently stuck). This makes koschei useless for packages that are affected by this issue - and it appears to be affecting more and more packages over time.
I also filed a ticket with koschei upstream: https://github.com/fedora-infra/koschei/issues/356
Metadata Update from @zlopez: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: Needs investigation, high-gain
I suspect this is due to #11631 I've tried to revert rawhide back to gz... when a compose with that ever finishes we can see if koschei resumes
Doesn't look like it: https://koschei.fedoraproject.org/package/python-nh3?collection=f40
Yeah, it's getting some db error:
Downloading repo primary-f38-build-5627628 /usr/lib64/python3.10/site-packages/hawkey/__init__.py:348: DeprecationWarning: The class hawkey.Repo is deprecated. Please use dnf.repo.Repo instead. The class will be removed on 2019-12-31. warnings.warn(msg, DeprecationWarning) Repo primary-f38-build-5627628 was successfully downloaded Resolving dependencies (repo_id=5627628, collection=f38) for 205 packages Service repo_resolver crashed. Traceback (most recent call last): File "/usr/lib64/python3.10/site-packages/sqlalchemy/engine/base.py", line 1900, in _execute_context self.dialect.do_execute( File "/usr/lib64/python3.10/site-packages/sqlalchemy/engine/default.py", line 736, in do_execute cursor.execute(statement, parameters) psycopg2.errors.NumericValueOutOfRange: integer out of range
@mizdebsk can you look?
Oh, I guess this could be: https://github.com/fedora-infra/koschei/issues/234 again?
Metadata Update from @kevin: - Issue assigned to kevin
So, I just did the steps there to wipe that table and restart the sequence. It seems like it's processing again... but I will leave this open for a bit to confirm.
It looks much better now. I'll continue to monitor my packages for potential issues.
So, the frontend has been crashing some, but I suppose thats a different issue... I am going to go ahead and close this now.
Please do re-open or file a new ticket if you still see any issues.
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)