The problem is a little deeper. The build should install from nexus the package if its in nexus and the version in master hasn't increased. Its not doing that, which is the root of the problem. Removing the package from nexus without fixing that will simply buy us *one* build (which if we need it bad enough, would be a fine hack) but the next merge build will refail for the same reasons.
Ed On Wed, Nov 8, 2017 at 7:52 AM Vanessa Valderrama via RT < fdio-helpd...@rt.linuxfoundation.org> wrote: > This error typically occurs when an artifact that already exists is trying > to be deployed. Would you like to remove the artifacts that were deployed > on 10/10? I believe that will resolve this error. > > vpp-dpdk-dev-17.08-vpp2_amd64-deb.deb > > Thank you, > Vanessa > > On Wed Nov 08 08:49:28 2017, hagbard wrote: > > This appears to be something going wrong pushing to the nexus > > server... it > > looks like the nexus server is rejecting the push, from: > > > > https://jenkins.fd.io/view/vpp/job/vpp-merge-master- > > ubuntu1604/3174/consoleFull > > > > 13:07:08 [ERROR] Failed to execute goal > > org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy-file (default- > > cli) > > on project standalone-pom: Failed to deploy artifacts: Could not > > transfer > > artifact io.fd.vpp:vpp-dpdk-dev:deb:deb:17.08-vpp2_amd64 from/to > > fd.io.master.ubuntu.xenial.main ( > > https://nexus.fd.io/content/repositories/fd.io.master.ubuntu.xenial.main > ): > > Failed to transfer file: > > > https://nexus.fd.io/content/repositories/fd.io.master.ubuntu.xenial.main/io/fd/vpp/vpp- > > dpdk-dev/17.08-vpp2_amd64/vpp-dpdk-dev-17.08-vpp2_amd64-deb.deb. > > Return code is: 400, ReasonPhrase: Bad Request. -> [Help 1] > > 13:07:08 [ERROR] > > 13:07:08 [ERROR] To see the full stack trace of the errors, re-run > > Maven > > with the -e switch. > > 13:07:08 [ERROR] Re-run Maven using the -X switch to enable full debug > > logging. > > 13:07:08 [ERROR] > > 13:07:08 [ERROR] For more information about the errors and possible > > solutions, please read the following articles: > > 13:07:08 [ERROR] [Help 1] > > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException > > 13:07:08 Build step 'Execute shell' marked build as failure > > > > > > On Tue, Nov 7, 2017 at 11:50 PM Lori Jakab > > <lorand.jakab+f...@gmail.com> > > wrote: > > > > > Hello, > > > > > > Any update on this? We can't get the latest patches via the Ubuntu > > > package > > > manager and that hurts certain test scenarios. > > > > > > -Lori > > > > > > > > > On Mon, Nov 6, 2017 at 6:31 PM, Ed Warnicke <hagb...@gmail.com> > > > wrote: > > > > > >> This looks like we are hitting the limit on storage at packagecloud. > > >> > > >> I've manually trimmed some old packages, but we really really need > > >> to get > > >> the script going that autotrims for us. > > >> > > >> Vanessa, > > >> > > >> How are we doing on that? > > >> > > >> Ed > > >> > > >> On Mon, Nov 6, 2017 at 9:17 AM Luke, Chris <chris_l...@comcast.com> > > >> wrote: > > >> > > >>> The post-merge jobs are failing with errors like this: > > >>> > > >>> > > >>> > > >>> *16:04:05* [ERROR] Failed to execute goal > > >>> org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy-file > > >>> (default-cli) on project standalone-pom: Failed to deploy > > >>> artifacts: Could not transfer artifact io.fd.vpp:vpp-dpdk- > > >>> dev:deb:deb:17.08-vpp2_amd64 from/to > > >>> fd.io.master.ubuntu.xenial.main > > >>> ( > https://nexus.fd.io/content/repositories/fd.io.master.ubuntu.xenial.main): > > >>> Failed to transfer file: > > >>> > https://nexus.fd.io/content/repositories/fd.io.master.ubuntu.xenial.main/io/fd/vpp/vpp- > > >>> dpdk-dev/17.08-vpp2_amd64/vpp-dpdk-dev-17.08-vpp2_amd64-deb.deb. > > >>> Return code is: 400, ReasonPhrase: Bad Request. -> [Help 1] > > >>> > > >>> > > >>> > > >>> (from > > >>> https://jenkins.fd.io/job/vpp-merge-master- > > >>> ubuntu1604/3148/consoleFull) > > >>> > > >>> > > >>> > > >>> This is sufficiently voodoo for me to not know how to proceed. (The > > >>> Nexus stuff consistently annoys and baffles me, not least the > > >>> overly-verbose chatter in build logs) > > >>> > > >>> > > >>> > > >>> Could someone take a look, please? > > >>> > > >>> > > >>> > > >>> Net result: No packages are being stored from master, and docs are > > >>> not > > >>> getting generated. It has been doing for thia a few days as best I > > >>> can tell. > > >>> > > >>> > > >>> > > >>> Thanks, > > >>> > > >>> Chris. > > >>> _______________________________________________ > > >>> vpp-dev mailing list > > >>> vpp-dev@lists.fd.io > > >>> https://lists.fd.io/mailman/listinfo/vpp-dev > > >> > > >> > > >> _______________________________________________ > > >> vpp-dev mailing list > > >> vpp-dev@lists.fd.io > > >> https://lists.fd.io/mailman/listinfo/vpp-dev > > >> > > > > > > > > > > > _______________________________________________ > vpp-dev mailing list > vpp-dev@lists.fd.io > https://lists.fd.io/mailman/listinfo/vpp-dev >
_______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
