vdbergh
vdbergh
Think: what do you want to know from a patch? Indeed an estimate of how much Elo the patch is. But an Elo estimate is useless without a confidence interval....
There is no such thing as "notification summaries". There are two things: - The event log: this is a database. For the `finished_run` events, the event log records the information...
I tried to fix the slow pagination (the queries that contain `"skip":`) in #1630 . Alas it did not work (I don't understand why). I think that in normal circumstances...
It should be easy to do it incrementally. Of course `get_results` is absolutely vital for the primary function of Fishtest so I would keep some sanity checks for a while...
I think so (Tom told me this a long time ago, I haven't read the code).
The idea is that the main page should see reasonably up date data.
Is it caused by mongodb or by the mako rendering?
I guess the solution should be to use pagination in the task list (e.g. using the example of the event log). It would be a bit of an extra hassle...
Not related to this issue but there are some strange things in tests/view https://github.com/glinscott/fishtest/blob/af3a98f8d1730d2cf055d35a7a83b59e2e44204b/server/fishtest/views.py#L1282-L1287 Why is `last_updated` changed when you view the test?
I will try, if it is not too urgent. This weekend I will be a bit busy.