What we need in the next round of PIFR

Events happening in the community are now at Drupal community events on www.drupal.org.
You are viewing a wiki page. You are welcome to join the group and then edit it. Be bold!

There may already be a list going on this, but I didn't fine one in the issue queue. What we list here can be turned into issues, but I think we need a higher-level discussion first.

  • Notes/description for each testing client on qa.drupal.org
  • Notification if a PIFR test client is not contacted within 24 hours (when they just disappear and stop checking in)
  • Abiliity to mark an environment as “advisory”
  • Ability to test on multiple environments and require all to pass
  • Fix queue length discrepancy
  • Show list of deferred queues
  • Easier way to find the status of a contrib branch
  • Notification of contrib maintainer if a commit fails
  • Regular testing of contrib modules regardless of whether a commit has happened.
  • Logging what PIFR client did a test (keep a log of those)
  • Capture fatal errors on PIFR tester

Drupal.org Testing Infrastructure

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds:

Hot content this week