Master keep time of test
deekayen - August 1, 2009 - 01:03
| Project: | Project Issue File Review |
| Version: | 6.x-2.x-dev |
| Component: | Miscellaneous |
| Category: | feature request |
| Priority: | normal |
| Assigned: | boombatower |
| Status: | closed |
Description
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.
#1
Perhaps 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.
#2
It 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.
#3
#4
Automatically closed -- issue fixed for 2 weeks with no activity.