http://bugs.winehq.org/show_bug.cgi?id=18947
Summary: AppDB isn't deleting idle maintainers Product: WineHQ Apps Database Version: unspecified Platform: PC URL: http://appdb.winehq.org OS/Version: Linux Status: NEW Keywords: source Severity: normal Priority: P2 Component: appdb-unknown AssignedTo: wine-bugs@winehq.org ReportedBy: kennybobs@o2.co.uk
The AppDB should remove maintainers that don't do anything (by design), but it isn't. Admins are removing idle maintainers manually, and there are a lot of them!
This solution itself isn't ideal, as they just reapply, there is no way to block this, and many users don't take the hint.
http://bugs.winehq.org/show_bug.cgi?id=18947
Rosanne DiMesio dimesio@earthlink.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dimesio@earthlink.net
--- Comment #1 from Rosanne DiMesio dimesio@earthlink.net 2009-06-14 19:09:11 --- Negligent maintainers are worse than no maintainers, because having a maintainer prevents the admins from processing test reports, etc., as soon as they are submitted. Right now, test reports for apps without maintainers are normally processed within 24 hours, while reports for apps with maintainers who aren't doing their job sit around for 2-3 weeks. That really gives people who submit those reports a bad impression.
http://bugs.winehq.org/show_bug.cgi?id=18947
--- Comment #2 from Jeff Zaroyko jeffz@jeffz.name 2009-06-15 05:12:28 --- I'm not sure why it isn't happening, the cron script that gets run every day/night that does maintenance should be sending people warning emails and then removing them automatically. This was working last year when I moved up the warnings + and remove to happen on the 8th day. Not sure when it stopped working, maybe Alexander has some idea about what's wrong.
http://bugs.winehq.org/show_bug.cgi?id=18947
--- Comment #3 from Ken Sharp kennybobs@o2.co.uk 2009-06-17 06:13:39 --- There is an email sent every day that shows that warnings are sent and deletions are made, but it's not clear if these are idle maintainers or just idle users.
There is a line that says something along the lines of "Users we would warn but have data..." Maybe the system isn't warning users that have added test results/screenshots/comments?
http://bugs.winehq.org/show_bug.cgi?id=18947
--- Comment #4 from Rosanne DiMesio dimesio@earthlink.net 2009-06-19 07:37:42 --- I just logged into the AppDB, and found that some of the old test reports now say "no" in the Maintainer column. However, there are equally old ones that still say there is a maintainer. Did someone remove the delinquent maintainers manually? (If so, you missed some.)
http://bugs.winehq.org/show_bug.cgi?id=18947
--- Comment #5 from Ken Sharp kennybobs@o2.co.uk 2009-06-19 07:44:29 --- Yes, I'm doing it now, it's a very slow process (see Bug 18891).
http://bugs.winehq.org/show_bug.cgi?id=18947
--- Comment #6 from Rosanne DiMesio dimesio@earthlink.net 2009-06-19 08:00:25 --- If you want to divide up the work, I can take care of processing the test reports after you remove the maintainers. (I just did a bunch.)
The problem with us doing it manually is that it masks the underlying problem, which really does need to be fixed. Unfortunately, I don't see a way around that.
http://bugs.winehq.org/show_bug.cgi?id=18947
--- Comment #7 from Ken Sharp kennybobs@o2.co.uk 2009-06-19 08:12:01 --- It doesn't mask the underlying problem, as we already know what the problem is. Leaving the results in there for months while we figure it out isn't a solution.
Removing the idle maintainers makes things easier. I'm sure this will continue to show up until a fix is commited.
Bad maintainers is still a serious problem, so they need to be removed anyway.
I've had a user complaining because I removed him after test results had been waiting four weeks. Seen as the automatic deletion is set to eight day, he really can not complain.
http://bugs.winehq.org/show_bug.cgi?id=18947
--- Comment #8 from Rosanne DiMesio dimesio@earthlink.net 2009-06-19 08:59:11 --- (In reply to comment #7)
It doesn't mask the underlying problem, as we already know what the problem is.
Do we? Why isn't the automatic system working?
If he's received the notices, I agree he has no reason to complain. But are we really sure those notices are being sent?
http://bugs.winehq.org/show_bug.cgi?id=18947
Alexander Nicolaysen Sørnes alex@thehandofagony.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |alex@thehandofagony.com
--- Comment #9 from Alexander Nicolaysen Sørnes alex@thehandofagony.com 2009-06-24 16:08:31 --- I haven't seen any maintainance messages for a while; the cron scripts are probably not running. I'll send a mail to Jeremy.
http://bugs.winehq.org/show_bug.cgi?id=18947
nathan.n saturn_systems@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |saturn_systems@yahoo.com
http://bugs.winehq.org/show_bug.cgi?id=18947
--- Comment #10 from Alexander Nicolaysen Sørnes alex@thehandofagony.com 2009-07-21 09:00:02 --- There appears to be something wrong with one or more of the cron scripts. This could just be a result of increased traffic on the database, but it should possible to make some optimizations.
As a result of the scripts not being run, no maintainers are warned when there's queued data for their apps; therefore we shouldn't delete any idle maintainers at the moment.
http://bugs.winehq.org/show_bug.cgi?id=18947
Alexander Nicolaysen Sørnes alex@thehandofagony.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED
--- Comment #11 from Alexander Nicolaysen Sørnes alex@thehandofagony.com 2009-07-22 08:19:14 --- I've disabled the cron script that is reporting errors, and the maintainer notification mails now seem to be working.
It appears that the error log was so big that it exceeded the maximum memory limit, which is not a good sign . . .
http://bugs.winehq.org/show_bug.cgi?id=18947
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #12 from Dmitry Timoshkov dmitry@codeweavers.com 2009-07-22 19:59:57 --- Closing.
http://bugs.winehq.org/show_bug.cgi?id=18947
Rosanne DiMesio dimesio@earthlink.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |REOPENED Resolution|FIXED |
--- Comment #13 from Rosanne DiMesio dimesio@earthlink.net 2012-03-07 22:41:20 CST --- Reopening because it's happening again; there are test reports going back to mid-February waiting to be processed, and the maintainers haven't been removed.
The only cron script email I've been getting is the "Cleanup script starting" one; I haven't received any of the other four since February 13.
http://bugs.winehq.org/show_bug.cgi?id=18947
--- Comment #14 from Rosanne DiMesio dimesio@earthlink.net 2012-04-04 10:15:50 CDT --- This is still not working. I've been processing reports older than a couple of weeks so we don't get a huge backlog, but idle maintainers are not being removed, and doing it manually is a very cumbersome task.
http://bugs.winehq.org/show_bug.cgi?id=18947
Rosanne DiMesio dimesio@earthlink.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED
--- Comment #15 from Rosanne DiMesio dimesio@earthlink.net 2012-04-10 18:59:46 CDT --- Looks like it's fixed for now.
http://bugs.winehq.org/show_bug.cgi?id=18947
Jerome Leclanche adys.wh@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED CC| |adys.wh@gmail.com
--- Comment #16 from Jerome Leclanche adys.wh@gmail.com 2012-04-19 22:08:54 CDT --- Closing
-
wine-bugs＠winehq.org