Hello Ole, Thanks for bringing this up. Hopefully I will be able to shed some light into the issue.
On Sat, May 16, 2015 at 09:23:25PM +0200, Ole Streicher wrote: > Hi, > > how does ci.debian.net actually (re-)run the tests? > > I have several tests added since 5 weeks now, but never got a > successfull test. For example, fitscut [1] got an CI test on April 10, > and appeared in debci about a week later. However, up to now, no real > test was run. Another example is tcl-fitstcl [2]: here the test was > added on April 26, and I got a failure report on May 6. I updated (with > a corrected test) at the same day, but did not get a newer report yet. > > The FAQ says > > | How often are test suites executed? > | The test suite for a source package will be executed: > | * when any package in the dependency chain of its binary packages changes; > | * when the package itself changes; > | * when 1 month is passed since the test suite was run for the last time. > > Also, if I look on the home page [3], I find just a few tests run every > day, which a bit contradicts the total number of packages (which just jumped > from ~1100 to ~3600 in April or May [4]). Shouldn't this number be > > Are there currently any problems with debci? Does it really run > continiously? What is happening is that a system that did the job when the load was small (190 packages), using a "simplest thing that works" philosophy now needs a little bit of work to be adapted to handle a load that is almost 20 times larger (3753 packages at the last update). Let me quote the FAQ entry right below the one that you quoted: | Q: I just added a test suite to my package; how long does it take for it to be | processed? | | Short answer: it depends on many factors and it may take some days, but it will | show up eventually. | | Long answer: the current infrastructure runs tests sequentially on a single | box; think of a loop in which each iteration takes a few days. The delay for | your package to be processed will depend on: | | the size of the current test queue | | the time in which your package has hit the mirror network | | If the package has hit the mirror network at the beginning of the current | iteration, it will take a few days to be processed. If it arrives at the mirror | network in the end of the current iteration, then your are lucky: it will be | processed at the beginning of the next iteration. "A few days" was the estimate when we were a little over 1000 packages, and now we have three times that number. We already came a long way into having a more performant setup, using a distributed setup with multiple workers and all that fun stuff. Martin Pitt started that work back during last year, and I continued that for a few months now. There are still a few details to sort out, but I think we are quite close to being able to migrate to that. -- Antonio Terceiro <terce...@debian.org>
signature.asc
Description: Digital signature
