The review audit pulled a total fail today. As in a "Go home, Review Audit, you're appallingly drunk" fail.

The subject question (Progs 10k+ only link) remains closed, and was closed by a Programmers' mod and has been deleted by the community2. There was even a M.P.SE question asking why the question was closed. Another mod and yours truly explained why the question was off-topic and there was no hope of salvaging it.1

So imagine my surprise when I saw that question in the reopen review queue today. My morning coffee had kicked in, and the up vote count on the question seemed suspicious, so I clicked to open the question in a new tab. I saw that the question was indeed still closed; realized it was an audit; and then I selected the correct action of "Leave Closed."

And I failed the audit. Or more accurately, review audit failed to audit properly. :-)

Horrific Fail by the Review Audit

And just in case anyone doubts I clicked the right button in my caffeine deprived coma, I did select "Leave Closed."

See! The coffee had kicked in!

Can we either

  • Schedule the Review Audit for some counseling so it doesn't do this again


  • Encourage it to share whatever it's drinking when it fails like that

1 The MP.SE question is also heavily down voted due to the initial inflammatory rhetoric the OP used in asking their question. The OP was asked to clean up their language and has since edited / removed the rhetoric.

2 Specifically, 3 community members voted to delete the post and it was removed on June 21st. Beyond reference material for this question, there really wasn't any need to have kept the question around.

Oops! Review Audit did it again. This time, it bit another user in close queue and yet another user in reopen queue. FWIW question used in these audits not only was closed, but also failed to reopen.

Checking the timestamps, the question had been closed a few days prior to the audit. Does this suggest that the review audit is using a cached list of questions? And perhaps the cache needs to be refreshed more often?

  • 6
    The review queue wouldn't fail this way if people stopped upvoting these fscking posts. – user102937 Jun 15 '14 at 4:06
  • 7
    @RobertHarvey: The review queue shouldn't fail this way, upvotes or no upvotes. If the actual post is currently closed, and you click "Leave Closed", that should not fail an audit. – Ilmari Karonen Jul 5 '14 at 4:26
  • @IlmariKaronen - Part of the problem may be that the post received several up votes and then sat for a bit (few days) before being noticed. – user194162 Jul 5 '14 at 4:32
  • 1
    same failure yet again in close queue - question closed about 3 days before is shown as known good in close queue, WTF - programmers.stackexchange.com/review/close/74382 ... – gnat Aug 18 '14 at 7:20
  • 1
    ...something is broken, not only because these audits violate rule "No close votes or downvotes, ever... for close/reopen audits" but because these are bad (not clear cut) for any kind of audits, no matter known good or bad, and no matter what queue. No sensible selection algorithm could pick these for audits – gnat Aug 18 '14 at 7:23
  • 1
    looking at vote split, views and answers in these funny "audits", it feels as if a new goal has been introduced lately: to teach reviewers leave open any garbage that manages to get into hot list (both questions in broken audits look like have been listed there) – gnat Aug 18 '14 at 7:52
  • ...regarding caching, I wouldn't be sure to blame it. More likely is that little elves just fly too slowly :) – gnat Aug 21 '14 at 9:04

You must log in to answer this question.