On 08-01-2024 17:16, Adam Williamson wrote: > Doing it this way was Ben's preference (he wanted to be able to see > that every bug was updated and get a notice from the script for any > single bug change that failed), Historically, the script ran much faster than Bugzilla, which meant after a while, we'd start getting timeouts. This is why there are pauses built into the script. A few years ago, the performance of Bugzilla improved greatly, but I never felt like exploring where the boundaries are. Updating all matching bugs in one transaction is still probably going to result in timeouts, but smaller chunks should work well enough. Of course, that means a transient failure could cause many bugs to need to be re-run instead of just one. That's not to say it can't be done, but it was never a priority for me. On Mon, Jan 8, 2024 at 11:30 AM Sandro <lists@xxxxxxxxxxxxx> wrote: > > I just noticed that some bugs with version '37' were still open while > others were already closed. I'm not saying that's what happened here, but it's not uncommon to see bugs that are closed EOL get re-opened but not have an updated version. For a long time, I never checked that when putting the bug count lists in the Friday's Fedora Facts posts. The first time I did, there were hundreds of bugs across several EOL releases. :-) -- Ben Cotton (he/him) TZ=America/Indiana/Indianapolis https://fedoraproject.org/wiki/User:Bcotton -- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
