since the codebase is constantly changing, files that passed testing yesterday might fail if tested today. it would be extremely impractical to keep sending _all_ previously passed files, i think.

so we need some reasonable logic to determine what should be resent.

example: issue is marked w/ a certain status, the file is marked as passed, and it's the last patch in the issue?

or maybe some other logic...

Comments

hunmonk’s picture

hunmonk commented

rok and i have decided the following:

  • only issues marked 'code needs review' and 'ready to be committed' will be searched for patches that need re-testing
  • only patches that are currently marked as passed will be retested
  • patches meeting the above to qualifications will be retested once every 24 hours

the 'testing statuses', and the 'testing interval' will both be configurable.

dww’s picture

dww
we/he/they
commented

sounds good to me.

hunmonk’s picture

hunmonk commented
Status: Active » Fixed

committed, applied and running on project.drupal.org

Anonymous’s picture

(not verified) commented
Status: Fixed » Closed (fixed)

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