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? Best regards Ole [1] http://ci.debian.net/packages/f/fitscut/unstable/amd64/ [2] http://ci.debian.net/packages/t/tcl-fitstcl/unstable/amd64/ [3] http://ci.debian.net/ [4] http://ci.debian.net/status/ -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87fv6w9viq....@news.ole.ath.cx
