Morgan,
Thanks! Now, we got "OK" for doctor test in functest daily job. https://build.opnfv.org/ci/view/functest/job/functest-fuel-baremetal-daily-master/1251/consoleFull BR, Ryota > -----Original Message----- > From: morgan.richo...@orange.com [mailto:morgan.richo...@orange.com] > Sent: Monday, March 06, 2017 4:59 PM > To: Mibu Ryota(壬生 亮太) <r-m...@cq.jp.nec.com>; Jose Lausuch > (jose.laus...@ericsson.com) <jose.laus...@ericsson.com>; > opnfv-tech-discuss@lists.opnfv.org > Subject: Re: [opnfv-tech-discuss] [doctor][functest] doctor scenario debugging > > Hi Ryota, > > when we produce Functest docker, we are currently cloning the Doctor master > repo the last Functest docker has been successfully > produced 1 h ago (started at at 6:10 - Jenkins Time) - previous one was > produced on the 3rd of March so I assume your > changes are taken into account since this time > > Last CI run I found was on fuel started at 6:19 jenkins and should not > include the change but next run should include > it, wait and see... > > /Morgan > > Le 06/03/2017 à 01:16, Ryota Mibu a écrit : > > Jose, Functest team, > > > > > > Quick report: We've fixed bugs in doctor test script [1,2] and got OK in > > doctor's verify job [3]. > > > > However, functest daily job is using old code even in the latest job [4]. > > Maybe we should wait next daily job set. But, > I'll be happy if you can check whether the functest jobs use the latest codes > of included repos or not. > > > > [1] > > https://gerrit.opnfv.org/gerrit/gitweb?p=doctor.git;a=commit;h=8f72e69 > > 5538c2281f923bdbf7a6d7b1d1763c70c [2] > > https://gerrit.opnfv.org/gerrit/gitweb?p=doctor.git;a=commit;h=7c34d9e > > cbd17053ca9d14cc518b11e501b66cbeb [3] > > https://build.opnfv.org/ci/job/doctor-verify-fuel-sample-master/93/ > > [4] > > https://build.opnfv.org/ci/view/functest/job/functest-fuel-baremetal-d > > aily-master/1247/ > > > > > > Thanks, > > Ryota > > > >> -----Original Message----- > >> From: opnfv-tech-discuss-boun...@lists.opnfv.org > >> [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of > >> Ryota Mibu > >> Sent: Wednesday, March 01, 2017 12:34 AM > >> To: opnfv-tech-discuss@lists.opnfv.org > >> Subject: [opnfv-tech-discuss] [doctor][functest] doctor scenario > >> debugging > >> > >> Hi, > >> > >> > >> As we discussed in doctor meeting today, I created JIRA tickets for > >> tracking status of our debug in each installer. We need to get green > >> lights in doctor scenario test in functest report. As we may need to track > >> different bugs for each installer, I created > three tickets for each. > >> > >> Fuel --> https://jira.opnfv.org/browse/DOCTOR-95 > >> Apex --> https://jira.opnfv.org/browse/DOCTOR-96 > >> Joid --> https://jira.opnfv.org/browse/DOCTOR-97 > >> > >> One of barriers is lack of info due to no access to CI pod. In order > >> to ease our debug, I propose to print logs of forked processes in > >> doctor scenario if the test failed, so that we can see log messages in > >> doctor.log . I believe it won't bother functest > main log (Jenkins console). > >> > >> https://gerrit.opnfv.org/gerrit/29489 > >> > >> > >> BR, > >> Ryota > >> > >> > >> _______________________________________________ > >> opnfv-tech-discuss mailing list > >> opnfv-tech-discuss@lists.opnfv.org > >> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss > > > > _______________________________________________ > > opnfv-tech-discuss mailing list > > opnfv-tech-discuss@lists.opnfv.org > > https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss > > > -- > Morgan Richomme > Orange/ IMT/ OLN/ CNC/ NCA/ SINA > > Network architect for innovative services Future of the Network community > member Open source Orange community manager > > > tel. +33 (0) 296 072 106 > mob. +33 (0) 637 753 326 > morgan.richo...@orange.com > > > ____________________________________________________________________________________________________________________ > _____ > > Ce message et ses pieces jointes peuvent contenir des informations > confidentielles ou privilegiees et ne doivent donc > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu > ce message par erreur, veuillez le signaler > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages > electroniques etant susceptibles d'alteration, > Orange decline toute responsabilite si ce message a ete altere, deforme ou > falsifie. Merci. > > This message and its attachments may contain confidential or privileged > information that may be protected by law; they > should not be distributed, used or copied without authorisation. > If you have received this email in error, please notify the sender and delete > this message and its attachments. > As emails may be altered, Orange is not liable for messages that have been > modified, changed or falsified. > Thank you. > _______________________________________________ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
