After my last test, the test failures seem to have disappeared, see here: https://builds.apache.org/job/Commons%20Math%20H10/
Thomas On Tue, May 5, 2015 at 4:39 PM, Luc Maisonobe <l...@spaceroots.org> wrote: > Le 05/05/2015 10:51, Luc Maisonobe a écrit : > > Le 04/05/2015 23:30, Thomas Neidhart a écrit : > >> On 05/04/2015 09:31 PM, Luc Maisonobe wrote: > >>> Le 04/05/2015 19:13, sebb a écrit : > >>>> On 4 May 2015 at 16:43, luc <l...@spaceroots.org> wrote: > >>>>> Le 2015-05-04 14:48, Thomas Neidhart a écrit : > >>>>>> > >>>>>> Problem still remains, see here: > >>>>>> https://builds.apache.org/job/Commons%20Math%20H10/49/console > >>>>>> > >>>>>> The test failures only occur on the following slaves it seems: > >>>>>> > >>>>>> * H10 > >>>>>> * ubuntu-2 > >>>>> > >>>>> > >>>>> This looks like what happened a few months ago then. > >>>>> > >>>>> I will try to look at it. As we are only able to reproduce this on > this > >>>>> build system, I guess this implies committing lots of small changes > (with > >>>>> System.out.println and the like) and triggering a custom buid from > the > >>>>> Jenkins configuration above. I can do that, but wonder if there is > another > >>>>> way without committing the tests in the master branch. Can we set up > an > >>>>> h10-builds branch that would be used by the job above and would be > ignored > >>>>> by the regular job ? > >>>> > >>>> Yes, just configure the Jenkins job to use the appropriate branch. > >>>> It is currently using > >>>> > >>>> */master > >>> > >>> I explored the project and did not find any way to change the build. > >>> Looking at the REST API explanation page, I found a reference to > >>> JOBNAME/config.xml. However, if I try this URL I get an access denied > >>> failure with message "luc is missing the Job/ExtendedRead permission" > >>> and if I try the createItem URL I get an access denied failure with > >>> message "luc is missing the Job/Create permission". > >>> > >>> Could someone give me karma for changing these elements on the Commons > >>> Math H10 job? > >> > >> I changed the job configuration to use the h10-builds branch and started > >> a new build already. > > > > OK, thanks. > > It seemed to work up to commit 96903ec I made this morning, but not > > for the two next ones (67da172 and 14f24f2). They were not picked up > > even after wating a long time and so each time I trigger a new build it > > is still done from 96903ec. > > I don't know why, but it started working again in the afternoon and I > could do a few tests. > Then it seemded to get stuck on a commit. I tried to force it reload > its work space by cleaning it. I was allowed to do it but now the build > does not work anymore. I probably not only cleaned old stuff but also > completely wiped the directory ... I still cannot change anything else > on the job. > > Gary, could you add me to the hudson-jobadmin group (looking at > <http://wiki.apache.org/general/Jenkins> it seems the way to get access). > > I am sorry. > Luc > > > > > Luc > > > >> > >> I am not sure that I have the credentials to give you the permissions. > >> > >> Thomas > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > >> For additional commands, e-mail: dev-h...@commons.apache.org > >> > >> > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >
