Normally if the branch tests are failing there's no way to get an automated test of the patch that will fix them. It would be really nice if we provided that somehow. Could we have a link that forces a test to be done even though there's a branch #fail?

While we're doing this it would be nice to improve the UI so people know why their patches are postponed. They never do understand that.

Comments

jthorson’s picture

jthorson commented

Postponed patches can now be 'forced' using the 'retest' link for that patch on qa.d.o.

This could probably use some documentation somewhere before we close the issue, though.

jthorson’s picture

jthorson commented
Issue summary: View changes

Updated feature request.

drumm’s picture

drumm
he/him
Location NY, US
commented
Issue summary: View changes
Status: Active » Closed (cannot reproduce)

This was done in the 7.x-3.x branch.