I always thought that there are two use-cases of Testboard: 1. Whenever you push to the Isabelle repository, this is tested by testboard 2. You can push your changeset only to testboard, to check it before pushing it to the isabelle repo and perhaps breaking it.
However, according to Lars' reply, the second use-case is almost not possible, as a particular changeset will quickly be hidden by a huge number of later pushes to the isabelle repository, and never be touched again. So here is my question: If I have some changeset, and want to check whether it breaks AFP before pushing it to the isabelle repository, how do I do it? Can I use Testboard? -- Peter On Fr, 2013-09-27 at 11:49 +0200, Lars Noschinski wrote: > On 27.09.2013 09:16, Peter Lammich wrote: > > I pushed on testboard 19 hours ago, and my push (36cf426cb1c6) currently > > only shown as 1/3 processed. Now, testboard seems to have stopped > > processing it ... however, many later pushs have already run through > > completely. > > > > What's the strategy to get your push on testboard processed within > > reasonable time? > > Basically Mira is just watching the repository. If a test run finishes, > it looks at the repository, takes the "tip" and tests it (if it was not > already tested). In particular, this means that later pushes can take > the focus away from your pushes. > > It might be a good idea to implement a strategy which tests the existing > heads in reverse chronological order (commits pushed last get tested > first), but I am not sure whether this information is available in > Mercurial (we have the commit date, but this is not necessarily related > to the push-date). > > -- Lars > _______________________________________________ > isabelle-dev mailing list > isabelle-...@in.tum.de > https://mailmanbroy.informatik.tu-muenchen.de/mailman/listinfo/isabelle-dev _______________________________________________ isabelle-dev mailing list isabelle-...@in.tum.de https://mailmanbroy.informatik.tu-muenchen.de/mailman/listinfo/isabelle-dev
