Hi, I encountered a same issue patch link: https://gerrit.fd.io/r/c/vpp/+/22727 log: https://logs.fd.io/production/vex-yul-rot-jenkins-1/vpp-verify-master-centos7/22346/
Best Regards, Sun, Chenmin From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of Sun, Chenmin Sent: Saturday, October 12, 2019 9:49 AM To: Dave Wallace <dwallac...@gmail.com>; vpp-dev@lists.fd.io Subject: Re: [vpp-dev] How to solve "No problems were identified. If you know why this problem occurred, please add a suitable..." #automation Thanks for the feedback. Best Regards, Sun, Chenmin From: Dave Wallace [mailto:dwallac...@gmail.com] Sent: Friday, October 11, 2019 11:57 PM To: Sun, Chenmin <chenmin....@intel.com<mailto:chenmin....@intel.com>>; vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io> Subject: Re: [vpp-dev] How to solve "No problems were identified. If you know why this problem occurred, please add a suitable..." #automation It looks like there was some state in the build executor that didn't get cleaned up correctly. I'm guessing that a new executor was used in the 'recheck' which did pass. We'll keep an eye on this to see if it is a recurring issue. Thanks for reporting it. -daw- On 10/11/2019 9:46 AM, Sun, Chenmin wrote: Hi, Here's my patch link. https://gerrit.fd.io/r/c/vpp/+/22637 You can see the 4th compiling passed without that error, however, I didn't change any code. Best Regards, Sun, Chenmin From: Dave Wallace [mailto:dwallac...@gmail.com] Sent: Friday, October 11, 2019 9:43 PM To: Sun, Chenmin <chenmin....@intel.com><mailto:chenmin....@intel.com>; vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io> Subject: Re: [vpp-dev] How to solve "No problems were identified. If you know why this problem occurred, please add a suitable..." #automation Please provide the link to your gerrit patch. Thanks, -daw- On 10/10/2019 10:04 PM, Sun, Chenmin wrote: Hi, I found my patch always met an automation compiling error, stating "No problems were identified. If you know why this problem occurred, please add a suitable...". Opening the log I can see "ninja: error: manifest 'build.ninja' still dirty after 100 tries". I have met 3 times on my latest patch(the 4th compiling is ongoing). Does anyone know what does this error means? How to solve this problem? -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#14157): https://lists.fd.io/g/vpp-dev/message/14157 Mute This Topic: https://lists.fd.io/mt/34482502/675079 Mute #automation: https://lists.fd.io/mk?hashtag=automation&subid=1480517 Group Owner: vpp-dev+ow...@lists.fd.io<mailto:vpp-dev+ow...@lists.fd.io> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [dwallac...@gmail.com<mailto:dwallac...@gmail.com>] -=-=-=-=-=-=-=-=-=-=-=-
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#14178): https://lists.fd.io/g/vpp-dev/message/14178 Mute This Topic: https://lists.fd.io/mt/34482502/21656 Mute #automation: https://lists.fd.io/mk?hashtag=automation&subid=1480452 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
