Your question is certainly valid. There are still too many tests depending on some data to exist. Finding out why it no longer fails requires some (extensive?) digging into which patches were pushed in the meantime. ________________________________________ Van: koha-devel-bounces@lists.koha-community.org [koha-devel-bounces@lists.koha-community.org] namens Jonathan Druart [jonathan.druart@biblibre.com] Verzonden: woensdag 30 oktober 2013 16:59 Aan: koha-devel@lists.koha-community.org Onderwerp: Re: [Koha-devel] Jenkins status [was Jenkins build is back to stable : Koha_master #1475] No answer? Does that mean I am the only one wondering why jenkins is back to stable? Or maybe is it because I was not clear enough in my question ? A big work has been made on unit tests. It seems important to me to know why our integration server fails when the code passes on my development instance. Regards, Jonathan 2013/10/24 Jonathan Druart <jonathan.druart@biblibre.com>:
Hi all!
I often receive emails from Jenkins: "master is unstable", "master is back to stable". Last unstable status was caused by a fail in t/db_dependent/Acquisition/Invoices.t (I think). Here Jenkins says : "it is stable, see changes". But changes are about a tt change. I don't know who fixed the failure and how it was fixed. It is frustrating not to know :) Especially because the tests pass on master with my data!
Do you think it would be possible to put something in place in order to follow Jenkins ' moods?
For discussion. Regards, Jonathan
2013/10/23 <chris@bigballofwax.co.nz>:
See <http://jenkins.koha-community.org/job/Koha_master/1475/changes>
Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/