Over at http://drupal.org/node/614316#comment-2290952 is a string-changing patch that somehow caused 19 fails and 17 exceptions. http://qa.drupal.org/pifr/test/19620

Finding that curious, I requested a re-test at http://drupal.org/node/614316#comment-2291282. But it ended up changing it from RTBC to "needs review," which bumps it out of my queue where it's much harder to keep track of it. And since the re-test request is issued by "System message" and not by "webchick" it doesn't show up in "My issues" either.

There's no reason to move the state of the patch, unless it's at "code needs work" IMO.

CommentFileSizeAuthor
#2 639230-followup-status.patch1.33 KBboombatower

Comments

boombatower’s picture

boombatower commented
Title: Don't move issues from RTBC to needs review when re-rest is requested » Check issue criteria on re-test and use existing status if valid
Project: Project Issue File Review » Project issue file test
boombatower’s picture

boombatower commented
Title: Check issue criteria on re-test and use existing status if valid » Only change issue status on followup if necessary
Assigned: Unassigned » boombatower
Status: Active » Needs review
StatusFileSize
new 639230-followup-status.patch1.33 KB
boombatower’s picture

boombatower commented
Status: Needs review » Fixed

Committed.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.