Now that Jenkins is responsible for reaching out to drupal.org to notify of when a job starts and ends, we can start tracking test queue/start/end times in pift, and potentially provide that information to the end user.
It would also be very handy as a metric for performance testing, and also allow us some method to determine how much actual testbot time that projects consume, as well as categories of testing, like issue vs daily, or d8 vs d7.
Closed: outdated
3.0
Output and Artifact Display
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.