Hi Miquel,
On 28/07/11 11:04, Miquel Torres wrote:
Hi Antonio,
I'm afraid you are right, the solution I proposed makes no sense.
Sorry I gave you a wrong answer. A revision is unique for a project
(well, now to a branch of a project), and thus they are not separated
by environment. Codespeed was not really designed with revisions in
mind that sometimes have results, and sometimes not. To solve that,
revisions would need to depend on an executable as well, or introduce
a check that so that the revision list is tailored to a particular
exe, but it would be ugly.
I can think of a semi-ugly workaround, I don't know how close it is to a
working solution.
If I understand correctly, the numbers which are displayed in the "changes"
page are precomputed and saved into "Reports" by create_report_if_enough_data.
I can see that the function finds the last_results to compare with simply by
doing last_revs[1]. What about changing this logic to pick the latest rev
which actually contains at least one result for the current environment?
There is a way though to "solve" it right now. Separate executables
into two different projects. pypy32, pypy64, instead of different
environements. The revision list shown does change on-the-fly
depending on the project the selected exe belongs to.
uhm, I don't see any option to select a different project from within
speed.pypy.org. Is it simply because there is only one? Or having another
project would mean to visit a complete different webpage?
Moreover, I wonder how this problem relates to the upcoming speed.python.org:
will every interpreter (cpython, pypy, jython, etc.) be a separate project?
Will it be possible to compare results of different interpreters?
ciao,
Anto
_______________________________________________
pypy-dev mailing list
pypy-dev@python.org
http://mail.python.org/mailman/listinfo/pypy-dev
