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.
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. Cheers, Miquel 2011/7/27 Antonio Cuni <anto.c...@gmail.com>: > Hi Miquel, > > On 25/07/11 21:09, Miquel Torres wrote: >> >> Btw., in any case you can start saving results in separated >> environments. That will at least make changes work right away, and it >> does make sense to have "tannit 32 bits" and "tannit 64 bits". > > are you sure that having two separate environments will fix the "changes" > page? I tried to add "tannit-64" (no results yet, a build is running right > now), but in the dropdown menu of the Changes page I can see all the > revisions that are also in "tannit". I'd have expected those two to be > completely separate. > > ciao, > Anto > _______________________________________________ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
