Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.On /pifr/status, if a client is currently testing, it should list how long that client has been testing that patch. This can have a dual use so that if a client is testing longer than X, it can reset the client/patch. It's also fun information and good for helping debug what server config changes make an improvement without having to do math with timestamps in the logs.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | 537116.png | 9.15 KB | boombatower |
Comments
Comment #1
deekayen commentedPerhaps rather than just displaying the current time of the test in progress, record and display the time to test the patch in total. It might in some way aide catch in his efforts to improve the performance. The time would vary between clients of course, but it might help identify a patch with slow code.
Comment #2
boombatower commentedIt currently records all the information you are requesting.
Last requested - time client requested test
Last tested - time client returned test
So obviously that includes XML-RPC time, CVS checkout, but seems like what we are looking for? Or do you want something more specific...like the actually time it took to run tests? (which is somewhat different then how long client has been running).
It would be easy to diff the amount of time passed since client requested test, but not sure if that's what your looking for.
Comment #3
boombatower commented