Pavel Raiskup

Well, I haven't seen it for a long time actually. I mean, there's the residual issue #2272 that we know of, but it is a different issue from this one....

Note there's an error in the backend.log: ``` [2023-11-22 13:25:54,679][ ERROR][PID:1764229] Backend process error: Giving up waiting for copr_base repository, please try to manually regenerate the DNF repository (e.g. by...

Has this actually happened for the F40 branching?

Thank you for the feedback. Reviewing the action items above... I think they are still worth doing, we had ~300 failed actions during the last branching event:  

``` $ psql -c 'select count(id) from action where action_type = 6 and created_on > 1706751687 and result != 1;' Line style is unicode. Border style is 2. ┌───────┐ │...

Most of them are in the `@fedora-review` namespace (only 91 not): [copr-fe@copr-fe ~][PROD]$ psql -c 'select count(id) from action where action_type = 6 and created_on > 1706751687 and result !=...

I backed up the corresponding logs on backend: ``` $ ls -1 /var/lib/copr/public_html/archive/issues/copr-3016 action_dispatcher.log-20240218.gz actions.log-20240218.gz ```

I checked two examples of non-`@fedora-review` builds, but they still use fedora-review: https://copr.fedorainfracloud.org/coprs/zzambers/fedora-pkgs/build/6240960/ https://copr.fedorainfracloud.org/coprs/fed500/md4c/build/6222513/

This has been implemented as createrepo_c retry mechanism in #3225. We believe it fixed this issue.

Triage: @xsuchy's idea -> Could we have a button for "starting discussion" (no matter if temporary project or not)?